notimrelakatos

> I suspect the one problem that will be difficult to solve is elegance and abstraction.

The fact that this industry was able to sustain itself for so long and not actually get this is a miracle in itself. This is what ruined OOP when it became just managements lingo and it'll probably happen again with tools like ChatGPT, we are just going to vomit code in a faster (and cheaper) way.

A few rebellious souls will soon realize that domain modelling and writing correct code is hard, they'll end in the usual places that already exist today, by working in some niche company that applies pure FP or proving theorems in Lean/Coq/Agda.

> These people have no real knowledge of history

That's a kinda naive take, the ones actually writing those theories know history pretty well. Marx rewrote all history fit his dialectic, the same is done by his children because it really works, rewrite the past to influence the present and get the future you want.

> it makes the difficult things possible, and that's what we needed

Indeed, the problem of just saying "you don't need k8s" is you may accidentally invent an even worse in-house version of k8s.

> The argument that digital gold has no value outside of speculation usually comes from people in rich developed countries with a strong financial system

Some developing countries even have shitcoins as their official currency, like the Brazilian Real. So for us crypto comes almost naturally.

They are stupid, but rich people sometimes wear them for a reason, if they ever get stranded in a messy situation and their wealth is confiscated, they can still sell their watches and other miscellaneous items to bootstrap themselves outta poverty zone.

Unstable (most often than not) is almost an exact copy of the latest branch, which means it has most of it's packages updated to latest version. Given the nature and abstractions of NixOS, unstable ends up being way more stable than most distros, you also get rollbacks for free.

Behind the pretty facade there's a hyper competitive environment inside the JS community, sometimes with very low stakes. What's the incentive to fix fundamental issues if the metrics for success are stars and forks?

The best way to avoid their insanity is to use JS as a target language, pick some of their good tools and move on with life, working with safer languages.

Dear lord, this hits too close home, I've been having nightmares maintaining some Azure infra lately. I'm not a cloud-provider fanboy, they all suck at the end of day, but Azure is the one that deliberately makes my life worse every day.

All those features and no decent integration between them, unless you're a multi billion 100k employee company you'll have no luck with their customer support either.

Indeed, I've once met someone who migrated a COBOL project to Java, the biggest complain wasn't even the Language itself, but extracting business logic from a 40-year old spaghetti codebase. Sometimes bugs where part of the business logic itself and other developers who consumed the monstrosity had to make corrections on their side.

Seems to be that "what would happen if NixOS and Qubes had children" scenario. Glad to see Nix propagating itself, the fundamental ideas are right, maybe what we need is different people trying to implement more stuff atop it, so even if NixOS dies the ideas live on.

Formal methods seems to be perfect for verifying protocols, specially finding design flaws, here an example of an ongoing effort to verify TLS

https://www.mitls.org/

https://github.com/project-everest/mitls-fstar

You are always paying Microsoft, one way or the other.

In the 2000's you had people getting paid 6-figure salaries to just "program" in HTML, that was, of course, before the dotcom bubble burst. This seems to be a modern response to the same kind of developer that's been popping up for the last 10 years, all the fuss over the newest shiny tools will never replace good fundamentals, and most of this fear comes from the fact that people know their fancy frontends/APIs are glorified glue code in messy codebases. There are still systems today that'll require knowledgeable people to maintain for decades to come. The MS Word example is the best part because it'll reduce my free IT consultancy to parents/friends.

Look at your work as a craft, invest time into getting incrementally better and you shall know no fear.

> But it seems even after being a react god master you will still be x10 times less productive than an average rails developer for developing an everyday feature.

This is a very enlightening point, maybe because the creators of React can afford to pay for unproductive gods, and those crazy assumptions are accidentally embedded in their tools, unlike rails, which was built by a guy trying to solve problems in the optimal way.

The real issue is when such tools become the standard for everyone else, and this often happens because giant corporations have the capital to push their bullshit, just to make their hiring process easier.

Not paying taxes to a corrupt managerial elite is one of them

Job hopping is the perfect strategy for mediocre developers in this "bull market", if done quickly you'll only tell stories of glory, never having to deal with your bad decisions long term.

I'm not saying only bad developers do this, but there's an extra incentive for them to do so and increase noise for recruiters.

I look forward to the bright future were I have to maintain messy code from AI Rockstars.

I'd rather see the culture that gave us the Ramayana, Mahabharata, Vedas, Upanishads, Algebra and many more outstanding creations have it's own way of doing capitalism, or whatever the heck they end up with, than having a another copy of the US, with more curry and funny accents.

This new Americanism seems like the cultural incarnation of entropy, whose sole purpose is desertify culture itself.

> Is Google inconsistent, or has their policy on how to deal with these things changed over the past few years?

Nope, they're being very consistent if you use the correct ideological goggles, change Bobb's color palette and first name a little and we would have another Damore-like shitshow.

I've been using NixOS for 2 years now, my general impression is that even if Nix isn't the popular solution, it'll probably inspire the right way of doing things for the next years. It might not look like much, but representing the whole system's dependencies as a Graph database, then using a purely functional language to define such database has happily prevented me from shooting myself in the foot many times over the past year.