Depending on the database used, the data might still be there, just really hard to recover (as in, its presence is a side-effect, not the intent).
https://stackoverflow.com/a/12472582 takes a look at Postgres case, for example.
Depending on the database used, the data might still be there, just really hard to recover (as in, its presence is a side-effect, not the intent).
https://stackoverflow.com/a/12472582 takes a look at Postgres case, for example.
It’s the language I’m most capable of making a living with. It’s familiar to the point of being boring, I know what popular tools to avoid, I know my way around making Rails get the hell out of the way, turning it into a useful and handy tool.
I do want a chance at something that’s more exciting though. Some of the features I spy in other languages would be so nice to have.
Although I’d recently finally had to solve a problem where Ruby being slow was the major factor. Haven’t had that much fun in years. Benchmarks and second degree lap burns will do that to a person.
Do not solve maintenance problems that you don’t face.
With free time and some rest I’d move to sourcehut.
Gitlab adheres to a “one tool for all the jobs” philosophy and tends to be a performance mess for the end user. Every time I had to use it, I wanted not to.
SourceHut is a counterexample to claims of monolith superiority gitlab makes. Whether it will continue to be that is an open question, but right now it’s quite a joy to use.
If we remove words “serde” and “enum”, no one will be able to guess whether the argument is for rust or golang.