Surely there are not so many people building e-commerce sites that server components should have ever become so popular.
I tried with ChatGPT and Claude but both were not able to find a solution that respects the entire specification, especially transforms.
Initially, my expectation was that there must be a library for this kind of thing, but alas.
Sorry that's not more useful and explicit, it was a while back and never went anywhere.
These are valuable skills, though perhaps nowhere near as valuable as they end up being in a free market.
Comparison: I often program in Python (and teach it) - and while it has its own syntax warts & frustrations - overall the language has a "pseudocode which compiles" approach, which I appreciate. Similarly, I appreciate what Kotlin has done with Java. Is there a "Kotlin for Rust"? or another high quality system language we ought to be investing in? I genuinely believe that languages ought to start with "newbie friendliness", and would love to hear challenges to that idea.
That was never my argument. The commenter I responded to edited his comment to add those points after I replied. This was his comment before:
> Companies cannot set prices arbitrarily
[Source required]
Dead Comment
In this particular case it's wage-push inflation. The lowest quintile of workers has seen very strong wage gains among other reasons because of tight labour markets and minimum wage legislation, which on the consumer side prices a lot of people out of the service economy.
[Source required]
Edit: how are you downvoting me? Go look at corporate profit margins now, 10 years ago, and 40 years ago.
If you believe you can hand wave with simplified BS like "Supply and Demand" you probably have some heavy reading on price elasticity to catch up on.
> The software had a limit on the size of the feature file that was below its doubled size. That caused the software to fail
A configuration error can cause internet-scale outages. What an era we live in
Edit: also, after finishing my reading, I have to express some surprise that this type of error wasn't caught in a staging environment. If the entire error is that "during migration of ClickHouse nodes, the migration -> query -> configuration file pipeline caused configuration files to become illegally large", it seems intuitive to me that doing this same migration in staging would have identified this exact error, no?
I'm not big on distributed systems by any means, so maybe I'm overly naive, but frankly posting a faulty Rust code snippet that was unwrapping an error value without checking for the error didn't inspire confidence for me!