←back to thread

798 points bertman | 1 comments | | HN request time: 0.216s | source
Show context
Tabular-Iceberg ◴[] No.45899963[source]
I remember when QuickTime came out in 1991 and it was obvious to everyone that video should be copied, pasted and saved like any arbitrary data.

It's absolutely insane to me how bad the user experience is with video nowadays, even video that's not encumbered by DRM or complex JavaScript clients.

replies(13): >>45900417 #>>45900487 #>>45900707 #>>45900818 #>>45900981 #>>45901051 #>>45901059 #>>45901071 #>>45901279 #>>45902069 #>>45902135 #>>45903125 #>>45903505 #
usrbinbash ◴[] No.45901071[source]
> It's absolutely insane to me how bad the user experience is with video nowadays

Has nothing to do with video per se. Normal embeddings, using the standard `<video>` element and no unnecessary JS nonsense, still work the same way they did in the 90s: Right click the video and download it, it's a media element like any other.

The reason why user experience is going to shite, is because turbocapitalism went to work on what was once The Internet, and is trying to turn it into a paywalled profit-machine.

replies(6): >>45901097 #>>45901124 #>>45901236 #>>45901343 #>>45901729 #>>45902520 #
jsheard ◴[] No.45901343[source]
Plain <video> elements are easy to download, but not great for streaming, which is what most people are doing nowadays. Much of the JS complexity that gets layered on top is to facilitate adaptive bitrate selection and efficient seeking, and the former is especially important for users on crappier internet connections.

I'm not a fan of how much JS is required to make all that work though, especially given the vast majority of sites are just using one of two standards, HLS or DASH. Ideally the browsers would have those standards built-in so plain <video> elements can handle them (I think Safari is the only one which does that, and they only do HLS).

replies(2): >>45901896 #>>45901919 #
jsmith45 ◴[] No.45901896[source]
Chrome has finally just landed enabled by default native HLS playback support within the past month. See http://crrev.com/c/7047405

I'm not sure what the rollout status actually is at the moment.

replies(1): >>45902132 #
1. jsheard ◴[] No.45902132[source]
> See go/hls-direct-playback for design and launch stats analysis.

Is that an internal Google wiki or something? I can't find whatever they're referring to.