Heff

21 ms·

1.
by Heff 6mo ago
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
2.
by Heff 6mo ago
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 bro
3.
by Heff 6mo ago
In the works! You should be able to use the existing <youtube-video-element> [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]
4.
by Heff 6mo ago
This is great. Keep it coming.
5.
by Heff 6mo ago
Thank you!
6.
by Heff 6mo ago
Absolutely! The community has always been the strongest part of the project. In the new version the core player itself is built as many composable components rather than one monolithic player, so we're going to invite more people to co
7.
by Heff 6mo ago
The biggest architectural move at multiple layers of the stack was moving from monolithic controller objects to composable, tree-shakeable components, functions and state slices. Less trade-offs and more taking advantage of modern JS bundle
8.
by Heff 6mo ago
Full rewrite and an intentional architecture to allow for composability and tree shaking, meaning the player bundle only ever includes the features you're using.
9.
by Heff 6mo ago
I second that it sounds like HLS/DASH (Adaptive live streaming over HTTP) is what you're looking for, instead of RTP/RTMP. WebRTC being a more open model for real-time streaming, but nowhere near as easy or scalable HTTP-ba
10.
by Heff 6mo ago
Something AI has done for Video.js is allow us to set our sights higher, with the about the same size team. Specifically aiming for idiomatic components and patterns for each popular JS framework (React, Svelte, Vue, React Native), not ju
11.
by Heff 6mo ago
I’m not sure which user we’re talking about, but it’s up to the video.js user to decide if and when they use ads. Just like it’s up to YouTube. Video can get expensive, so some video wouldn’t exist without some form of monetization.
12.
by Heff 6mo ago
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 wh
13.
by Heff 6mo ago
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.
14.
by Heff 6mo ago
That's great! It looks like you have a pretty extensive integration with the prior version of Video.js, so migrating will take some work, but I think worth it when you can make the time. That said, for Beta it works with browser-suppor
15.
by Heff 6mo ago
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 f
16.
by Heff 6mo ago
Drop a note in discussions or issues! Would love to hear what you’re working with. https://github.com/videojs/v10/discussions
17.
by Heff 6mo ago
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!
18.
by Heff 6mo ago
OP and Mux co-founder here so have all the context on this. A lot has changed. Mux stepped in to help maintain React Player a few years ago. It wasn't getting frequent updates and Mux has a vested interest in the whole OSS player ecos
19.
by Heff 6mo ago
Not a today answer, but this is something I'm excited to build within the new Presets concept of video.js v10, where we can build specific "video interfaces" beyond a standard player using the composable architecture. https:
20.
Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller(videojs.org)
648 points by Heff 6mo ago|137 comments
21.
by Heff 7mo ago
I've been building for the web since the 90s and it's always felt a little off how slow the uptake on web components has been. Glenn Maddern's X-GIF talk at JSConf EU '13 opened my mind to expanding the browser beyond it
22.
by Heff 8mo ago
Video.js creator here, and I agree with this ^. Frame accurate seeking isn't something the native video element does. Check out the Omakase player: https://player.byomakase.org/
23.
Mux (YC W16) is hiring engineering managers for video at scale(mux.com)
1 points by Heff 1y ago
24.
by Heff 2y ago
Had to be said :)
25.
by Heff 2y ago
Oh boy, I could write a book in response to this... > a section on their site explaining how they are able to undercut everyone in the business and still keep going This is great feedback that I'm putting on our todo list. We should
26.
by Heff 2y ago
Thank you! Winamp is getting a lot of love (and controversy) right now so it felt worth calling out. But it's not my favorite of the themes in practice. I think that's Sutro, which kind of surprised us by how nice it turned out.
27.
by Heff 2y ago
Fully flexible color choice is a foot gun. I've definitely made some very ugly themes with that too. The goal is to have very many themes here, including user-submitted ones, so it might be hard to create something that can warn about
28.
by Heff 2y ago
Anything frame-accurate or smooth scrubbing has always been a challenge with he abstraction level of the video element. I don't have an exact answer from you, but you might look around the web codecs space, where more performant exampl
29.
by Heff 2y ago
That's a really nice implementation. I feel like it should be easy for that to support videos too, if desired. I assume it's just using a media element under the hood.
30.
by Heff 2y ago
Thank you! If you still experience friction when trying to build your own theme, then our job isn't done. So let us know!

More ›