[dead]
Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
71–80 of 170 posts
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#72Awesome! And thank you all for your projects and your hard work!
I hope the plugin directory get an overhaul too and a prominent place an the webpage. The plugin ecosystem was for me a huge benefit for Video.js
Even though some of them are outdated, they were a good source of inspiration.
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#73I'm not familiar with video hosting but have played with html5 video player but I have this question: on the servers side, do I have to host a specific endpoint that serves chunks of video? Lets say I take 720p video @ 800mb and I chunk it into 2mb pieces with ffmpeg. So I have a folder somewhere (webserver, cdn, blob storage) with the original 4K video, then generate downscaled versions for 1440p, 1080p, 720p, so I…
Maybe look at MPE-DASH?
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#74[flagged]
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#75I'm not familiar with video hosting but have played with html5 video player but I have this question: on the servers side, do I have to host a specific endpoint that serves chunks of video? Lets say I take 720p video @ 800mb and I chunk it into 2mb pieces with ffmpeg. So I have a folder somewhere (webserver, cdn, blob storage) with the original 4K video, then generate downscaled versions for 1440p, 1080p, 720p, so I…
Just convert it to HLS, which is naturally chunked at 1-2 second intervals, and serve all the pieces from nginix. No dynamic content needed. I do this with videojs and it works great. Added bonus of HLS is that my LG TV supports it natively from tags.
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#76Congrats 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!
So fun seeing all these familiar names pop up in a single thread, haven't been active in video after leaving Kaltura but have fond memories of FOMS/FOSDEM and meeting all of you!
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#77Out 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.
Is it not a web component, per se? Per the article, all the React stuff does seem to bake down to HTML Custom Elements, that get wired up by some client-side JS registering for them. That client-side JS is still a "web component", even if it's embedded inside React SPA code bundle, no? If you mean "why do I need React / any kind of bundling; why can't I just include the minified video.js library as a script tag / ES6…
You certainly can just add it to a tag and then not do any of that.
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#78In 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
The HTML generator meta tag (f11 to open dev tools) says it's Astro: https://astro.build/
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#79[flagged]
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#80Earlier quoted context omitted.
This is true, and the whole iOS/iPadOS/tvOS ecosystem supports HLS natively making it much easier to work with on that platform. In addition, Chrome recently added support for HLS[1] (and not DASH), so the native browser support for HLS is getting pretty wide. HLS also has newer features that address the growing manifest issues you were seeing. [2] All that said, I think a lot of people would feel more comfortable if…
How do you actually use HLS in the form of a native browser feature? Can you just put the m3u8 in the video src?
Yes, doing that works perfectly. If you use videojs it will automatically use native support if present.