joss82

I am hoping for an AMD treatment and this does not seem to be it, at least not yet: it's targetting a different mechanism. But at least it's great that there seems to be active research in this field.

So apparently they are working on a new game that is not rimworld but using the same engine…

The odds are massively skewed against the existence of such a world, even given how massively fucking gigantic the universe is. To have a human-habitable world, you need:

- Solid rock

- Gaseous atmosphere

- Atmospheric pressure between 0.6 to 70 (!) (depending on gases mix) atmospheres

- Right temperature: between -20C and +40C

- Mix of gases so that CO2 is not more than 0.1% and oxygen 20% or equivalent

- Something to filter hard UV rays: for example ozone layer

- Something to push larger asteroids away or attract them: a large moon for example

- Enough greenhouse-effect gases but not too much (:'

- Relatively strong magnetic field to deflect high-energy particles, but not too strong otherwise it creates radiations like Jupiter's

- Water

- Carbon

- Iode

- Ton of other stuff like Potassium and Phosphorus

- No cyanide and other supertoxic compounds like tetrachlorides

Those are all requirements, miss one and you will die, quickly or slowly.

And this is just to barely SURVIVE. I'm not even talking about niceties like food or electricity.

That’s the exact opposite impression of my recent user experiences of software: slower than ever.

Contrary to what initiatives like the tigerbeetle team is doing with tigerstyle, or the 10 nasa coding rules, code created by llms tends to be verbose and slow.

This backdoor only appears on decades-old VIA C3 embedded x86 processors

In a good way or a bad way?

Hi, Parseur founder here :D

I understand what they are trying to do, but to me it feels like the moment when MongoDB entered the database space, with semi-structured, "flexible" storage format. It has its uses, for prototyping mostly.

But in high-volume, production workloads, giving a structure to the data you extract (what Parseur does through defining the Fields in your Mailbox, basically giving your output data a schema) adds a ton of value, and the larger the dataset, the truer it is.

Usually, you start by defining where you want your data to go, and which structure it should have, before working backwards from here and starting to extract the data. This is the key to automating your document workflow.

I've been working on Parseur for the last 10 years, and OCR has not been solved yet, let me tell you.

OCR still sucks in 2026. Hopefully this might improve the situation but I haven't tested it yet.

There is no mention of the amount of fuel used to transport the fuel in the article. From what I know it’s a tiny fraction: boats are efficient at transporting stuff (slowly)

That is not what I understood from the article. What I understand is:

Fossil fuels are 40% of freight tonnage, but transporting them fuels is responsible for 50% of the total freight fuel consumption.

I assume 99% of freight uses fossil sources as fuel.

Yes, this is also my feeling.

It happens for every single Anthropic release. Then I try it on real dev and the result is laughably bad. Except in design where it has been doing a decent job for a while. I am not a designer and my bar is pretty low.

Thank you for this answer, it saved me hours of experimenting.

And bonus points for bashing MongoDB, of course. Every single project that I worked on where MongoDB was used, also had MongoDB as the single largest constraint and operations time sink.