Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: rbowman Newsgroups: comp.os.linux.misc Subject: Re: rPI Goes Public Date: 28 Jun 2024 17:32:04 GMT Lines: 15 Message-ID: References: <666e2a36@news.ausics.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net nBDrgM1DBVR3h7/KuasPTguTUw1M4tij2J2008OmmhYhrNUuxy Cancel-Lock: sha1:/O/brVAYYQntcMzQWF4orrndlU8= sha256:b6BmrZfcu0QMYvH8FJjUjUh98evFKP2n5ciNqbQ+dDg= User-Agent: Pan/0.149 (Bellevue; 4c157ba) Xref: csiph.com comp.os.linux.misc:56603 On Fri, 28 Jun 2024 00:18:29 -0400, 26xh.0712 wrote: > My big gripe though isn't the PI per-se, but the Pi5 reliance on the > not/never-ready-for-prime-time Deb WORM. Four of the five main things > I do with PIs would NOT work with WORM. Went to BeeLink boxes and > Manjaro instead. I can't address Bookworm since I've studiously avoided moving my Debian box from Bullseye. I am running Ubuntu on a BeeLink SER 4 and am happy with it but that model is a AMD Ryzen 7 and not comparable to a Pi. I probably will pick up a Pi 5 at some point primarily to work with the Pico W. I'm currently using MicroPython on the Pico and would install the C/C++ tool chain on the Pi.