pkill

joined 1 year ago
[–] pkill@programming.dev 1 points 8 months ago* (last edited 8 months ago) (1 children)

Apparently there are multiple crates but no official toolchain so unsure how that works in practice. You're still limited to either waiting for hours or cross-compiling though since currently the best available RISC-V CPU is quad-core 2.5 GHz (which still looks hella promising, 2 years ago best we had was 1.5 GHz dual-core). This blog post by Drew DeVault goes into detail of how daily driving RISC-V looked like 2 years ago. I suppose these days it looks noticeably better, especially since Samsung and Apple have been eyeing RISC-V adoption due to ARM consortium doing some monopolistic shit with their licensing. But eventually, so far, not enough critical mass was attained and afaik the whole drama mellowed out a bit.

Regarding the energy efficiency, some experimental units managed to even be manifold better at this:

https://arstechnica.com/gadgets/2020/12/new-risc-v-cpu-claims-recordbreaking-performance-per-watt/

But on the other hand, studies involving some RISC-V models show quite the contrary when it comes to energy efficiency, although the thermal performance is much better:

https://link.springer.com/article/10.1007/s11227-024-05946-9

And below is a screenshot from a comparison by Gary Explains using more microcontroller models. So it really depends on the specific model, but it seems like the design of RISC-V has some solid potential to beat ARM in terms of energy and thermal efficiency.

[–] pkill@programming.dev 1 points 8 months ago* (last edited 8 months ago) (3 children)

I agree with you that every proprietary software must be presumed to be a trojan with a backdoor but still some critical, low level free software being decades old C codebases with oftentimes millions of LoC has proven to be a double-edged sword where on one hand most of it is super optimized (just compare launch times of lightdm or GDM to e.g. regreet) but on the other hand by pure probabilistics it's more likely to contain some vulnerabilities accumulated over the years of imperfect code reviews.

Sure I believe it's worth hoping and supporting initiatives that might one day bring us to something like RISC-V smartphone with high level of hardware security that'd run something like Alpine (a minimalist distro) but based on Redox OS. Maybe that'll come true in a couple of years.

But right now GrapheneOS even despite proprietary hardware is the best option security-wise, unless you're willing to tinker with hacking together some RISC-V SBC-based device (which might even have better battery life than most smartphones by up to 60%!), but the optimization of basically any software is going to suck so badly. And forget compiling any Rust code on the currently available RISC-V CPUs. want memory safety? pick something with a VM/GC instead.

[–] pkill@programming.dev 1 points 8 months ago

downvotes only convince me of your class collaborationist naïvete

don't worry, this infantile disorder will pass for most of you as capitalism spirals into further attrocities beyond our imagination

[–] pkill@programming.dev 1 points 8 months ago (1 children)

day of the rope coming

[–] pkill@programming.dev 1 points 8 months ago

Or having to create such abominations which is especially annoying when you find out you didn't need one this time.

[–] pkill@programming.dev 2 points 8 months ago* (last edited 8 months ago)

I mean I get it might be because of being afraid of it being used to train LLMs. But I doubt that it would work, either because they won't be used regardless or because of how federation works, i.e. literally it'd be more efficient if all of the known network instances' operators somehow agreed to include/Lemmy, kbin and all of the microblogging platforms that can federate with Lemmy shipped a robots.txt that blocks known AI crawlers. Probably what would be more useful would be something that e.g. Akkoma and some other AP implementers offer, i.e. message autodeletion.

Also terrible if you want to retain any anonymity even if more people did it, because of stylometry.

[–] pkill@programming.dev 1 points 8 months ago

pretty much, though it's pretty basic in terms of functionality at the moment

[–] pkill@programming.dev 0 points 8 months ago* (last edited 8 months ago) (5 children)

AOSP is not proprietary. Also security is not achieved merely by the merit of being libre, see CVEs for sudo, glibc or Apache HTTP server or even the Linux kernel itself.

And when it comes to proprietary firmware updates, in case of x86 one such notable example is the microcode which is pretty important to keep updated for security.

[–] pkill@programming.dev 3 points 8 months ago

attempting to build a database normalization checker up to 4NF. Also forking some Spotify client and modifying it to work with the Soulseek network has been in my bucket list for a long time

[–] pkill@programming.dev 2 points 8 months ago (1 children)

on Firefox if a desktop addon has no mobile version you can look up how to add custom add-ons collections when it comes to cookie prompt blockers, but ublock origin and adding filters to it work out of the box. Recently also some apps started showing cookie prompts with no option to decline unless you pay, if they can work offline, make them so

[–] pkill@programming.dev 50 points 8 months ago (7 children)

This is a centralization problem. Come and force federation upon my SimpleX server in Iceland!

view more: ‹ prev next ›