upvote
The future is in closed source ecosystems on a modified Harvard architecture
reply
deleted
reply
WTF but I get the point
reply
What happens when somebody tries to contribute based on the last-published commit? Do you merge/rebase their contributions for them?
reply
Haven’t figured out how to deal with contributions going forward…

The issue is that we get dozens of PRs, generating a bunch of code is trivial but reviewing and merging it and making sure it doesn’t break in interesting ways is still pretty hard.

Personally I lean towards not accepting code contributions anymore, but accepting design documents for features and l bug reports etc

reply
How about a strict anti LLM use policy for contributors? It adds what's basically a "proof of human work" challenge to opening new PRs, and effort required to review human PRs usually roughly scales in proportion to the amount of effort required to make human PRs. And human contributors who take time to make a PR manually are probably more likely to become longer term community members and not just drive-by contributors

It's not a perfect solution of course, it just takes OSS back to the fairly broken state it was pre-AI. Still, it might be an improvement and should be at least considered.

reply
We do have a LLM disclosure policy.

I’m not sure how we could enforce an 0 LLM policy in practice though…

reply
Amounts to ‘won’t be getting contributions‘ which is maybe not that bad at this point on the timeline
reply
There's plenty of people who contribute to non-AI open source projects, you just don't get the lazy people who don't want to be a serious part of the project or the people who don't know how to program anymore
reply
I mean, win or not, it has nothing to do with some people freaking out, and that certainly have nothing to do with whether open source have a future.
reply
Not really sure what you’re trying to say; my main point is that OSS is going to change drastically in the next couple years
reply
> Seriously reconsidering if open source has a future nowadays

*In C or C++.

reply
Until we don't replace UNIX clones, Khronos APIs, LLVM or GCC with something else.

C and C++ will stay around for a very long time, even with AI powered systems.

If anything, maybe that is a call that even if implementing compiler backends is hard and time consuming, bootstraping compilers, and new approaches to OS design, are the only path away from such dependencies.

reply
Rust is on its way. Vulkan is no GL, and Gallium it's something else over classical MESA under SGI/Sun.

Legacy 32 bit users with NetBSD and Hyperbola can survive a little with Go based tools/small browsers/mail/usenet/IRC clients and some web browsers with Bubblewrap, but not forever.

reply
Rust being here matters,

https://www.khronos.org

https://vulkan.org/events/vulkanised-2027#program

The only thing closer to it is WSGL.

Also there are much more operating systems than those examples.

reply
rust isn't invulnerable.
reply
A tank isn't invulnerable either, but of someone starts shooting at me I'd rather be in a tank than on a 50 year old bicycle.
reply
Fun fact, Russian soldiers ride on top of their tanks and APCs because its safer than being inside of one during an assault. Doesn't mean you are wrong, but there will always be trade-offs. There is no such thing as perfectly secure.
reply
Tank desant is practiced because there isn’t room in the tank to fit extra people. It’s very much not safer outside of a tank than inside! It’s actually the worst of both worlds, because you don’t have the armor protection but are highly visible. The only advantage it gives over infantry assault on foot is mobility. Which is why it’s generally only practiced when there aren’t sufficient APCs/IFVs available
reply
Fun fact, these specific types of problems aren't possible on a JVM. Yet somehow Java isn't the right language to write a webserver in. These problems are possible in Rust and C/C++. At least its "hard" to have this type of problem in Rust.

Security is hard and is mostly about the number of engineers and amount of time spent looking at a specific implementation. When writing code, do you think about the problems of leaking information due to different operations taking specific amounts of time? That's an actual concern when writing a prod service that uses the network. And it has to be balanced against scalability and issues caused by DOSes. It isn't trivial and it isn't binary...there are always trade-offs. Nothing will ever be perfectly secure and usable and scalable.

reply