Loroco y queso!
lemmyng
Flatpak is for GUI applications. For CLI tooling the distro package managers are still the way to go.
So... Crank?
I still have my HP 48 series calculator. It's a sturdy beast.
That's essentially Vivaldi now.
I've seen it successfully happen due to licensing costs and cloud migration (MSSQL->Spanner), as well as for scalability reasons (vanilla postgres->cockroach). The first one was a significant change in features, the latter did sacrifice some native plugins. In the first case the company was using vendor specific features, and rewrote the backend to fit the new vendor.
There's vendor agnosticism, and then there's platform agnosticism. Writing your code so that it's not tied to one specific implementation of postgres is fine, and lets you use a compatible drop-in. Writing your code so you can swap MSSQL for Oracle or Aurora or whatever at will does not make sense. In every case of attempted platform agnosticism I've seen they ended up abandoning the project within a year or two with nothing to show for it.
A pillow. 24h nap here I come.
You can blame Google for that. Their algorithm is built in a way that any page that doesn't follow a certain format just won't rank high, and that format doesn't fit "just the recipe" pages.
And wider and unobstructed FOV is a pretty compelling concept.
That's the problem - you're replacing a window with a camera. Some rain, dust, or a bike rack, and your view is now worse than the window.
It's commented out... Remove the #
As a follow up: if the answer is "yes, it's still the same ship" then one can ask: if you take all the original parts and build a ship with them, is that the same ship as well?