Yes I did, and its comments, prior commenting here. I'm aware that some users managed to upgrade successfully but still that does not change what I believe about this rollout.
As with my comment in another tree, no, none of the Elixir core team or Dashbit employees are directly involved with this effort, though they may be advising informally and will likely submit a PR here and there.
They're not even saving any money. Syntax highlighting is a trivial workload, whereas the average SPA spends a lot of time in pointless roundtrips that have the server send more data down the pipe than the SSR equivalent.
That's a good question, without looking into any of the code id say bandwidth cost goes higher when moving away from server side rendering since you have to send the code for client side rending to each client which connects.
You say that, until you’re one of the unlucky people who discover that cloud DBs are just cloud VMs in disguise, and those cloud VMs have network throughput limits.
A fun part of a retro at my company last year was me explaining to a team, “had all of your pods’ requests succeeded, the DB would have been pushing out well over 200 Gbps, which is generally reserved for top-of-rack switches.” Of course, someone else then had to translate that into “4K Blu-Rays per second,” because web devs aren’t typically familiar with networking, racks, data centers…
Serving static files off highly efficient, distributed CDNs is a solved problem. There's no "4K blu-rays per second" when you're talking about gzipped, highly cacheable text data.
If github has a million users visiting it per day on a FRESH cache, and all of them have to download at least 10 megabytes of text data (both of these numbers are far too high), you are at ... 0.015 "4k blurays per second". Yeah I think MS's datacenters will survive.
A single-page app is not serving "static files". It might serve an initial bundle, but literally everything after that is dynamically generated. There's no way you could serve those responses via a CDN.
I guess if you say "we've made the UX worse" instead of "we've reduced costs but made the UX worse" to shareholders, they think of cost savings regardless.
Do you need every record you add/update to the database to be there when you try to read it later or are you ok with a best effort to save that works to some 9x.xxxxx degree but occasionally drops some things?
If it needs to be there, use a a fully transactional database.
It could mean that, or it could mean your user database or where you store your blog comments or your customer's todo lists. Basically anything where you want to make sure all the data is still there the next time you go looking for it.
Latest research (as in only ~2m old) dispels that narrative a bit but not entirely. Looks like spermidine is the autophagy signal but they’re not sure fasting does t always increase spermidine
Also…lifting light weights for like 10 minutes a day at home is a lifechanger in the early days
Early days as in the first ~4 months of the journey (which is lifelong…a formerly obese person will always be highly likely to regain the weight)
It’s a life changer because when you’re at a significant caloric deficit, your body sheds both fat and muscle. When you lose muscle, your metabolic rate drops, also lowering your rate of fat loss
If you lift even a little, your body will hang on to muscle more effectively, making it easier to lose and maintain weight over a longer period
reply