Profits over productivity. If replacing people with AI, as impractical as it may be, leads to higher profits then CEOs have an obligation to do so. Poverty, sickness, and homelessness are none of their fucking concern.

The other day I asked an llm to create a partial number chart to help my son learn what numbers are next to each other. If I instructed it to do this using very detailed instructions it failed miserably every time. And sometimes when I even told it to correct specific things about its answer it still basically ignored me. The only way I could get it to do what I wanted consistently was to break the instructions down into small steps and tell it to show me its pr.ogress.

I’d be very interested to learn it’s “thought process” in each of those scenarios.

I’m finally starting to pull the trigger on dumping Google (specifically because of this event). For me at least it’s been a combination of, “They’re not that bad,” and, “This is basically like moving to another state.”

The guides I’ve seen lately about what replaces what is a good start but there should really be more in-depth guides for either moving over your data or just how to get started. Just naming alternatives is about as helpful as suggesting “raising chickens” as an alternative to high egg prices.

Cool idea! AFAIK emails are just sent as text but the client renders them when you read them. Theoretically it wouldn’t be hard to send markdown and add a header that indicates the body is markdown. Hard part is integrating support into the client. Since HTML is more verbose than markdown, and you can often mix markdown and HTML, this could actually lead to space and data savings!

I’d say it’s the tooling that sucks more than anything. I’ve had installations fail because of bad caches (and resolved it by doing things NPM advised me not to do), installations that take forever and seem stuck on one dependency, conflicts with ES and Common modules, node_modules folders that dwarf other folders in size, nobody makes proper use of devDependencies, some odd dependencies on Java or Python, and so on. I think the ease of learning JS has done it a disservice as you get millions of devs contributing but not all are trained as devs or computer scientists and you get a flood of libraries that all do the same thing and often even reproduce built-in functionality.

I really do enjoy coding in it more than any other language but when it comes time to run or build is when my rage kicks in.

Wait… what were we talking about? Oh, yeah.

Shitty web apps aren’t really the fault of the underlying tech. This is a problem of design and I don’t think the programming language really has much of an effect on the usability.

This is why renewable energy isn’t just for energy security, it’s for national security.

Jokes aside, nothing wrong with rewriting in Java. It is well-suited for this kind of thing.

Rewriting it in anything without fully understanding the original code (the fact they think 150yo are collecting benefits tells me they don’t) is the biggest mistake here. I own codebases much smaller than the SSA code and there are still things I don’t fully understand about it AND I’ve caused outages because of it.

Not only that, but their business model doesn’t hold up if they were required to provide their model weights for free because the material that went into it was “free”.