HNHacker News
TopNewBestAskShowJobs

yjftsjthsd-h

35,176 karma · joined December 17, 2016

submissionscomments
yjftsjthsd-h··on Linux was created as a rejection of robust software architecture and tools
> Yeah I think they're conflating UNIX-like general philosophy and Linux.

I don't think they are, actually; they appear to be arguing microkernel vs monolithic kernel, and we have unix-likes based on microkernels.

yjftsjthsd-h··on Linux was created as a rejection of robust software architecture and tools
I am fairly confident that you would find that most people, if offered the chance to take that performance hit in exchange for some security improvement, would not take the deal so quickly as you. Since this is (somewhat) in the context of mobile, I also have to point out that it's also going to be a battery hit and that might be an even harder sell.
yjftsjthsd-h··on Linux was created as a rejection of robust software architecture and tools
> That most of the Linux kernel runs in https://en.wikipedia.org/wiki/Protection_ring 0 should have stopped decades ago

Do you have a way to do it on the hardware people actually have that doesn't destroy performance every time the CPU context switches? You can always move all your filesystems to FUSE if you like the performance...

yjftsjthsd-h··on Linux was created as a rejection of robust software architecture and tools
> Linux was created as a rejection of robust software architecture and tools. It's a monolithic kernel with no internal isolation written as memory unsafe code. A typo in an obscure driver for unused functionality can easily create a fully privileged code execution vulnerability.

Which is, of course, why GrapheneOS is based on minix, right?

Edit: Really, this is just GOS being GOS; only ever Security (by their own very specific, poorly defined definition thereof), with nothing else allowed to be a consideration. There is a reason the industry went with monolithic kernels when other options existed. Even today in 2026, we've merely worked out how to reduce the performance hit of microkernels, and in the 90s Torvalds was very justified in preferring to ship something that would actually run decently on extant hardware.

Edit2: To be fair. I like minix. I have actually tried to make HURD into a usable system. I want these things to work. But there are harsh tradeoffs in play that are still painful even after decades of work, and this kind of post does not exactly convince people that GOS is making level-headed evaluations of technical choices.

yjftsjthsd-h··on Eclipse Mosquitto – An open source MQTT broker
I'd be curious to hear what http server you prefer.
yjftsjthsd-h··on Memory Safety Bugs in Rust Standard Library
> So by that logic we don't count C23, until all C implementers decide to follow it?

I mean. I'd sure be reluctant to depend on it until it had trickled out through the ecosystem

yjftsjthsd-h··on Disk encryption on NetBSD – achieving secrecy
This feels like the reverse of https://xkcd.com/1200/ ; yes, there is some benefit to encrypting the whole disk, but there's nothing wrong with explicitly defining a security model around the idea that $HOME is what matters.
yjftsjthsd-h··on Why get an expensive Pi when I have an old phone?
Have you done this successfully? Would appreciate any notes/prompts you could share
yjftsjthsd-h··on Why get an expensive Pi when I have an old phone?
> Why get an expensive Pi when I have an old phone?

Because the pi has a maintained kernel and a userspace I don't have to fight.

yjftsjthsd-h··on IceWM
> Red Hat and Canonical made their calls, and basically every other desktop environment outside of their control as well.

Thankfully, that's not really how open source ecosystems work. There are still people interested in both using and developing X11.

> Outside of legacy systems, I just don't see why people are going out of their way to get back on X11/Xorg outside of perceived FOSS politics and posturing.

Well, when Wayland supports the features that people use on X11 I suppose we can discuss it. As of the present day, moving "forward" to Wayland would mean massive regressions in a11y tools that I'm not willing to give up just yet, and accepting a fragmented landscape where questions like "how do I change the keyboard layout" or even "is it possible to change the keyboard layout to anything but us+qwerty" are "It Depends™, what compositor do you use" (because Wayland deeply believes in reinventing the wheel over and over again, forever).

yjftsjthsd-h··on IceWM
Yes, X11 is a protocol, which is still slowly developed by adding extensions to it. Whether it does or doesn't need to be actively developed is a question of what features you do or don't think it needs.
yjftsjthsd-h··on IceWM
screen is a terminal multiplexer that at some point added the ability to split the terminal in a tiling manner, but that's a lot more recent than 1987
yjftsjthsd-h··on No AI Slop: A Manifesto
I, personally, would certainly argue that those should be done in small PRs. If you have a working application and want to rewrite in rust, I would expect it to be done by replacing individual components one at a time while making sure relevant tests keep passing. If you're making a new application, I would expect it to be built incrementally by adding parts incrementally.
yjftsjthsd-h··on IceWM
> X11 is not actively developed, a fork is.

Xorg is not actively developed. X11 is fine.

