And you immediately lose the ability to do `crontab -l` on any server to know its scheduled tasks.
Now you get to look around the myriad of places where you can put systemd files, and figure out which ones are base services and which ones are custom, with no general convention to go about it. Nope.
While the incident did happen, a lot of actions were taken and most of the data was recovered.
OVH now also keeps backups even for clients that don't pay for it.
I was hit by that datacenter catastrophe and got my data back almost immediately, in a new VM.
I've been using them for years with little issue (no more than happened on my AWS or Azure accounts, I would say less because it's less of a mess in general).
First of all, ruby-lsp does a great job at this, and the recent Herb helps with frontend templates.
This is enough to navigate between controllers, models and libs, unless you're trying hard to be clever which you shouldn't.
Then, in Rails, things have a canonical place in the codebase, that is consistent between codebases.
This is in contrast to languages and frameworks where every codebase is setup differently, but the static typing helps find code wherever it's hidden without pain, and thus without need for cleanup and thoughtful design.
To each their own, I prefer power for me, and pain for whoever drifts from the convention.
This is a massive change for cache in webapp templates as it makes their rendering more stable and thus more cacheable.
A key component here is that we are trusting the user's browser to not be tampered with, as it is the browser that sets the Sec-Fetch-Site header and guarantees it has not been tampered with.
I wonder if that's a new thing ? Do we already rely on browsers being correct in their implementation for something equally fundamental ?
As history showed us numerous times, it doesn't even have to be the best to win.
It rarely is, really. See the most pervasive programming languages for that.
Which is a shame really because if you want something simple, learning Service, Ingress and Deployment is really not that hard and rewards years of benefits.
Plenty of PaaS who will run your cluster for cheap so you don't have to maintain it yourself, like OVH.
It really is an imaginary issue with terrible solutions.
Now you get to look around the myriad of places where you can put systemd files, and figure out which ones are base services and which ones are custom, with no general convention to go about it. Nope.