

Isn’t there a joke about all languages becoming half baked implementations of lisp?
FLOSS virtualization hacker, occasional brewer


Isn’t there a joke about all languages becoming half baked implementations of lisp?


Not being intimately familiar with modern C++ these days it is almost refreshing to see the process turn down a feature. One of the criticisms of the language is that its so multi-paradigm that you run a real risk of spaghetti codebases if you are not careful to enforce a house style of features used for a given project.
Maybe all long lived languages see this in the end? My day to day is in plain old C and the recent versions of the standard are much more incremental with what they add.
We’ll see how the upstart new languages like rust and zig deal with these issues as they mature. Maybe it’s a case of those who do not learn from the mistakes of C++ are doomed to repeat them?


Open Innovation Network is a patent pool to protect open source projects from patent trolls. It’s basically mutually assured destruction if the pool has any patents covering products you sell.


DisplayLink have always been touchy about their IP and the lack of open source drivers is the main reason I don’t consider their hardware anymore. I guess they want to stop it getting merged so they don’t end up in a patent battle with OIN.


Why wouldn’t I just run Debian Testing? I’m not sure what this is offering.
Didn’t fish port themselves to rust as well?


Have you got any evidence for that? As I understood it the frozen funds are exactly that, frozen not siezed.
There has been debate in Europe about whether to use those funds to support Ukraine fighting now or save them for the rebuilding of Ukraine after the hostilities have ended. There will need to be a lot of rebuilding.
It’s not AI usage in the kernel - it’s the increase in AI to do code auditing that had seen the spike in bug reports. A lot of FLOSS projects are seeing this regardless of their use of not of AI to generate code.


I think the panels on my home are around 20% efficient so this sounds promising.
I didn’t see anything in particular talking about allowing apps which have used AI although they seem to be using agents to do the repackaging.
According to the site it is repackaging upstream binary releases in a flatpak rather than building anything. I guess for example you could point it at the official Krita app image and make it available that way rather than relying on the community flathub build.


Slop has existed before AI but it has lowered the barrier to generating it. Having no AI policies isn’t really working because the slop posters don’t declare it and as a reviewer you don’t want to be second guessing a potential contributor.
We are probably going to move to a policy that allows narrow use of AI tools but emphasises human understanding and ownership as mandatory components of contribution.
I dunno, probably funding the majority of engineers that work on key components of the system.
In my experience having maintainers who are paid means they have time to do the long term work on improving the projects.
Other firmwares exist, even libreboot is a fork of coreboot. The availability of the code is not an automatic invite to start judging it’s authors. The four freedoms are there so exercise them.
Good luck getting the masses to adopt them. Passkeys seem like an improvement on trying to get your average meat brain to remember several unique passwords.
Have you never felt a ladies feet at night? Ice blocks.
Nice, although I’m slightly suss about the extension wanting access to my Google data.


I can absolutely understand some of the objections and I understand why writers and artists are pissed. My code has always been free software so I don’t object to it being in the training sets because that seems fair use according to the four freedoms.
The power usage is definitely a concern but that holds up for all computing. I don’t see people up in arms about inefficient CI loops retesting the whole world for a single line change. Think of savings that could be made!


The phrase vibecode has become totally meaningless. The original use was too “give in too the vibes” and let the agent go wild. There is no indication that is what Linus is doing.
The fact is LLM’s have proven to be good at finding bugs. Suitably constrained they can be diligent and helpful assistants.
The Bun experience is instructive and if that was Linus’ end goal it would be concerning but I don’t see any evidence that any of the Linux maintainers are interested in that sort of wholesale conversion. The good projects with taste will adjust to the new tools and the slop projects will eventually collapse under their own contradictory architectures.
I really must play with some of the modern lisps. I’m afraid most of my experience is with elisp which while it has it’s charms I wouldn’t call a general purpose lisp.