For consumers, it's neither been quality nor trash. They just don't think about it.
I think this tension arises from the commercialization of a consumer product. If consumers and product managers aren't pushing the product in all these different directions, there aren't issues. "Pro" software doesn't face these issues either - Resolve, Photoshop, SolidWorks, Excel; but consumer-oriented spinoffs do. Apple's attempt to consumerize FinalCut was poorly received at launch.
I always wondered how commoners (?) could afford to go to a pub every day to socialize, or if it was cheap, how the pubs could survive with a bunch of people who were just hanging out day after day.
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 when Video.js was first created. If the way you think about video is basically an image with a play button, then the video tag works well. If at some point you need Video.js, it'll become obvious pretty quick. Notable differences include:
* Consistent, stylable controls across browsers (browsers each change their native controls over time)
* Advanced features like analytics, ABR, ads, DRM, 360 video (not all of those are in the new version yet)
* Configurable features (with browsers UIs you mostly get what you get)
* A common API to many streaming formats (mp4/mp3, HLS, DASH) and services (Youtube, Vimeo, Wistia)
Of course many of those things are doable with the video tag itself, because (aside from the iframe players) video.js uses the video tag under the hood. But to add those features you're going to end up building something like video.js.
Part of what makes AI useful to me is getting though the layers of "what the hell is this, exactly" that slow you down when you jump more than one level beyond your domain knowledge. I think every knowledge container (document, website, what have you) should have a "what the hell is this" link /rich tooltip /accordion section /whatever by default.
Of course, AI explanations often also fail at this unless you give them "ELI5" or other relevant prompting (I'm looking at you Perplexity).
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.
In this case, you're talking about the browser user, and not the dev user of video.js, but I feel like you know this and are just trying to rail against ads in a manner that's just not relevant.
If someone providing video content wants to run ads as part of making the video available to you, that's up to them. It's also up to you if you want to attempt to view the video without those ads or skip watching altogether. But to the dev of video.js, you're personal choices of consuming AVOD content are irrelevant.
it just doesn’t work in every environment. every browser version has it’s own issues and edge cases. If you need stable video player or want streaming features you should use it.
P.S i built movie streaming and tv broadcasting player for country of Georgia and supported environments from 2009 LG Smart TVs to modern browsers.
you think it’s solid until you want customization and old browser support. it should work fine if you just want to autoplay a small size mp4 file on mute
Hey, core contributor here! If a plain video element plus hls.js is all you need to accomplish your goals, we wouldn't ever try to convince you otherwise. In fact, our "HlsVideo" media renderer is backed by hls.js, and Rob Walch has done Herculean feats maintaining and updating that playback engine. If, however, you don't simply want what's provided from the built in <video controls>, or don't want to worry about all of the hairy edge cases or minutia of feature-rich UIs, VJS can help. If you want it to be dirt simple to switch between, say, a simple MP4, MPEG-DASH, or HLS, Video.js's architecture makes that simple. If you want to customize UIs from the ground up but not have to think about/worry about the state modeling of relevant media UI state, you can grab all and only the bits of VJS you want. Also, while still in its early stages, if you don't need the "swiss army knife" of features (and, sadly, code footprint) that is built into hls.js, you can use our "SimpleHlsVideo" media renderer.
We definitely aren't trying to convince anyone to use our free, open source library that doesn't need it. But we do think there are lots of value adds for lots of folks under lots of circumstances that we can and will help, including as simple as not needing to reinvent the wheel a bunch of times.
Being an asshole? For saying "could have fooled me" to one of the 6 posts on a brand new account heavily advertising video.js benefits in response to my post mentioning that the video element is already both powerful and easy to use, and that adding HLS.js to add HLS support to it for browsers that don't support it natively is dead simple?
I guess your threshold for calling someone an asshole is a bit low.
I don't have a problem with using video.js for the reasons the parent poster mentioned, but HTML5 video is insanely easy to implement, and there's no reason to take on a dependency like this if you don't need something beyond what the web platform already gives you.
The Coast Guard has long been responsible for port security. TSA does administer TWIC, the Transportation Worker Identification Credential program, which is a biometric identification system go access to secure port facilities.
Yeah, it was actually a lot of fun. I worked in a port-related area and often we would just cruise around the port and look at the ships. If it looked cool we would yell loudly and ask if we could come aboard. The seamen were usually thrilled to show us around their massive ships and would often invite us to a barbecue. With the introduction of the ISPS all of that was over in an instant.
Okay, so this is good for tracking egg price changes (I guess? It was $1,591).
But if you put this into your accounting spreadsheet or whatever, you'd be off by a few cents all over the place, your account balances wouldn't match up. Then what do you do?
I've been looking into this and 96% isn't great. The solution is digital receipts... which are still being blocked by industry interests etc etc.
Can you do those ad-hoc though? I was looking into this too. I feel like it requires a system config change, apply, and then you need to do container start + machinectl login to actually get a shell.
That's definitely what I want... most of the time.
* declarative mode, where your guest config is defined within your host config, or
* imperative mode, where your guest NixOS config is defined in a separate file. You can choose to reuse config between host and guest config files, of course.
Hashibashi - does this mean it's okay to place the chopsticks across the top if it's not to show you're finished? I heard that was okay as long as you align them not to point at another person (not across the table). If there's no chopstick rest I'm not sure where else you're supposed to put your chopsticks.
Also I'm not sure how you're supposed to eat e.g. fried rice without yokobashi or kakibashi.
Also! I thought kaeshibashi was a good thing. I've definitely seen people do that at parties.
Everything that a maintainer would need to prove to themselves to merge it can be codified in a pipeline.
Or some kind of protocol for building those things in the MR so that any new behavior explicitly demonstrates the new states and transitions.
This is hard if the new MR introduces a completely different paradigm outside the mental model of the reviewer and maintainer. Might be better off completely forking the project and running it in parallel aka taking on the maintainer duties if they feel so inclined to completely change things
reply