Re: NPAPI replacement for those of us who still need system API access

Am Freitag, 9. Oktober 2015 22:38:23 UTC+2 schrieb Richard Bateman:

> My point is that we aren't alone in these types of needs; no matter how many features you may add to the web, and no matter how awesome that is or how much I would love not to have to deal with native code, there are a huge number of niche use cases which simply aren't satisfied without some access to it.
> 

+1 for that.
I have a plugin that *needs to* draw native windows in the browser and otherwise interact with the web page. The plugin is sandboxed, runs in a very restrictive and safe context (per default, that can be configured individually by the user).
I don't care much about platform independence for that use case. It is fine when it runs on windows PC only, because the environment where it is supposed to be used is windows PCs. But I care a lot about accessing native resources (communication with a service on localhost via a proprietary, speed optimized protocol), and I care about drawing a native window inside the current document in the browser, with real time images streamed from the service.
All this has worked fine so far and made users (customers) happy. But it is taken away when NPAPI is taken away, leaving me with just the only option to go back to a fat desktop client with all its disadvantages.. besides the time it takes to re-develop everything from scratch.

-- 
EL