Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What does "behind" actually mean, though?

Think about how far Linux has/hasn't come in the last 10 years. The user experience is nicer, drivers "just work" more, there's more support for more stuff...but at the end of the day, the actual computing experience is mostly the same today as when I installed Debian back in 2016. It's polish, interoperability, etc that's improved.

Maybe VR takes off and takes over the desktop, and then openBSD can't keep up with that, but I don't think that's likely. So what are they trying to "keep up" with?

 help



The number of OpenBSD contributors, since 2017 is going down. For all the praise the system gets here, the developer team is small. And feature-wise the system is a toy compared to Linux. It's like comparing DigitalOcean with AWS.

Ppl praise the stance of OpenBSD/NetBSD and what-not. That's commendable, but then close the tab, open their spotify and get back to agentic programming for their proprietary company source. But God-forbid if OpenBSD turns anything more than a museum OS, full of purity but with a user-base of five. Because the GPU doesn't work properly, the sound drive is clunjy, wifi might work, etc.

LLMs could port huge amount of drivers to both system with a fraction of the effort. Specs can be implemented easily and properly. Then of course, you need to test and that takes time, but it's technically easier and more ppl could contribute.

I get the feeling, but they're not OpenBSD a favor, if anything else I feel the exact opposite is happening.


> It's like comparing DigitalOcean with AWS.

As someone who has to professionally deal with AWS's feature breadth, this does not hit the way you expect.


> As someone who has to professionally deal with AWS's feature breadth, this does not hit the way you expect.

Hahaha, fair! I meant feature-wise :-P


> LLMs could port huge amount of drivers to both system with a fraction of the effort

Could, but they don't. Latest Linux versions give compiler/linker errors (undefined references) which speaks great lenghts about the code quality.


Ironically with sloppy code we will be back to 2001 with non-concurrent OSS and shitty sound daemons as esd/arts, now merged into pipewire but with crappy patches around.

Meanwhile OpenBSD will get 9front's GeFS stabilized and it will work on a fraction of what BTRFS needs to function, and don't let me start on ZFS.


> What does "behind" actually mean, though?

In this case, reading the link you're replying under, it's being able to mount a disk formatted with a popular filesystem. The alternative here is waiting for a human to type this relatively "solved" problem, as a procedural requirement, more than anything.

So, it can easily mean "things won't work in this OS". But, that's to be expected with FreeBSD, for legitimately good (from the perspective of FreeBSD) reasons.


Bugfixes, feature implementation, and hardware support will not be able to be added to OpenBSD with the speed that they are added to Linux.

Whether you like this new reality or not, it is an objective fact that LLMs are the silver bullet Fred Brooks told us didn't exist—multiplying development speed by 10x or more—and that if you're not using them you are hobbling yourself. This especially goes for a "security-focused" OS like OpenBSD, because AI is more diligent about finding vulnerabilities and can do so without rest. Meaning that if you're serious about security, you are using AI to harden your software... and if not, someone else is using it to hack you.


> it is an objective fact that LLMs are the silver bullet Fred Brooks told us didn't exist—multiplying development speed by 10x or more

That is not remotely an objective fact. It's an opinion, and it isn't even an accurate assessment of the tech at that.


It's an objective fact.

I'm sitting here watching astra do in a day what would have taken me at least 3-6 months. The code is verified correct. The model finds, reads, understands, and then integrates the latest literature into its designs and plans. It implements the code, proves it correct, and has come up with its own novel solutions on top of the state of the art. It then refines its implementation to hit the performance goals I give it. This is the reality today.


>I'm sitting here watching astra do in a day what would have taken me at least 3-6 months.

I've got some bad news for you.


What’s the bad news, exactly?

That it would've taken you 3-6 months because you're bad at what you do and don't know much. Being 10 times faster and better than 0.05 isn't particularly impressive.

I work in formal verification at a company whose products you've definitely interacted with today. On an average day, I throw thousands of dollars worth of tokens at the SOTA models and have them produce tens of thousands of lines of both proofs and code (alongside proofs of correctness).

We're solving problems now that we never even would have attempted previously. We couldn't have even staffed them if we wanted to. Even if we had the people, it would be years of development before we saw usable results.

If you can't understand how this kind of work would take a human with a few decades of experience 3-6 months, you're the 0.05 developer in my world.


>multiplying development speed by 10x or more

[[citation needed]]


As one example I can think of, there are a ton of devices that only work on Windows (or Windows and MacOS). The audio interface I have is one example: its "official drivers" are Windows and MacOS only. I know that someone is trying to make Linux drivers for it, using LLMs, because if there's one thing LLMs are very good at, it's RE and figuring out how hardware works. One of my other friends made an accessible equivalent to the Razer app for his Razer headphones because the official app is complete shit.

Most audio drivers are Intel HDA bound, they will work almost the same everywhere, it's just about enabling and disabling pins.

Except for ones like those from Universal Audio, or other pro audio audio interfaces, which work over Thunderbolt/USB4...



Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: