people like to think this (especially indies), but the reality is saas is less about the tech, and more about liability reduction
folks have been able to self-host sentry for all of time, why don't they?
nothing changes- bad businesses continue to be bad businesses
@zeeg is sentry going to eventually integrate with infrastructure/system metrics?
The product is so good with errors and traces right now. If only we could get system metrics integrated, I wouldn't need other solutions.
@mitsuhiko I agree with this so much. Even apart from dep maintenance hell, too many engineers think deps are "free" from risk. You introduce that dep, now you have to support it in prod. If something goes wrong, now you're debugging more layers that you could have written yourself.
“Celebrated are the minimal dependencies, the humble function that just quietly does the job, the code that doesn't need to be touched for years because it was done right once.” https://t.co/EmT4KleCx2
@domenkozar@dnouri I don't think tokio calls them that. Async is single threaded and better to not use the word "thread" to describe the execution model probably?
@pfreixes Right, maybe not so different from a monorepo in some cases.
In the end, this is software development and it's all about physical/logical boundaries.
At least with "modular monolith", maybe it will prevent people thinking that every logical boundary needed to also be physical.
@mitsuhiko@dhh it's good to have someone test against orthodoxy at the very least -- show some alternative paths
The amount of hate he gets for benign opinions is wild though
@fulmicoton@antirez It's unfair to pick and choose the cases one language behaves better then another
I do think Ruby has some nice designs but Ruby vs Python is boring
@mauricioaniche I think reality is closer to the fact that people are too lazy to learn the real db layer, write sql and data mappers and not that they are too lazy to understand an ORM
@mauricioaniche I've known many ORMs well, written my own sort of one but now I recommend against them because they usually aren't necessary and just add an unnecessary layer.
A good middle ground is something like python sqlalchemy's table/mapping layer BUT NOT the ORM