Hacker News new | past | comments | ask | show | jobs | submit login

So you downloaded 30 MB of client side code instead of 100kb. Don't see how that's a win. By "higher quality" you mean placebo (see foobar2000 faq) or some DSP filters?



> So you downloaded 30 MB of client side code instead of 100kb. Don't see how that's a win.

Depends how you're counting. Using that 100kb of code "as intended" essentially requires Firefox (95MB) or Chrome (153MB), or some proprietary alternative.

To use VLC instead, we can get by with something like dillo (1MB) and youtube-dl (1MB), which (added to your 30MB estimate for VLC) is much less client-side code.

(Size estimates taken from packages.debian.org)


Firefox and Chrome are application platforms, like your OS. It doesn't make sense to count them. They don't only run youtube, unlike VLC which is only a media player. Otherwise VLC counts as 20 GB (or whatever) for the OS as well.


Then Firefox and Chrome loose again, though.

Because then you have the 7GB OS + 95MB Firefox + 100kB YouTube vs. the 7GB OS + 30MB VLC + 2MB youtube-dl

And, additionally, the browser is just a document displayer, like a PDF viewer, or an image viewer. 135MB for that is far too much in any case.


From a performance perspective, it is a win. I've used the VLC trick to smoothly play videos on machines which are too old to play them at full frame rate in the browser.


Its already on my system so doesn't get downloaded with each video.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: