Live data from Hacker News

I've now played with a Raspberry Pi 400 for a week and here are my conclusions

news.ycombinator.com

11–20 of 222 posts

Re: I've now played with a Raspberry Pi 400 for a week and here are my conclusions

#11

Sounds like a neat bit of kit. For anyone unfamiliar, it's essentially an ARM-powered PC, in the form factor of a keyboard. [0] > I was able to unbrick it I know it's a nitpick, but if it can be repaired, it's not bricked. [0] https://www.raspberrypi.org/products/raspberry-pi-400-unit/

From recent usage of the term 'bricked' here on HN I think those of us who consider bricking to at least require use of JTAG to alleviate to have lost the battle.

Re: I've now played with a Raspberry Pi 400 for a week and here are my conclusions

#12

Sounds like a neat bit of kit. For anyone unfamiliar, it's essentially an ARM-powered PC, in the form factor of a keyboard. [0] > I was able to unbrick it I know it's a nitpick, but if it can be repaired, it's not bricked. [0] https://www.raspberrypi.org/products/raspberry-pi-400-unit/

Do we really have to have the “bricked is relative” argument again?

Edit: To be more constructive, how about a definition for “bricked” as “unable to be recovered by the intended users of the device through reasonably expected efforts.”

Re: I've now played with a Raspberry Pi 400 for a week and here are my conclusions

#13

Sounds like a neat bit of kit. For anyone unfamiliar, it's essentially an ARM-powered PC, in the form factor of a keyboard. [0] > I was able to unbrick it I know it's a nitpick, but if it can be repaired, it's not bricked. [0] https://www.raspberrypi.org/products/raspberry-pi-400-unit/

In my opinion if the fix is not know at the time it could be considered bricked, at least temporarily until the fix is discovered.

How would you called a device that meets a fate like that? Stuck? Blocked? Unaccessible?

Re: I've now played with a Raspberry Pi 400 for a week and here are my conclusions

#14

ahhh I'm eagerly awaiting this to come out! Adafruit and PiShop don't have it yet :/

I bought mine from https://www.canakit.com/raspberry-pi-400.html right after release and it showed up quickly (IIRC shipping was from Vancouver).

Re: I've now played with a Raspberry Pi 400 for a week and here are my conclusions

#15
I learnt to program on the ZXSpectrum with "Write Your Own Adventure Programs for Your Microcomputer" [0]

The RPi400 with Pico-8 seems to tick the same boxes, so I got one for my 10yr old. He's loving it. Perfect use case.

[0] https://colorcomputerarchive.com/repo/Documents/Books/Write%...

Re: I've now played with a Raspberry Pi 400 for a week and here are my conclusions

#16

Sounds like a neat bit of kit. For anyone unfamiliar, it's essentially an ARM-powered PC, in the form factor of a keyboard. [0] > I was able to unbrick it I know it's a nitpick, but if it can be repaired, it's not bricked. [0] https://www.raspberrypi.org/products/raspberry-pi-400-unit/

In my opinion if the fix is not know at the time it could be considered bricked, at least temporarily until the fix is discovered. How would you called a device that meets a fate like that? Stuck? Blocked? Unaccessible?

I agree; I think bricked is a fine word for this, even if it's reversible. Once you give up it's permanently bricked.

Re: I've now played with a Raspberry Pi 400 for a week and here are my conclusions

#17

Sounds like a neat bit of kit. For anyone unfamiliar, it's essentially an ARM-powered PC, in the form factor of a keyboard. [0] > I was able to unbrick it I know it's a nitpick, but if it can be repaired, it's not bricked. [0] https://www.raspberrypi.org/products/raspberry-pi-400-unit/

In my opinion if the fix is not know at the time it could be considered bricked, at least temporarily until the fix is discovered. How would you called a device that meets a fate like that? Stuck? Blocked? Unaccessible?

"I thought I had bricked it, but..."

Re: I've now played with a Raspberry Pi 400 for a week and here are my conclusions

#18
I also got one. Really like the physical form factor and the keyboard.

I don't think something like this is ideal for running a full-blown Linux/Chromium/Firefox desktop environment though - it's just too slow for the bloated web sites of today. And using a mouse isn't exactly "sit-in-front-of-the-tv" friendly.

I like the idea of running something like BMC64 ("a bare metal C64 emulator for the Raspberry Pi with true 50hz/60hz smooth scrolling and low latency between input & video/audio") but unfortunately it doesn't work on the Raspberry Pi 400 yet.

Re: I've now played with a Raspberry Pi 400 for a week and here are my conclusions

#19
> Then I accidentally yanked a cable

USB-C is so outrageously bad in this regard. I have a smartphone on my desk, connected via USB3 for debugging. At some point it started reconnecting if I just slightly touch the phone or cable, which is extra fun if it happens mid-deployment.

Re: I've now played with a Raspberry Pi 400 for a week and here are my conclusions

#20
post #16

Earlier quoted context omitted.

In my opinion if the fix is not know at the time it could be considered bricked, at least temporarily until the fix is discovered. How would you called a device that meets a fate like that? Stuck? Blocked? Unaccessible?

I agree; I think bricked is a fine word for this, even if it's reversible. Once you give up it's permanently bricked.

Whether you agree or not, it's incorrect. Common usage of "bricked" has been one thing and not the other for many years.
Post reply on HN