Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller

videojs.org

Post reply on HN
Print view View original

141–150 of 170 posts

Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller

#141

Post by cyanf »

rezmason wrote: post #57

In 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

A seldom appreciated benefit of gruvbox: like vim binds, it's available everywhere. If it has a theming system, somebody ported gruvbox to it.

Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller

#143

Post by jacobgkau »

As someone who uses VideoJS on a website with a large video library, and has generally been dismayed at the state of the plugin ecosystem every time I consider doing a major version upgrade of VideoJS, this kind of thing is great to hear.

Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller

#145

Post by Heff »

robin_reala wrote: post #110
Heff wrote: post #47

Earlier quoted context omitted.

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 fr…

This is great. Keep it coming.

Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller

#146

Post by Heff »

01jonny01 wrote: post #142

It would be good if videoJS had youtube embed api and documentation like Plyr has

In the works! You should be able to use the existing [1] with the HTML side of v10 today, but we're working on porting over the other media elements into the new architecture for better React support.

[1] https://www.npmjs.com/package/youtube-video-element

[2] https://github.com/muxinc/media-elements

Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller

#147

Post by Heff »

dylan604 wrote: post #127

I see you promoting that the looks are consistent across browsers. I've seen several other video players that are browser dependent because of particular JS features used. Are future features going to remain browser agnostic?

Can you give an example of a player/feature combo where this is the case? For general player features there's not really an excuse for only working in one browser, but features like Casting can be browser dependent because the browser has to expose that functionality. Other interesting prototypes rely on a new API called Web Codecs that isn't fully supported everywhere.

In the core JS of Video.js v10 we're building without the assumption of there even being a browser involved so we can point to future JS-based platforms like React Native.

Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller

#148

Post by Heff »

jacobgkau wrote: post #143

As someone who uses VideoJS on a website with a large video library, and has generally been dismayed at the state of the plugin ecosystem every time I consider doing a major version upgrade of VideoJS, this kind of thing is great to hear.

Drop a note in the discussions some time. I'd love to hear about what you're doing and even help migrate when the time is right for you.

https://github.com/videojs/v10/discussions

Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller

#150

Post by dylan604 »

Heff wrote: post #147
dylan604 wrote: post #127

I see you promoting that the looks are consistent across browsers. I've seen several other video players that are browser dependent because of particular JS features used. Are future features going to remain browser agnostic?

Can you give an example of a player/feature combo where this is the case? For general player features there's not really an excuse for only working in one browser, but features like Casting can be browser dependent because the browser has to expose that functionality. Other interesting prototypes rely on a new API called Web Codecs that isn't fully supported everywhere. In the core JS of Video.js v10 we're building w…

There have been other video players that attempt to be more "professional" adding things like audio meters and other tools. These are using parts of JS that is not available anywhere except in Chrome. After digging in, there's a lot of audio related things that Chrome is trying to do that FF/Safari are not. We have mp4 files with multiple audio streams that Chrome exposes ability to select from while FF/Safari do not. Creating waveforms on the fly from a video source also becomes problematic.

We've also had issues getting frame accuracy when navigating the video stream. There's some sort of "security" that randomizes/rounds the returned value of currentTime that I cannot wrap my head around as how that is security related. Lots of effort spent on getting stock HTML5 video element to be frame accurate.

Post reply on HN