2 ms·

There's already a VLC web plugin, how would VLC.js be any different for the end user? https://wiki.videolan.org/Documentation:WebPlugin/ https://wiki.videolan.

There's already a VLC web plugin, how would VLC.js be any different for the end user? https://wiki.videolan.org/Documentation:WebPlugin/ https://wiki.videolan.org/Documentation:WebPlugin/

striking 10y ago
The web plugin requires installation and draws a native window with native code, onto your browser viewport. "VLC.js" would theoretically take an HTML <video> or <canvas> tag, as well as a filename, as arguments... and that'd be it. No setup, no nothing. You would just have video, playing. Although I've had some bad experiences with software decoding on mobile platforms, so I don't really know of any advantages to having it as a JS file besides "look at what's possible with emscripten". It'd wreck your laptop's battery life, probably be unplayable on mobile. Why not just have your user... download VLC?
tiles 10y ago
I believe NPAPI is being deprecated; that wiki page is very out of date.
- cpeterso 10y ago
  Neither Chrome nor Edge support NPAPI plugins today. Firefox is dropping support for all NPAPI plugins (other than Flash) in Firefox 52 (March 2017).