yjftsjthsd-h··on IceWM
> Freedesktop just wanted to kill it for weird reasons.

I wouldn't wish to defend them, but by all accounts the biggest reason is because Xorg's code quality is quite poor, which is (if true) somewhat fair. I wish they tried replacing it without breaking everything and shipping the terrible design that is Wayland, but the goal of replacing Xorg is reasonable.

yjftsjthsd-h··on IceWM
What package manager installs things via curl|sh?
yjftsjthsd-h··on IceWM
I'm mildly bemused at the other comments treating this as a blast from the past. I use icewm today as a super low resource DE for a headless remote desktop system, with a major benefit being that it's all in one with no configuration needed; one unit includes panel, app menu, and window manager that work out of the box.
yjftsjthsd-h··on I'm making LLMs work on small and old devices
I'm told that qwen 3.8 27B is good enough for practical programming work, so if that's doable then I could easily see the utility. Or... the biggest qwen I see here is Qwen3.5-2B; is that actually capable of programming or agentic work with code?
yjftsjthsd-h··on I'm making LLMs work on small and old devices
It's technically sweet regardless, so don't take this as even a little bit of negative pushback, but I am curious what the utility of these small models is? Are they smart enough to be useful on practical tasks? What are people doing with them?
yjftsjthsd-h··on A live tree of systemd jobs on the boot console
dinit has most of systemd's advantages without its infinite scope and non-portability
yjftsjthsd-h··on Critical RCE Vulnerability in Apache HTTP Server
The question was how rust would prevent this vulnerability.
yjftsjthsd-h··on A general purpose Apple Silicon layer for x86-64 PCs
You don't even need that, really; just have wine load the PE binary into memory and hand it a bunch of DLLs that use Linux syscalls under the hood. It's less transpiler and more of a funky dynamic linker+loader plus libraries.
yjftsjthsd-h··on Critical RCE Vulnerability in Apache HTTP Server
Depends on exactly what it is that a project is objecting to. For example, here's Nura:

> AI tools have several ethical issues. They require an unreasonable amount of energy[1] and water[2] to build and operate, their models are built in part with heavily exploited workers in unacceptable working conditions[3], usually without consent from or compensation for creators of the source material[4] and oftentimes causing DDoS attacks against FOSS infrastructure in the process[5] (which in turn force the deployment of challenge-based protections and increase cost and complexity of self-hosting for everybody[6]). Furthermore, they are being used to undermine labor and justify layoffs[7]. These are harms that we do not want to perpetuate, even if only indirectly.

( https://docs.nura.eco/policies-and-processes/development/ai-... )

If you really believe that AI tools are automatically unethical because they destroy the environment, harm workers, and constitute an attack on FOSS infrastructure, then it doesn't really matter how the tool is being used. If you just don't want to see code quality decline, then it's probably not a problem.

yjftsjthsd-h··on A general purpose Apple Silicon layer for x86-64 PCs
WINE emulates an ABI, rather than a CPU or such, but I'd happily argue that that's an emulator. (In fairness, though it's not generally described that way, I would call web polyfills API emulation)
yjftsjthsd-h··on A general purpose Apple Silicon layer for x86-64 PCs
Rosetta is an emulator (or, I suppose, a series of emulators), i.e. a piece of software that makes a computer pretend to be another kind of computer. This is also a bit of lower level software that makes a (x86_64) computer pretend to be a different kind of computer (aarch64), in this case, by AoT and JIT translation, though that's an implementation detail. What distinction are you trying to make?
yjftsjthsd-h··on A general purpose Apple Silicon layer for x86-64 PCs
So, basically an emulator layer that doesn't need a host OS? (I'm not really interested in running Darwin, but that's a cool concept)
yjftsjthsd-h··on Greg Kurtzer's Ginux is now a userspace kernel
What existed when Linux was started? It had an obvious advantage over proprietary unixen (being gratis and libre, plus running on commodity hardware), and to the best of my knowledge the only real competition was from BSD, which was at the time under some legal dispute.
yjftsjthsd-h··on Greg Kurtzer's Ginux is now a userspace kernel
The anti-AI crowd uses "slop" as a term for all AI contributions, so yes, trivially.
yjftsjthsd-h··on Greg Kurtzer's Ginux is now a userspace kernel
> All less than Linux process isolation, but still.

.... Right. Exactly. Everything has some vulnerabilities, but if an attacker has to use a relatively rare VM escape, that's a huge win.

yjftsjthsd-h··on Greg Kurtzer's Ginux is now a userspace kernel
But if php is hacked and that's chained with a LPE, we'd like the attacker to get root inside a sandbox where that doesn't mean much.
Page 1 of 34Next →