ben-schaaf

Anyone making this claim just hasn't played a lot of factorio, because this just isn't true. Player feeding is fast in the early game, but it just doesn't scale. There's too many buildings to feed and it takes too long to walk between them. People have already made tool assisted speedruns, and as expected it involves building a huge automated factory as quickly as possible.

You don't need an OLED to get poor text rendering on macOS, that came for free with Mojave when they removed subpixel antialiasing.

I agree it's fine and good that they want to sell this and keep it accessible for individuals, but modifying a CC-NC license and then calling this "open source" is not it.

If everyone followed this model instead of open source, then Corridor Key itself would have to cover dozens of software licenses for all it's dependencies.

The execute stage very much modifies state; in fact it always modifies state. Any non-memory instructions modify registers, and any memory instructions either write to registers or to memory. Even a noop will increment the instruction pointer, so you're always modifying a register regardless.

Reading that code there's a 48-bit counter used for each millisecond, so ~281 quadrillion UUIDs per second.

Not sure the point you're trying to make, it sounds like you're agreeing that dumb TVs should be cheaper than equivalent smart TVs?

Monitors have also gotten incredibly cheap, and there's Sceptre who sell dumb TVs that are pretty cheap. So I don't really buy that they're selling TVs at a loss.

That's why Anthropics C compiler worked so well; because they had gcc's huge repository of tests to lean on. Oh wait...

So if you compare a diesel to a petrol-hybrid, and you use the diesel's NEDC rating and compare it to the hybrid's WLTP rating, then number bigger!

Lets make a real comparison: The NEDC combined rating for the 2025 e-POWER is 5.4l/100km (FWD). The 2018 diesel version you linked uses 5.6l/100km, and the petrol 2018 version uses 6.2l/100km.

For a truly fair comparison you could have looked at the non-e-power versions from 2025, which come in at 7.4l/100km.

That's still (usually) the public paying for it. Parking permits are generally hilariously cheap compared to the market value of the land they reserve.

This doesn't ring true. Shit goes wrong all the time, and we put people in the loop to fix things when it does.

Plugins are a frequent culprit of issues like this. Depending on how you're tracking memory usage you may already be able to at least narrow down the culprit by looking at which process is using too much; plugins run on a separate process and may launch additional processes from there.

Unfortunately tracking individual plugin memory usage is not possible without invasive (and slow) tracing. If the plugins are causing big memory usage in the main process it can be hard to nail down due to that state being shared between all plugins.

Most plugins just work in Python 3.14. Python didn't break backwards compatibility that much.

Hard to compare the two programs over a week of uptime. ST memory usage does get larger as caches get filled over time, but I've had uptimes of months without issue. I'd expect similar results from other editors.

Do you have a specific memory issue where it keeps using more over time?