3 ms·
Ya know, my initial reaction to this was pretty negative. As a developer, I don't like the idea of losing access to a more powerful technique in favor of a les
by mindcrime 11y ago
Ya know, my initial reaction to this was pretty negative. As a developer, I don't like the idea of losing access to a more powerful technique in favor of a less powerful one. If I want to write an add-on, I want XPCOM / XUL, etc., at least as an option.
However, giving it more thought, I think this might actually be a Good Thing in the long-run. OK, it's a stretch, but hear me out... I've been a vocal opponent of this whole idea of making the browser a poor man's operating system for a while. I want a Web where browsers are really good at, well, browsing hypermedia, and other applications handle "application stuff". So maybe, in a roundabout fashion, making it a little bit harder to extend the browser even further, will encourage people to shift back to a model of handing off some kinds of requests to an entirely different app, rather than trying to shoe-horn the kitchen sink, bathtub, 3d printer, milling machine, jumper cables, semiautomatic pistol, bandsaw, swimming pool, and clown suit all into the browser.
Or maybe not. Hey, a guy can wish, right?
- dragonwriter 11y agoI think the opposite is more likely: Firefox and Chrome using the same extension mechanism -- and, inevitably, that means two-way chasing on implementing APIs that prove useful -- means that even if the ability to do more complex apps in Firefox falls in the short run, the ability to more complex apps in the browser in general (or, at least, Firefox, Chrome, and their descendants and others who adopt the same framewoek) is going to accelerate over a longer term.
- mindcrime 11y agoYeah, I'm afraid you're right. :-( But like I said, a guy can wish. A more interesting question might be: "What would it take to slow down this movement towards doing everything (and then some) IN the browser"?