Tomte

I agree with all you say, but with longterm I really mean when we've arrived here

> But until Rust is considered a first-class, fully-supported language in the kernel, that's fine

A first-class language whose kernel parts may always break does seem unreasonable. I still think policy will have to change by that point.

Because if in a few years I have a device whose driver is written in Rust, a new kernel version might have simply dropped or broken my device driver, and I cannot use my device anymore. But sure, if R4L wants to stay a second-class citizen forever, it can still be acceptable.

And if no Rust developer has time or interest in those eight weeks? I don‘t claim that it can never work (or it cannot work in the common case), but as a hard rule it seems untenable.

> rust folks should fix the rust binding when C changes breaks the binding

I have never understood how that could work long-time. How do you release a kernel, where some parts are broken? Either you wait for Rust people to fix their side or you drop the C changes. Or your users suddenly find their driver doesn‘t work anymore after a kernel update.

As a preliminary measure when there isn‘t a substantial amount of Rust code, yet, sure. But the fears of some maintainers that the policy will change to "you either learn Rust and fix things or your code can be held up until someone else helps you out" are well-founded, IMO.

Exactly. That’s why I said avoid. Even if you think the AGPL prevails.

You already know that the licensor has his own, idiosyncratic interpretation. He either misunderstands the AGPL (probably clause 7 par 3 b), or he’s trying to deceive you. Both cases can easily lead to hostilities.

> When using iText Core/Community under AGPL, you must prominently mention iText and include the iText copyright and AGPL license in output file metadata, and also retain the producer line in every PDF that is created or manipulated using iText.

https://itextpdf.com/how-buy/AGPLv3-license

Not really AGPL, they just advertise AGPL and mean something else. Avoid.

So it‘s a lie.

I thought everybody already bought Brother, at least for laser printers in private use.

I have a soft spot for HP for reasons, but I‘d never even think about buying their printers (the real HP is Agilent, Philips and probably more companies, anyway…).

Pro: action button

Con(?): 60 Hz

And the price hike again shows that Apple is the master of the "for just a few hundred dollars more, you can get...“ upsell to bigger iPhones.

No, that part is in the law about the armed forces. And I remember distinctly from my compulsory service that we got extensive lectures about the legality of orders and when to disregard them (and report further up the chain of command), with examples.

Open Source projects could sell SBOM fragments with correct licensing information.

"Instead of scanning for copyright notices and license texts yourself, just sponsor us on GitHub and get access to always up-to-date SBOM information by the people who really know what‘s inside“.

I‘m German, I know the pronunciation, thank you very much!

And we Germans do turn the latter syllable into a schwa.

„Ich schwöre, der Bundesrepublik Deutschland treu zu dienen und das Recht und die Freiheit des deutschen Volkes tapfer zu verteidigen, so wahr mir Gott helfe.“

I swear to serve the Federal Republic of Germany faithfully and to bravely defend the rights and freedom of the German people, so help me God.”

David Gerard: Attack of the 50 Foot Blockchain

Oh, it‘s in Lebanon? I think it‘s mostly known for being in Civ 5.

Wait till you see Jamie Oliver…

Alec from Technology Connections has an ongoing thing called "no effort November". Nice idea, doesn‘t work for him, though.

You agreed with your peering partners what to send.

See also https://www.eyrie.org/~eagle/software/inn/docs-2.7/newsfeeds...

> the Parliament building is still called Reichstag even if there is no Reich no more

"Reich" isn‘t a Nazi thing. The building was already called that decades earlier. It goes back to the last German emperor, and Reich actually means empire. The Roman Empire is also called Römisches Reich.

The manual was pretty much a Linux for beginners book. It not only explained installation and basic system administration, but had substantial vim and Emacs chapters, as well as a chapter on retro gaming using emulators. (SuSE 5.3 in my case).

Soo-seh. Like the women‘s name.

Similar: CoDeSys (Controller Development System). They also decided to leave the original meaning behind and rebranded to the all-caps CODESYS.

Why the hell is lunduke not on the HN domain instakill list?

According to the talk it‘s more about Dynamic_Predicates, i.e. arbitrary conditions on a type. He‘s showing an Ada type definition for prime numbers, not just simple subranges.

Ada devroom at FOSDEM: https://fosdem.org/2025/schedule/track/ada/

> clearly being abused here to suppress coverage of, at best, one of the largest security breeches in American history

Worst suppression ever with several front-page threads about it that were not flagged.

Something you also need to understand: there are dozens of "new" developments to a story like this every day. But they don‘t warrant another whole thread.

We have had plenty of those stories unflagged on the front page. There is no reason to have three Musk stories every single day. And no matter how strongly you feel about it, I‘m fed up.

May I recommend Metafilter? They discuss almost nothing else than current American politics, you‘ll feel right at home.

> and now most of their patches have finally gone in.

Is there anything outstanding? I thought they recently reached the point where everything from -RT is in mainline.

He has at least said this to Martin: "How about you accept the fact that maybe the problem is you." (https://lore.kernel.org/rust-for-linux/CAHk-=wi=ZmP2=TmHsFSU...)

I wouldn‘t expect a grand Rust announcement anytime soon, above what has already been said. Rust in the kernel seems to be fine, but it will have to adapt to longstanding kernel processes. And if it means there won‘t be Rust in some maintainers‘ subsystems, so be it. The kernel won‘t be 100% Rust next year anyway.

AsciiDoc is even older than Markdown.