@betelgeuse93 @itsfoss OFC the main benefit of a #Pi5 with 1GB isn't for #consumers but #industrial customers.

• #Broadcom uses @RaspberryPi / #RaspberryPi as a "#GatewayDrug" to ease #embedded systems designers/integrators into #ARM / #ARM64 systems and get those big enough to want something custom to contact Broadcom.

Also in many systems like #automation, 1GB is more than sufficient (Given that @OS1337 can run on 32 MB RAM in a VM) it's safe to assume the $5 in shave without MOQ is worth it for most buyers who want the extra compute power and I/O compared to a #Pi0W / #Pi0W2 or #Pi3B+ ...

@0x47df I still think the OG #RaspberryPi is good.

• OFC the #Pi0 / #Pi0W & #Pi0W2 are way better options unless one needs Ethernet but even with a USB-Hub integrating it they're smaller...

@r @fluffykittycat @flower Obviously people have used the #RP2040 for many projects and given it's ease of programming, low price, excellent documentation and easy availability it's no wounder it does put pressue on #ATmega / #ATtiny, #Arduino, #Teensy, etc.

• At least for low volume productions and prototypes as proof of concept.

#RaspberryPi shure are more and more targeting #embedded & #industrial clients given they do in fact disrupt the market as one can get proper #documentation and #tools without paying $$$$ upfront (AND sign NDAs) just to be able to boot #Linux on it.

• And competitors fail at understanding that this makes #Broadcom look good and is their entry-way into acquiring new clients. Because selling hardware purely off specs may work in #amd64 land where shit's legacy and the way things work is so entrenched that basic stuff just works as in booting. #ARM and even #ARM64 fail at having that level of #standardization.

OFC the #Pi0 / #Pi0W / #Pi0W2 doesn't need to innovate since every competitor isn't even trying to compete but merely farting out boards with 0 documentation and some halfassed boot images and no post-sales support so they keep dominating by virtue of being the only ones that just work...

@jgoerzen yeah, in terms of absolute low power draw there may be something more power efficient than the #Pi0W2 (basically a cut-down #Pi3 A+) and #Pi0 / #Pi0W (a cut-down Pi 2 Model A)…

• There should be lower power consuming yet more powerful (or at least more powerful at the same power draw) options already due to snaller structural width.

• After all the Xbox 360 went from 203W to 120W during it's lifecycle despite getting the Kinect as additional power-drawing accessory burdened on.

Problem is that so far no "competitior" even came close to #RaspberryPi when it comes to #documentation.

• Like most of the time they just randomly release some #Android / #Linux image and tell buyers to 'feck off' when it comes to reproduceable builds or mainline #LinuxKernel support…

Whereas even some "old" 14nm node'd #ARMv5r11 or #ARMv7 / #ARM64 we'd all expect something that delivers a desktop @ 2W TDP like the Intel Atom x5-Z8350 did over a decade ago!

@landley @lmemsm thx.

• I really appreciate your efforts and espechally #documentation as it makes it so much easier...

There's a reason I only considered architectures to build @OS1337 against that are "obtainable" and I'll prioritize those that I have in my possession and that can be cheaply acquired, which as of writing are about 12 build targets across 5 distinct ISAs ( #i486 and up, #amd64, #ARMv5r11, #ARMv7, #ppc64) , with only 1 (#i486SX) being currently in focus and the next one being the #Pi0 / #Pi0W who's code will run (abeit not performant) on the #Pi0W2 as well...

• All 3 #PiZero|s can be had for like €100 in total with shipping and SD-Cards so it's on-par with a useable #amd64 machine like a #ThinClient with proper SSD and RAM...

Also unlike any other #SBC manufacturer @raspberry_pi / #RaspberryPi actually write proper #documentation and not just fart out some random bootable image file and tell users to feck off!

#OS1337