And when applicable, the program would be much more efficient than the LLM.
So it would really be beneficial for the LLMs to be able to have their own environments to write and run code, but also to store those programs for later use automatically.
> How is a fictional character the product of someone's mind, but a character generated from a massive database of words from other people's minds is not?
I imagine it's the difference between a chef combining ingredients with intentionality vs a person going to multiple fast food restaurants and blending everything together.
bcachefs was already working at its own pace prior to being accepted in the kernel. It could have continued doing so for years until it was really "ready".
Instead it got kicked out because Kent constantly ignored the kernel's contribution rules and is unlikely it will ever be accepted back into the kernel.
I'd really appreciate it if we could drop the FUD over contribution rules. There are no such rules, it is explicitly Linus's way or the highway, and I already replied to that elsewhere.
And it went in when it did because Redhat was pushing for it and claiming to be supportive - but that never materialized. They wanted to get something for free without investing, or putting in the absolute bare minimum.
A _lot_ of people were saying publicly and privately "dear god yes we need something better than btrfs" - but no one from the existing kernel community was interested in stepping up.
Community's still growing, though. A lot of people have gotten active in making sure bcachefs actually works well for people end to end, and there's a hell of a lot more to shipping a filesystem than just writing kernel code.
You can't let Reddit guide your technical decisions.
The FS was marked experimental, so there is no urgency in fixing bugs or providing features in a certain cycle. Everyone using it knows what they got themselves into. You can still provide the DKMS module for faster fixes and features for anyone who wants to use BCacheFS more seriously for the time that the upstreaming process takes, but eventually it would have all been on mainline.
Asahi is taking a similar approach where they have their downstream kernel and push things upstream once they are mature.
That means the upstream kernel is not useful for running on that hardware now, but things are moving there eventually.
There's a project called "anylinux appimages" that aims to make the most compatible appimages. They also use DwarFS for faster opening and smaller file sizes.
I don't know how this happens to me but i always have trouble with Bottles. And not just the slightly bad UI, but like today, i have an installer that i can run directly with Steam that i cannot get to run in Bottles. When i last used it a couple years ago i did get what i needed working successfully but i remember it being a struggle.
That's exactly what's happening to the Linux git repository. The server constantly has mutltiple CPU cores dedicated to rendering git of various old, dead branches in html for scrapers.
GrapheneOS does include GPLv2 code both via AOSP and our own but not GPLv3. We want GrapheneOS to have no additional restrictions beyond AOSP. AOSP uses GPLv2 but not GPLv3.
We do need to be careful with GPLv2 due to license incompatibilities. For example, GPLv2-only licensing such as the Linux kernel is incompatible with Apache 2 and GPLv3. GPLv3 is compatible with Apache 2 so GPLv2-or-later can be compatible but only by using it as GPLv3 with the extra restrictions too.
It seems like you have more freedom than you think you do. See this comment <https://news.ycombinator.com/item?id=49594824> Packaging software shouldn't change the license of GOS as such. If you haven't had already, maybe the free software foundation could provide you with assurance?
I guess it will make your life much easier if you wouldn't have to restrict yourself that much.
No, we're not talking about packaging software in our app repository (App Store) but rather software being included in GrapheneOS. If any GPLv3 software is included in GrapheneOS then that places more restrictions on how it can be used as a whole.
Would you happen to have a link to this? I would like to learn about this but unfortunately treehouse.systems doesn't seem to be very well indexed by search engines, and Mastodon's search is failing me.
My argument was apple is doing nothing much for open source, then you suddenly come with link that shows Apple has done nothing for open source compared to other company like Microsoft or Google or even Meta.
If you have the will, and the knowledge all of those tools can be used to your advantage but no one has for the most part they want someone else to do it for them for free.
Don't they ship a propetietary clang variant with weirdass version numbers? That was true at least at some point. Fortunately most Mac users on my experiments have given up attempting to compile any code in their Macs after SIP etc made it too annoying so rarely have to support them anymore.
So it would really be beneficial for the LLMs to be able to have their own environments to write and run code, but also to store those programs for later use automatically.
reply