I think LLMs have solved that for Nix. I recently moved my homelab from an Ansible/Debian setup to NixOS. As long as I understand at a high level what Nix is and what problems it solves, I can let the LLM deal with the configuration language.
I started the project when ChatGPT 4 was first released, using it as a way to explore what LLMs could actually do. I also find working on it very relaxing, there is something cool about uncovering secrets hidden in code for more than twenty years.
The main advantage of an ORM isn’t query building but its deep integration with the rest of the ecosystem.
In Django, you can change a single field in a model, and that update automatically cascades through to database migrations, validations, admin panels, and even user-facing forms in the HTML.
I'd have to try this for myself before judging it. Apple's CoreData tried and miserably failed to do this, and I wasn't fond of the Laravel ORM either, but Django is probably a better example than those.
FastAPI/SQLAlchemy won’t be more scalable than a typical Django setup. The real bottleneck is the threading model, not the few microseconds the framework spends before handing off to user code. Django running under uWSGI with green threads can outperform Go-based services in some scenarios, largely thanks to how efficient Python’s C ABI is compared to Go.
Django works perfectly with green threads. It’s a superior model to async and avoids the whole function-coloring mess. I’ve seen Django setups outperform Go-based services running under similar conditions.
JavaScript is a terrible language and should only be used when there’s absolutely no alternative, such as in browsers.
In Brazil, you are expected to bring food or drinks when you are invited as a guest to a party. If you stay until the end, you are also expected to help clean up the place. Guests will often take over certain parts of the party without even asking, such as preparing drinks, taking care of the barbecue, serving people, or going to the store to buy more drinks.
That's why I still use two editors: IntelliJ for when doing "serious" work and Sublime when I need to edit random files or a huge JSON. I don't need anything in between.
I work with Node every day, and the library ecosystem is a nightmare. Just keeping a project from falling apart takes a huge amount of effort. Libraries are either abandoned when the author moves on, or they push major releases almost every month. And there’s a new CVE practically every week.
Python libraries are much more stable and reliable.
> Just keeping a project from falling apart takes a huge amount of effort
I think the culture of importing libraries with lots of dependencies is a big contributor.
> Libraries are either abandoned when the author moves on
This applies to any OSS project. Generally speaking popular abandoned libraries get forked.
> or they push major releases almost every month
This sounds like a very bad library to use. I would not recommend having this type of library as a dependency in Node or even in Python for that matter.
> Python libraries are much more stable and reliable.
Not sure what would make python libraries magically more stable and more reliable. Maybe libraries with minimal dependencies would could be the reason. That is why I recommend 0 or minimal dependecy libraries for node.
I work with both node and python. I agree with you on node, it is a dependency disaster. But regarding python the problem is not with the libraries themselves but in the circus of pip vs conda vs poetry vs pipenv vs uv vs ...
I’ve been building web apps since the ’90s, and I never understood the appeal of PHP. It was always a terrible language, and there were usually better alternatives available.
