The last one was plain old dodgy rust code.

This OpenAI RAM buyout really was a “If we’re going down, we’re taking everyone with us” move.

The problem is PRs / CI tooling. They treat a repo as an independent project, but…:

• A change needs to be able to span multiple repos
• …or you need a way of expressing dependencies between changes in multiple repos
• …and you need to be able to block changes to dependencies that should be non-breaking but aren’t.

Zuul CI solved a lot of these kind of problems for the Openstack project but I’ve personally found it a bitch to setup. Lots of good ideas in it though.

So where are the regulators right now? Oh yes, they’ve all been completely gutted by the governments.

All the lights go out on mine when it overheats, and then there’s a puff of white smoke.

Unbounded capitalism is for sure.

I would say “AI” makes a good poster child for what to fight against. It embodies a lot of what’s wrong.

It’s good for optimisation problems, where you have a complex high-dimensional space to search and you’re solving for some measurable quality.

It’s already there for most of us. It only a few rich companies getting richer that’s making the line go up.

No advantage over Arch IMO.

If you want to play with it, setup a VM.

I call it the Labrador method.

All your codebase belong to us!

Nvidia is less speculation that the other companies mixed up in this. They at least sell physical goods which they’ve been shipping.

Microsoft, Google, X, Meta - Oh boy!

The stat that’s going around at the moment is that 30% if the GDP is transactions between the “Magnificent 7”. That one is fair because it’s economic activity.

The underlying economy is in recession with the AI frosting on top pushing it to break even levels.

He doesn’t want to go to sites that are ad supported. He wants to support sites that don’t get their funding that way.

Yes ed begat sed, but sed works differently. It didn’t replace ed. It did a different job.

Ed loads the file into a buffer which you edit in a random access fashion and then save. Sed collects a list of commands and then streams the file line by line, executing the commands as they match lines. In your example nothing happens until you’ve entered the whole editing script.

ed and sed arre different things. One edits files in place, interactively. The other edits streams i.e.batch processing.

ed is the precursor to vi. Similar commands. It’s just you can only work on one line at a time.

…but what am I going to do while it’s compiling?

“We’re basically holding the planet together — and it’s not untrue.”

So he admits that it’s a bubble set to burst.

“unable to contact server” would do. It tells me it’s not a problem on my end.

A decent error message would have been useful.