Live data from Hacker News

Raspberry Pi 500 Delivers Great Performance, Convenient Upgrade to the RPi 400

phoronix.com

11–20 of 30 posts

Re: Raspberry Pi 500 Delivers Great Performance, Convenient Upgrade to the RPi 400

#13
post #5

Can it play youtube videos without saturating the resources yet? This was a major problem with Pi 4/400, I had to resort to quite an extreme overclock and some hacky custom browser builds to improve this. Bought it for a family member new to computing. I was put off so much of the 'pi as a basic desktop computer' that I wouldn't buy another for this usecase. Never did make sense to me why it struggled so much with a…

my main problem with the raspberry pi 4 8GB as a desktop PC is that first, the 8GB model is not exactly "cheap", and by the time you add all the extra stuff needed to make it usable (power supply, case, heatsink, fan, good sized of quality microsd card, etc) it costs well above a hundred bucks... And for $100 I can go to ebay and get a used dell small form factor desktop with a core i5-something quad core cpu, 16GB R…

Yes there's some really good used PC deals on eBay. I really like some of the $350ish options.

Re: Raspberry Pi 500 Delivers Great Performance, Convenient Upgrade to the RPi 400

#14
post #7

Earlier quoted context omitted.

That depends on the video, too. There's a bunch of different codecs in use with YouTube videos. Some of them are more intense than others to decode. It'd be nice if it was a user preference on YouTube, wherein: A user could say "VP9? Lol, no -- there's no way that's gonna work. How about h.264? I know I can play that." But it's really not that way even though it should be. Instead, we get a vaguely-meaningless way to…

Extension can do that! Enhanced h264ify or something let's you choose exactly the codec you want

Can confirm—I use enhanced-h264ify on my x230 and it works a charm for watching YouTube without nuking the performance of everything else

Re: Raspberry Pi 500 Delivers Great Performance, Convenient Upgrade to the RPi 400

#16
post #9
post #7

Earlier quoted context omitted.

That depends on the video, too. There's a bunch of different codecs in use with YouTube videos. Some of them are more intense than others to decode. It'd be nice if it was a user preference on YouTube, wherein: A user could say "VP9? Lol, no -- there's no way that's gonna work. How about h.264? I know I can play that." But it's really not that way even though it should be. Instead, we get a vaguely-meaningless way to…

>It'd be nice if it was a user preference on YouTube, wherein: A user could say "VP9? Lol, no -- there's no way that's gonna work. How about h.264? I know I can play that." No need for a user preference. There's an api that allows the site to query how well a given codec would work. https://developer.mozilla.org/en-US/docs/Web/API/MediaCapabi...

Perhaps there is.

The trouble, then, would be that YouTube's implementation is either broken or nonexistent. (We can tell this because if it did exist and did work well, then there would not be complaints.)

Re: Raspberry Pi 500 Delivers Great Performance, Convenient Upgrade to the RPi 400

#17
post #12

Warm memories of the Amiga 500 came up. :) https://en.m.wikipedia.org/wiki/Amiga_500

I believe there would be a market for themed keyboards designed after vintage computers with RPi module carrier boards. This is kind of the heir of the BBC micro and if love one with a black top, white bottom, and red function keys.

Clockwork Pi has one modeled after a TRS-80 Model 100, but it's a bit too small. A full sized Model 100-like would be super cool.

Re: Raspberry Pi 500 Delivers Great Performance, Convenient Upgrade to the RPi 400

#19
post #16
post #9

Earlier quoted context omitted.

>It'd be nice if it was a user preference on YouTube, wherein: A user could say "VP9? Lol, no -- there's no way that's gonna work. How about h.264? I know I can play that." No need for a user preference. There's an api that allows the site to query how well a given codec would work. https://developer.mozilla.org/en-US/docs/Web/API/MediaCapabi...

Perhaps there is. The trouble, then, would be that YouTube's implementation is either broken or nonexistent. (We can tell this because if it did exist and did work well, then there would not be complaints.)

Are we sure the browser is reporting it correctly?
Post reply on HN