If you understand Postgres's problems so well (though in reality, such problems can occur in many applications, and it's unclear how your rewritten version attempts to solve them), then why not address them in the main branch by becoming a contributor.
Less code and more value.
I'm sick of the fact that every techno-nerd (including me) can create a new level of abstraction, the integrity of which will be proven with foam at the mouth by other people.
Maybe from the client's point of view, although it's more likely a Tamagotchi. But from the server side, it’s more like a whole hippodrome where you need to support horse racing 24/7
AI doesn't do anything fundamentally new; you search for information the same way you used to through Google. The difference is that when you Googled, you understand that responsibility for the end result lies with you. Now, "users" shift responsibility to the "machine," even though they're essentially writing the program's configuration in their own language. Once you take responsibility for what your LLM writes, you'll no longer be so eager to pursue mythical "productivity."
Seems you don't get the difference between framework and library. In practice, the winner is not the “fastest according to benchmarks” tool, around which it is easier to hire people and build an ecosystem, as was the case with jQuery.
I started working with PHP back in 2002, it was cool, the first code I had to study was phpBB. By now I have made about 10 applications that have survived to production. I learned how to configure Linux servers, understand the front-end (sometimes), architecture, security, management and do a lot of things that now usually require a whole team to do.
Nobody usually bothers with logging actions with files, well, that is, it is like that almost everywhere. Downloading files is not a joke, there are many nuances, for example:
- format
- where to store
- logging
- info via headers
https://whatisyorweb.com [email protected]