[flagged]
Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
101–110 of 170 posts
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#102I've never used video.js, and the site/advertising seems to be fairly oriented towards people who have used it or are familiar with it. I had one question I couldn't answer reading the site: what makes this different from the native html video element? AFAICT just the transport controls?
Most browsers don't support HLS or DASH. (And why does that matter? Dynamic bitrate adjustment. The chunks are slightly easier to cache as well.)
> Most browsers don't support HLS or DASH.
Most can via media source extensions.
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#103Earlier quoted context omitted.
Most browsers don't support HLS or DASH. (And why does that matter? Dynamic bitrate adjustment. The chunks are slightly easier to cache as well.)
> Most browsers don't support HLS or DASH. Most can via media source extensions.
But that's not native. That's how videojs+HLS.js works, it plugs in the MSE to handle HLS.
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#104Has the WebVTT story changed? I once tried to customize the subtitle rendering but it seemed too difficult.
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#105In case anyone's wondering, this website's syntax highlighting color scheme is called "gruvbox", which I quite like but took an embarrassingly long time to track down https://github.com/morhetz/gruvbox
Any idea what the website's built with? I really like the design/UI tbh
[deleted]
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#106In case anyone's wondering, this website's syntax highlighting color scheme is called "gruvbox", which I quite like but took an embarrassingly long time to track down https://github.com/morhetz/gruvbox
Any idea what the website's built with? I really like the design/UI tbh
As the sibling comment mentions, it's Astro:
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#107Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#108Has the WebVTT story changed? I once tried to customize the subtitle rendering but it seemed too difficult.
I would also be interested in this. Subtitle presentation is something where browsers are still generally very bad at out of the box, so having good subtitle rendering support built directly into the library would make a lot of sense to me. As someone with a lot of knowledge on this subject, I would be very much willing to help at least draft design documents for something like this, if not more.
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#109I've never used video.js, and the site/advertising seems to be fairly oriented towards people who have used it or are familiar with it. I had one question I couldn't answer reading the site: what makes this different from the native html video element? AFAICT just the transport controls?
Fair point, we could answer that more directly on the site. Besides the comparison were there other things that make it seem oriented to people already familiar with it? Generally, the video tag is great and has come a very long way from when Video.js was first created. If the way you think about video is basically an image with a play button, then the video tag works well. If at some point you need Video.js, it'll b…
> Advanced features like [...] ads
I understand the use-case for this, but I find it working against the spirit of free software, which is bringing control back to the user.
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#110Probably not base case but a quick test to replace my audio player (currently using Plyr) turned up the following gaps for me, at least with the out-of-the-box code. 1. No playback rates under 1 2. No volume rocker on mobile 3. Would appreciate having seek buttons on mobile too 4. No (easily apparent) way to add an accent color, stuck with boring monochrome 5. Docs lacked clear example/demo/playground so I wasn't sur…
All solid feedback, thanks! I'm making sure these get captured as issues. Otherwise we're closely tracking feature parity with Plyr (and other players) and our goal is to have full parity by GA, aiming for the middle of the year.
If we’re doing feedback, then:
- On Mac with Increase Contrast turned on in accessibility settings the control bar ends up being white-on-light-grey
- When focusing the volume control with a keyboard, you can only mute or un-mute, not use up or down to adjust the volume. To do that you have to tab again into the volume slider field
- Don’t seem to be able to enter picture-in-picture mode with the keyboard
- Purely from a first class citizen point of view, it’d be nice to have all the accessibility options (transcripts, etc) shown in the homepage demo