5 ms·
Opera hasn't been Opera since version 12.
by superkuh 11y ago
Opera hasn't been Opera since version 12.
- Terr_ 11y agoI am literally typing this on 12.17... Which may be a bad idea, but that one of the main reasons I use it is because it has a built-in quick way to enable/disable Javascript, and it's usually off. I like to think that it leaves me safer than newer browsers with a broader attack-surface, but really it's just so much faster 95% of the time.
- coldtea 11y ago>I am literally typing this on 12.17... Which may be a bad idea, but that one of the main reasons I use it is because it has a built-in quick way to enable/disable Javascript, and it's usually off. Can't you do that in ALL browsers, with a plugin that adds a button to your toolbar?
- bcook 11y agoI think his point was that he prefers the javascript toggle to be "built-in quick", which is exclusive to Opera.
- coldtea 11y agoThat has marginal benefit for something that can be implemented as an extension that you install once and forget about it -- namely, just the installation part. In return, you get to use a modern browser without a bizarro rendering engine.
- Mithaldu 11y agoAh, Totschlagargumente. How lovely.
- acqq 11y agoIn the Old Opera I can do every imaginable setting on per-site basis, and all built in, no overhead of extensions. My default were browsing with javascript disbaled, and enabled only for a few critical sites. Much beter than the "ad blocker" extensions that make deal with some ad providers. Real control.
- coldtea 11y ago>In the Old Opera I can do every imaginable setting on per-site basis, and all built in, no overhead of extensions. The overhead for running a few select extensions, compared to native code, would be minimal. And if Opera implements its native extensions as a scripting API (lots of apps do), then zero.
- acqq 11y ago> The overhead for running a few select extensions, compared to native code, would be minimal. Only if the browser is designed that way. If the browser has only global settings implementing per-site handling can impose the need of extension reimplementing half of the browser (in extreme case, see how Google made their "extension" of the IE which effectively installed the 90% of the Chrome inside of IE). And you have to trust extension authors, they can do their own things. Old Opera had what I needed built in, it worked without the need of even enabling javascript subsystem. I don't know of any other browser able to work that way.
- coldtea 11y ago>Only if the browser is designed that way. If the browser has only global settings implementing per-site handling can impose the need of extension reimplementing half of the browser (in extreme case, see how Google made their "extension" of the IE which effectively installed the 90% of the Chrome inside of IE). That's not an extension running on IE to deactivate JS. It's a completely different rendering engine running inside an IE shell. The two concepts are so different it's not even worth commenting. >Old Opera had what I needed built in, it worked without the need of even enabling javascript subsystem. I don't know of any other browser able to work that way. It's trivial (one setting toggle) to disable Javascript in both Chrome and Safari (and I presume Firefox too).
- Terr_ 11y agoSo I went poking around, and the first result that came up for Chrome was Quick Javascript Switcher [0]. Unfortunately, it doesn't work like Opera, because it only lets you add site-tweaks that deviate from the global JS on/off setting. To change the global setting you need to keep navigating to advanced-settings dialogs. Digging into its JS source-code, the extension calls a browser-API chromeContentSettings.javascript [1]. Now, it sounds like at one point in the past that setting was asynchronous, meaning that disabling JS before visiting a suspect page wasn't guaranteed to work anyway [2], but no recent bug-reports or docs mention it, so maybe Chrome fixed that. Still not sure whether there's an exploitable race-condition between when the page URL is available versus when the plugin disables JS, I'm not familiar enough with the relevant events/callbacks. [0] https://chrome.google.com/webstore/detail/quick-javascript-switcher/geddoclleiomckbhadiaipdggiiccfje?hl=en https://chrome.google.com/webstore/detail/quick-javascript-s... [1] https://developer.chrome.com/extensions/contentSettings https://developer.chrome.com/extensions/contentSettings [2] https://github.com/gorhill/httpswitchboard/wiki/Blocking-javascript-execution-reliably-in-Chromium-based-browsers https://github.com/gorhill/httpswitchboard/wiki/Blocking-jav...
- maratc 11y ago> I am literally typing this on 12.17... Which may be a bad idea Absolutely. 12.18 has been available for a while.