Re:Show HN: I took back Video.js after 16 years and we rewro...
by nulltrace on Tuesday March 24, 2026 @09:07PM
(#47511871)
The feature-array approach to createPlayer is smart. We did something similar splitting a monolith into per-feature packages and the hardest part wasn't the split itself, it was figuring out where the boundaries go. Two features look independent until you realize they share some piece of state that neither wants to own. Curious how they handle cross-feature state deps here.
[ Parent
| on HN ]
Re:Show HN: I took back Video.js after 16 years and we rewro...
by cpillsbury on Tuesday March 24, 2026 @09:38PM
(#47512095)
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...).
Re:Show HN: I took back Video.js after 16 years and we rewro...
by cpillsbury on Tuesday March 24, 2026 @09:43PM
(#47512134)
One other thing to note: because the features are "composed", we at least have a lot of flexibility here that makes me feel pretty good about the fundamentals and not "coding ourselves into a corner" here.
Re:Show HN: I took back Video.js after 16 years and we rewro...
by nulltrace on Tuesday March 24, 2026 @11:42PM
(#47512993)
Yeah the composability buys you a lot of room. One central store with events, inject it into each feature, and they stay decoupled without painting yourself in.
Re:Show HN: I took back Video.js after 16 years and we rewro...
by blanched on Tuesday March 24, 2026 @09:40PM
(#47512107)
Please stop posting AI-generated comments. Your post history is full of them.