this is lovely work
Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
21–30 of 170 posts
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#22Out of curiousity, why not distribute this as a webcomponent? It's a perfect use case for it - a semantic object that has built in controls / chrome.
Ah...you're scratching at some scabs with this totally reasonable question.
We learned some tough lessons with media-chrome[1] and Mux Player, where we tried to just write web components. The React side of things was a bit of a thorn, so we created React shims that provided a more idiomatic React experience and rendered the web components...which was mostly fine, but created a new set of issues. The reason we chose web components was to not have to write framework-specific code, and then we found ourselves doing both anyway.
With VJS 10 I think we've landed on a pretty reasonable middle ground. The core library is "headless," and then the rendering layer sits on top of it. Benefit is true React components and nice web components.
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#23Congrats Steve! I haven't touched video since I was at JW Player a million years ago, but I always inspired by the simplicity of video.js (especially the theming). Hope this new iteration is exceptionally successful.
Oh hi Zach! Blast from the past. Hope you’re doing well and thanks for the well wishes. Always enjoyed chatting you and the JW team at FOMS and conferences. The water’s warm back here in video tech if you ever want to jump back in!
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#24this is lovely work
Thank you!
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#25[flagged]
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#26I was just lamenting the other day about the size of video.js, which is used in my legacy web app, and looking for a way to improve that. Very keen to explore how we could migrate to v10!
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#27Serious question. We currently have this tool in our framework, that we use to play videos from youtube, vimeo, and a whole lot of other sites:
https://github.com/Qbix/Platform/blob/main/platform/plugins/...
We currently already use video.js, and our framework us used all over the place, so we’d be the perfect use case for you guys.
How would we use video.js 10 instead, and for what? We would like to load a small video player, for videos, but which ones? Only mp4 files or can we somehow stream chunks via HTTP without setting up ridiculous streaming servers like Wowsa or Red5 in 2026?
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#28[dead]
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#29I was just lamenting the other day about the size of video.js, which is used in my legacy web app, and looking for a way to improve that. Very keen to explore how we could migrate to v10!
Drop a note in discussions or issues! Would love to hear what you’re working with.
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#30[flagged]
Hey VJS core contributor here. We definitely feel that concern and we also don't yet have a silver bullet formalized. I suspect we'll need some kind of alternate implementations or feature augmentation at some point. We're currently doing things in a bit more ad hoc way, such as the interrelationship between PiP and Fullscreen (see, e.g.: https://github.com/videojs/v10/blob/main/packages/core/src/d...).