HN user

LeFantome

1,933 karma
Posts0
Comments874
View on HN
No posts found.

I bought a 2013 MacBook Air for $50 two years ago to take on a backpacking trip. It runs Linux and I use it all the time. I had a video meeting on it this morning.

You run OpenCode with Big Pickle on it with decent performance. So you can even vibe code on it for free.

I have been using this for a couple of weeks and it has been very stable. Other than xfwl4 itself, the rest of the desktop has been the released XFCE 4.20 components. Already it is a better way of running XFCE on Wayland than using something like labwc I would say.

It is great to see a release. Hopefully more people will try it and give feedback so it can get into XFCE 4.22 by the end of the year.

Are you trying to tell me KDE requires you to configure wifi at the command line?

No. No, it absolutely does not.

I have used Plasma on at least four different distros in the past 2 months and that has not been true for any of them.

He certainly had to do a bit of heavy lifting but it is great seeing FreeBSD becoming usable on laptop.

I may consider trying to spin up FreeBSD on a non-essential machine just to give it a spin for a bit.

The K3 is a bit slower single core, about the same multi-core, and quite a bit faster at AI.

If you use the AI cores for general compute (eg. when compiling) then it is quite a bit faster than the RK3588.

At times, the above may vary as specific software may be less optimized on RISC-V.

Your ePub Is fine 1 month ago

You know you can use Ruffle if you really want Flash right?

https://ruffle.rs

But the only standard you need is WASM. All browsers support it. Use whatever you want to make it. In fact, Ruffle is just a WASM app.

Debian no longer supports Pentium, so neither does Antix.

There are still Linux distros that will work on it. Adelie should. I think Arch32 as well. And Tinycore.

I am not as sure about Slackware but I believe the single-core (non-SMP) kernel runs on Pentium.

I can see why they wanted to change the "RISC-V is inevitable" line. After you have heard it too many times it starts to sound like end-of-the-world zealots that expect us not to notice that the world has not ended as they have endlessly predicted.

Perhaps "RISC-V is now" will build some excitement. But there is a danger that it will ring even more hollow if we have to say it for 3 years before it rings true. RISC-V is inevitable and, for many use cases, it is soon. But for most people, it is certainly not now. RISC-V is still too slow and too expensive for most use cases outside of micro-controllers.

In the next 2-3 years, all that will change. RISC-V has a real shot at the embedded mid-range where the ARM product line has stagnated somewhat. RISC-V has caught up in performance, has the features, and is perhaps a bit better in terms of vectors and AI. With luck, we will see things like smart TVs and perhaps even phones. Real success in phones may take a few years of slowly chipping away though.

And on the server side, RISC-V has a chance to break-in. It is not going to put Intel, AMD, or ARM out of business just yet but it can start to build share. Specialized AI workflows offer a real opportunity.

For the SBC market, RISC-V is far too expensive given what it competes with. If RISC-V find volume elsewhere, this could change.

On the desktop/laptop, RISC-V is not even remotely a player. This will be the hardest market to break into. But any success ARM has makes it easier for RISC-V to follow. And once they are both there, what is the advantage of ARM again? Certainly not legacy compatibility.

RISC-V is inevitable. And its time certainly "starts" now. But I am not sure that RISC-V is now for most of us.

Is your point that Anthropic is now accepting code submissions to Opus 5.0 from “millions of contributors”? No?

Ladybird uses AI to code. This is not them banning AI. This is them not wanting to take responsibility for the code WE write with AI. They think outside code contributions are raising their risk and slowing them down.

I dislike this change but it does not track to what you are saying at all.

Like always with Open Source, if you really believe what you are saying, fork the project. Outrun them if you can.

Well, technically it is a "company" already as it is registered formally as a non-profit. They have income (sponsors) and paid employees.

To my eye, this change does not appear to be driven by a change in corporate governance or profit motive.

They explain that the change and the timing is driven by two things.

1 - The burden and of processing public contributions has increased with the rise of AI

2 - They need to focus and stabliize the code base in preparation to introduce a public alpha

Those reasons ring true enough for me that I do not need to go looking for other motivations. I do not like this change but I can see why they would.

It sounds like all public contribution will simply be impossible. That said, they will continue to develop out in the open on GitHub and you can clone the repo and build whenever you want. You can continue to contribute in other ways.

https://ladybird.org/#contribute

I hate this change and agree with your PR comment. This change makes me sad as well.

My hope is that public contributions can resume in the future. Part of their justification for this step is that they are trying to stabalize the project to produce a stable public alpha. Fair enough. And many Open Source projects have begun to voice concerns over the burden that the massive increase in contributions is causing, often from AI. Linus Torvalds has certainly been flagging this. The Open Source world in general is going to have to navigate this and come to a solution that works without the entire Open Source ecosystem becoming read only.

Once Ladybird ships a "stable" browser out to the world, I am hoping they can adopt whatever the "best practice" for Open Source has become to be able to accept public participation again.

Not necessarily. I just fixed the Ladybird build process so it will successfully build on a system that uses musl instead of glibc. By far the most compact way of explaining what needed to be changed is to share the changes themselves. It is a set of very small changes to a number of individual files.

Crappy timing for me. Ladybird has never built on musl based systems. I got that working just a couple of days ago (on Chimera Linux) and was hoping to push the changes to the project. I guess I am maintaining that myself now.