![](https://lemmy.world/pictrs/image/8365f36c-52fd-4996-9b50-6924ae68708d.webp)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
RISC-V is not proprietary enough.
RISC-V is not proprietary enough.
So if I’m developing a garage door opener using ESP32 RISC-V module, I’m not a RISC-V developer? The dev tools and the cross-compiler only come in x86_64 variant, they simply won’t work on RISC-V laptop. But at least they provide a Linux installer.
The only use case I can think of is to build Debian packages on a target architecture without cross-compilation, because many packages do not support cross-compilation, but it’s more an issue of poor build scripts.
Targeting developers is, I dunno, misses the audience. It would have been a great netbook, or a Raspberry Pi replacement.
If I develop something for Risc-V arch, it is probably some embedded thing with 100 MHz CPU and 2 Mb RAM, and I am cross-compiling it anyway on my more powerful PC.
Go on and put AR-15 on your flag, be like Mozambique with AK-47 on their flag.
Nope. They don’t care about privacy, as long as there’s no lawsuit.
TIL someone ported the collection of classic Linux screen savers to Android.
I’m in the same boat, I have (or rather had) published a few Android games which I don’t have time to update anymore, and Google had been unpublishing them one by one.
It’s not the same without two little screws jangling about
Because TeamViewer will set up a port forwarding and a NAT traversal for you.
VNC and RDP only work when your host has a public IP, or you know how to set up a proxy.