8 ms·
Yet another ActiveX-like tech re-spin, we are going back to the dark age. Having usable and capable _SCRIPTING_ language for web was the biggest achievement of
by baybal2 9y ago
Yet another ActiveX-like tech re-spin, we are going back to the dark age.
Having usable and capable _SCRIPTING_ language for web was the biggest achievement of the whole Web 2.0 push, now the browsermaker is about to reverse that
- scriptproof 9y agoNo, in no way. WebAssembly is more a tool to create a library for JavaScript and it is standard unlike ActiveX. It is possible for example to put wasm functions in IndexedDB to use them with multiples apps.
- grondilu 9y ago"Microsoft’s ActiveX[1] was a technology for code-signing x86 binaries to run on the Web. It relied entirely upon code signing and thus did not achieve safety through technical construction, but through a trust model." https://github.com/WebAssembly/spec/blob/master/papers/pldi2017.pdf https://github.com/WebAssembly/spec/blob/master/papers/pldi2...
- sqeaky 9y agoAnd no one used that trust model. Every place I was aware I was using activex, even deploying it in a few places, part of the process was showing the users how how to click the "Run Anyway" or "Ignore security warnings" type of buttons. It was such a night mare for support.
- tejtm 9y agoThe web was never composed of x86 hardware
- tannhaeuser 9y agoI'm siding with baybal2 on this one. No matter how much you're wishing to use your favourite language on the Web, WASM is at best unnecessary, as the kind of application it enables (near-native speed) can be had with ordinary native apps as well. Why does something like that have to run in the browser? The only reason I can think of is because software/game publishers want to control your usage even more. But it doesn't stop there: the worst possible outcome of WASM is that entire custom browser runtimes are being pushed to you [1]. Say goodbye to content linking, sharing, saving, translation, accessibility, ad blocking, etc. Not to mention content will only work on the bundled WebKit version. WASM is user-hostile and anti-Web. What does it even mean that W3C "approved" a working group? I thought WASM was a WHATWG thing. W3C shouldn't lend what's left of its credibility to it. [1]: https://trevorlinton.github.io/ https://trevorlinton.github.io/
- DiThi 9y ago> Say goodbye to content linking, sharing, saving, translation, accessibility, ad blocking, etc. That is already posible without WASM. But it's not done because it hurts search engine scores.
- bigato 9y ago> the kind of application it enables (near-native speed) can be had with ordinary native apps as well. Why does something like that have to run in the browser? For the same reasons all the other kinds of web applications are not developed as native apps as well. Hint: it's not only about speed. Some of the main reasons web apps are winning over native apps is easy of distribution, updates and being multiplataform. And it's being increasingly harder to force javascript to behave as a general application programming environment.
- bigato 9y ago> But it doesn't stop there: the worst possible outcome of WASM is that entire custom browser runtimes are being pushed to you [1] If we ever come to the point where all you need to develop a web browser is a wasm vm, don't you find exciting how much simpler a web browser would become? At the moment it is one of the most complex pieces of software out there. It is so hard to build a modern web browser from scratch nowadays that doing so as a hobby would take a lifetime. This takes the power away from individual developers, since it's not very realistic to build a new browser unless you are a big corporation with money to spare. This situation also poses a big problem for the development of new operating systems. If your shiny, awesome, new research open source OS does not have a modern web browser, it will never reach wide adoption and thus never atract enough developers to build critical mass. The alternative is to make your OS compatible with POSIX and thus reuse the work of others so that you can build existing web browsers. But then you are most likely bound to become just another unix/linux alike, thus hindering innovation.
- dennykane 9y ago> This situation also poses a big problem for the development of new operating systems. I am currently developing a new kind of operating system using nothing but web technologies (ie, it is technically a single-page web app). It might not be the same kind of legacy hardware-centric operating system that most techies fret over, as I am just interested in "userland" ideas (ie, what new kinds of applications can we build, using what new kinds of higher-order abstractions). IMO, the kinds of research programs you are thinking of are really, practically speaking, solved problems. Also, my OS is compatible with POSIX, as it is the first (that I know of) Javascript implementation of IEEE Std. 1003.1 (Shell Command Language). The project is called "Linux on the Web" : - https://linuxontheweb.org https://linuxontheweb.org ~or~ - https://linuxontheweb.appspot.com https://linuxontheweb.appspot.com As individual developers, we really need to start thinking of web browsers as the hardware layer, virtualized as it may be. Just as the scripting languages of the early 90's allowed us all to start thinking at higher levels at the language layer, modern web browsers allow us to start thinking at higher levels at the OS layer.
- fosap 9y agoIt does not change anything substantial about the web today. It will just be a saner output format for compilers than javascript. Unless you write compilers, nothing changes. It does not matter weather your language compiles to JS or WASM, and it does not matter what the browser executes.
- sqeaky 9y agoI agree with most of what you say but it is a bit extreme to say "Unless you write compilers, nothing changes". Some troubleshooting methods will change, the ability to view source will be reduced, performance will be increase, safety will increase... And many more subtle things. I agree it is a huge win, but there are some (minor) negatives.
- baybal2 9y agoThere is a major negative effect - you will be running obscure blobs of code - you can't think of anything worse for security. Sandboxing as such will not help you to any degree with that. People promoting sanboxing as a universal solution have poor knowledge of computer security
- wodencafe 9y agoCome on, don't downvote him just because you disagree with his opinion. That is only discouraging people from expressing their opinions.
- jrs95 9y agoI would agree 95% of the time, but honestly this one is just absurd.
- tyingq 9y ago"Each successive version will incrementally incorporate improvements to support more...features such as: Multiple return values, Multiple memories + tables, Threads + shared memory, SIMD, DOM/HTML integration, Garbage-collected object support..."[1] It does sound like we're headed for some fragmentation here. That list will allow for other scripting languages to run on browsers without having to download a huge runtime, and to interact with the DOM just as JavaScript does. Wasm starts to look more like a multipurpose VM versus looking like ASM. [1] https://www.w3.org/2017/08/wasm-charter https://www.w3.org/2017/08/wasm-charter
- IshKebab 9y agoYour comment makes no sense. Of course it will allow you to use multiple languages. That's the point! Like how you can implement any language using assembly.
- tyingq 9y agoSorry, but your comment makes no sense. Those features are needed for some popular languages to work well in WASM. They aren't implemented yet. Yes, you can hack around and push an entire runtime now. There's a reason nobody is doing that. It isn't practical, performant, or a good experience. Here's Brendan Eich's quote on the matter: "Certainly GCC or similar could generate wasm, but I think to get to the dynamic languages, like I mentioned Dart, or Ruby, or Python, even JavaScript — that’s gonna require some extensions that I mentioned earlier, like: garbage collection hooks, JIT support, things like that. Otherwise they just won’t be competitive."
- falcolas 9y agoI don't disagree that we're moving further and further away from the documents with links model, but that ship has long past sailed. It wasn't just ActiveX, it was Flash. And Java. And Silverlight. And EME. And JavaScript (which, despite the presence of "Script" in the name is not just a scripting language). Web browsers are currently (to take a reductionist view) just VMs with the ability to also view traditional HTML pages. Java had the right idea with its run-anywhere code and the JVM; it was just a bit too early to the party, and didn't have an HTML viewer to get its foot in the door.
- tannhaeuser 9y ago> Java [...] was just a bit too early to the party, and didn't have an HTML viewer to get its foot in the door. Well, it kindof had one ([1], [2], [3]). Rhino JS (still used all over the place; for example by Google's closure compiler) originated from that time. [1]: https://en.wikipedia.org/wiki/HotJava https://en.wikipedia.org/wiki/HotJava [2]: http://jazilla.sourceforge.net/pmwiki.php http://jazilla.sourceforge.net/pmwiki.php [3]: https://docs.oracle.com/javase/7/docs/api/javax/swing/JEditorPane.html https://docs.oracle.com/javase/7/docs/api/javax/swing/JEdito...
- j45 9y agoOh, swing.
- baybal2 9y agoJava is a bad language, bad design, and bad execution. Having more of Java in JavaScript is bad. Turning browser into a VM is just a recipe to bring pretty much every problem inherent to VMs to web development
- sp332 9y agoJS isn't going anywhere? And now you can write code in lots more languages that compile down to Wasm, so that's really the opposite of a reversal.
- borplk 9y agoThis is wrong on so many levels it's borderline trolling. As if minifying and uglifying and mangling ASCII Javascript is so readable and accessible. It was fine for displaying a "Hello dear user please enter your name" dialog in the 90s. Now we are just joking ourselves pushing ASCII program code for full-blown web applications down the wire to the user. If WASM isn't making that any better, it's not making it any worse either.
- baybal2 9y ago>This is wrong on so many levels it's borderline trolling >full-blown web applications Well, for underhanded "premium plugin" devs, this opens opportunities. I understand your position.
- jrs95 9y agoWhat is a "scripting" language? At this point JavaScript has effectively become a general purpose language. And one that usually gets transpiled and then minified for production anyways. Plus, since WASM is essentially for providing libraries to JS code, is there really much of a difference to either the developer or the end user between including a JS library via npm and a WASM library?
- baybal2 9y agoA scripting language, is a language whose main utility is to manipulate and run functions provided from outside of its execution environment