KerrAvon

HDR support is still a mess with Wayland. Sometimes you can fix it with gamescope but it’s a swiss cheese thing where for example gamescope breaks some controllers in some games with some GPU drivers. Maybe in a couple more years it’ll be “it just works” territory but it’s taking a while to get there.

Wayland is approximately correct in this case and Windows and Mac are behind the security curve for bincompat reasons; window titles certainly leak PII. There should be a way to do it, but it is sensitive information.

Apple continues to be the elephant in the repairability room. You want something that likely won’t need repair ever for its useful lifetime, a current MacBook is worth looking at. Upgradeability, nope.

couple things

- tbh, I think the Amazon deal doesn't matter much in the long run. The damage had been done earlier.

- why give Bezos any more free money? He's already rich enough.

Do a quick web search for "lasseter harassment" before posting stuff about it, maybe?

Topmost link on DDG starts with:

"John Lasseter was accused by multiple former employees and reports of a pattern of unwanted sexualized behavior at Pixar and Disney Animation, including persistent unwelcome touching, kisses, and leering that made staff uncomfortable"

Yes, all of them right-wing chuds.

I've been running a base UDM for a long time without any 2.4GHz issues -- is there something specific that was broken?

Do note that, even if the math works out such that the bank doesn't actually lose money, a short sale remains on your credit history for the subsequent seven years, which makes it very difficult to buy another house during that period. It's not something you want to do if you can avoid it.

Remember that the people running the US government at the moment are a combination of mentally deranged ideologues and Fox News bimbos. There is no actual plan for anything.

Not meaning to single you out specifically, but this entire discussion — all of this license gatekeeping is ridiculous. This is a very cool project, but if the license ruins it for you, there are zillions of open source GPL3 kernels.

I mean, this is not different from bitching about someone writing their custom kernel in C++ instead of Rust, or Zig. It’s not your project! Let people do their own thing! MIT is a perfectly fine license; maybe the lack of zealotry associated with it would even be a positive thing for whatever community might be built around this eventually, if the author is even interested in having other contributions.

I think you’re overreacting, to be honest. Whatever the original intent of the term, “vibe coding” as used does not — in my experience — refer to using LLM assistance for coding in general.

No, “Vibe coding” is a pretty accurate descriptor for the AI slop code dumps a lot of people are putting into PRs now. Maybe it’s acceptable for web UI front ends, but anything people actually rely on needs to be held to a higher standard.

Very general rule-of-thumb: Doesn’t matter if the AI wrote some or all of the code. If you, personally, can explain every line in the PR, and justify its existence, it’s fine; it’s not vibe coding.

Is this anecdata/personal folklore/"common sense" or is this based on science? It sounds like the former, tbh. Things tend to be more complex than this.

Powerful men/women don't have to be sexually or in other ways abusive to subordinates. They really don't. Most of them, in fact, don't. You certainly hear about the ones who do, for a reason.

Nope. Read the emails before discussing, please.

tl;dr: Because there were ongoing investigations (which was true) and it's generally considered bad to release your evidence before trial, or something like that, IANAL.

This will also be Trump's (false) reason for not releasing them.

Swift, by design, does not have GC.

Outside of hobbyist things, performance-critical code is the only responsible use case for a non-memory safe language like C in 2025, so of course it does. (Even that window is rapidly closing, though; languages like Rust and Swift can be better than C for perf-critical things because of the immutability guarantees.)

This. The memory overhead kills you in large systems/OS-level GC. Reducing the working set size really matters in a complex system to keep things performant, and GC vastly expands the working set.

In the best cases, you’re losing a huge amount of performance vs. an equivalent non-GC system. In the worst, it affects interactive UI performance with multi-second stalls (a suitably modern GC shouldn’t do this, though).

Everybody loves Woz, for good reasons, but (a) he’s not a manager (b) he’s not executive material (c) he’s notoriously unmotivated (d) he hasn’t engineered anything significant since what, the mid-1980’s?

Every bit of your second sentence is wrong. None of that was even on the drawing boards when Steve passed away.

usually a combination of money/benefits/locale is the answer to this question

Yes. If you look at the ZILF compiler in particular, which is capable of compiling the original sources, there's a lot more MDL in there than you'd expect would be required for ZIL proper.

This is great illustration of the brilliance of Inform 7.

I understand the appeal of Dialog -- Inform 7 can be really awkward for traditional programming constructs -- but I think I'd rather write ZIL if I'm going back to the usual control structures and OOP-style messaging.

the other thing is that it would not be as effective as presumed because 5G cell service in residential areas in the US is spottier than people realize. A lot of us are relying on WiFi calling.

Nothing against (or for) Zig, but the article author seems unfamiliar with other modern languages in common use... imagine if they saw Swift or Rust. Their mind would be utterly, utterly blown.

Swift is a peer to Rust, not Node / Python. It has some nice affordances that Rust doesn't, while still being a native-compiled language.

In practice, the problem with URIs is that it makes parsing very complex. You don’t really want a parser of that complexity in the kernel if you can avoid it, for performance reasons if nothing else. For low-level resource management, an ad-hoc, much simpler standard would be significantly better.

For one thing, they’re expensive and viral. “Zero overhead” implementations don’t take into account the need for unwind tables. For every function/method that might be thrown across. They’re disabled in a lot of production environments for this reason.

Get back to us if that Dell makes it 10 years without catastrophic failure or pieces falling off.

This is the correct answer. Why wouldn’t an actual AI just generate raw, fully optimized executables for production?