https://dd.thekkedam.org/assets/documents/publications/Repor... http://www.bailis.org/papers/ramp-sigmod2014.pdf
3,545 karma · joined February 28, 2020
https://dd.thekkedam.org/assets/documents/publications/Repor... http://www.bailis.org/papers/ramp-sigmod2014.pdf
They just completely swapped out the whole service from the stack and wrote one in Go because of how much better the concurrency management was, and Ceph's team and codebase C++ was too resistant to change.
TrueNAS sort of half-accomplishes this but as soon as you have to start configuring Redis and Postgres parameters to install Immich or understanding how to set permission on every layer of the filesystem so you can SMB share, the idea of a normal person being able to do this goes completely out the window.
My advice is to go ahead and just open-source everything. You won't on being closed-source anyway. You'll win on the experience for nontechnical users (or tehcnical users that don't want to spend time fiddling). You'll stomp out these complaints on Reddit and HackerNews so people don't get a bunch of negative comments when they google your company.
I would suspect this is because it is most mainstream recommendation from economists on how to disincentivize fossil usage without destroying your society & economic stability in the interim. Not because it's "lefty".
The yellow vest protests in France were basically what happens when you try to do A without also doing B.
Having an S3-compatible store was already a fairly heavy dependency in terms of something to run correctly in production, it's just that most people don't even consider running their own object store at any real scale, they just go to cloud. Whereas running your own Kafka is something more platform teams are already attempting.
Obviously you can make a product that only does really good username/password auth for example, but there's always more pressure to implement more things for another use case.
In short, the system should be designed by people that despise the general state frontend development. It should still look good, I love a modern clean frontend (like Docmost for example), but not at the expense of snappiness and scalability.
If it’s just a personal site, you can just let it go unavailable during an outage (and maybe rely on a CDN to keep it partially functioning).
About a year ago when the NYTimes wrote an article called liked "Who really gets to declare if there is famine in Gaza?", the conclusions of the article were that "well boy it sure is complicated but Gaza is not officially in famine". I found the conclusion and wording suspect.
I went looking to see if they would like to the actual UN and World Food Program reports. The official conclusions were that significant portions of Gaza were already officially in famine, but that not all of Gaza was. The rest of Gaza was just one or two levels below famine, but those levels are called like "Food Emergency" or whatever.
Essentially those lower levels were what any lay person would probably call a famine, but the Times did not mention the other levels or that parts were in the famine level - just that "Gaza is not in famine".
To get to the actual report took 5 or 6 hard-to-find backlinks through other NYTimes articles. Each article loaded with further NYTimes links making it unlikely you'd ever find the real one.
But in my day to day I'm just writing pure Go, highly concurrent and performance-sensitive distributed systems, and AI is just so wrong on everything that actually matters that I have stopped using it.