Earlier quoted context omitted.
I don't think WebAssembly will become more common than JavaScript anytime soon. And even when it will be, it means the tooling will have become so good that you won't even have to think about WebAssembly. That will be left to the people who create compilers to WebAssembly. Hopefully you'll just use whatever language your org/team/etc. uses, and have it compiled to JS or WebAssembly as is most appropriate for said lan…
I guess the first ones jumping on the WebAssembly wagon will be Web developers, so we will probably get WASM modules written in languages they see appropriate, when JS doesn't cut it anymore. I guess it will be Rust or Go. Rust because of Cargo (for npm users a big +) and Mozilla (good marketing of Rust). Go because of Google (also a Web company with good marketing) and because I read some Node.js developers already…
Goodbye PNaCl, Hello WebAssembly
71–80 of 352 posts
Re: Goodbye PNaCl, Hello WebAssembly
#72This one I'm fine with since WebAssembly is a worthy replacement, but I'm still annoyed at Google discontinuing Chrome Apps. Some examples of specialized apps I use all the time that would require a native app otherwise: - Signal Desktop - TeamViewer - Postman - SSH client - Cleanflight drone configuration tool It was one of the best things that happened to Linux desktops in a long time and removing it hurts users an…
Re: Goodbye PNaCl, Hello WebAssembly
#73Is WebAssembley going to turn into yet another web technology that can be used by websites in order to track us or to annoy us with advertising? I'm asking because every time something new is introduced, it feels like it ends up being used to abuse users (Javascript, XSS, Cookies, HTML5 Video).
It doesn't do anything that Javascript didn't already do. By the way, why do you think HTML5 is a problem?
Re: Goodbye PNaCl, Hello WebAssembly
#74This one I'm fine with since WebAssembly is a worthy replacement, but I'm still annoyed at Google discontinuing Chrome Apps. Some examples of specialized apps I use all the time that would require a native app otherwise: - Signal Desktop - TeamViewer - Postman - SSH client - Cleanflight drone configuration tool It was one of the best things that happened to Linux desktops in a long time and removing it hurts users an…
Forgive me if I misunderstand but won't android apps work on Chrome OS devices well at least the newer ones anyways?
Chrome Apps were great because they worked on all (desktop) platforms.
Re: Goodbye PNaCl, Hello WebAssembly
#75As a web developer working primarily in JS, what should I be learning now to stay relevant/up-to-date once WebAssembly is more common? Are we going to see more web stuff built with c++, like the dsp example in this blog post?
WebAssembly is a medium for ASM.js apps, and ASM.js apps are mainly C and C++ . You have to learn C and C++ period.
You can program in wasm's text format (the actual assembly language) directly, if you want, and you can program in anything that compiles to wasm. C/C++ have the most developed toolchains for higher (than wasm itself) level languages, for now, but that should open up.
Re: Goodbye PNaCl, Hello WebAssembly
#76Is WebAssembley going to turn into yet another web technology that can be used by websites in order to track us or to annoy us with advertising? I'm asking because every time something new is introduced, it feels like it ends up being used to abuse users (Javascript, XSS, Cookies, HTML5 Video).
I agree. It seems like most of the extra horsepower we have these days is used for tracking on behalf of a company instead of features that are useful for the end user.
The great thing about shitty websites is that I can opt to not visit them.
Re: Goodbye PNaCl, Hello WebAssembly
#77Looks like Mozilla won this fight. When Mozilla didn't accept PNaCl and Pepper API proposed by Google, Mozilla went down the ASM path which now led us to Web Assembly being the general way forward.
Yup, when you consider that WASM can be polyfilled with Asm.js it's pretty obvious where things were headed.
Re: Goodbye PNaCl, Hello WebAssembly
#78Earlier quoted context omitted.
Chrome OS has no native SSH client, but Google published a NaCL based SSH client: https://chrome.google.com/webstore/detail/secure-shell/pnhec... It's useful outside of Chrome OS if you have a security perimeter based on TLS with ACLs and auditing already in place and you want to use it for SSH as well: https://github.com/zyclonite/nassh-relay https://chromium.googlesource.com/chromiumos/platform/assets... Google use…
I wouldn't call it a "Linux Desktop" if you can't run a standard SSH client. Chrome OS is it's own beast.
https://groups.google.com/a/chromium.org/d/msg/chromium-hter...
But "if everything aligns" == "only if you're inside Google".
Re: Goodbye PNaCl, Hello WebAssembly
#79Earlier quoted context omitted.
It doesn't do anything that Javascript didn't already do. By the way, why do you think HTML5 is a problem?
The suggestion I got was that "HTML5 Video" was the subject. Which still doesn't make sense; the alternatives which it replaced (Flash, QuickTime, WMV, Java-based video players...) were all radically worse, and much more abuseable.
Worst, some sites these days will waiting until you've scrolled down a bit before they start playing a video, leaving the user to locate it and stop it.
As for Flash, it was indeed bad, but at least I had the option of not installing it.
Re: Goodbye PNaCl, Hello WebAssembly
#80Earlier quoted context omitted.
I wouldn't call it a "Linux Desktop" if you can't run a standard SSH client. Chrome OS is it's own beast.
In some ways, and if everything aligns, ChromeOS is actually better: https://groups.google.com/a/chromium.org/d/msg/chromium-hter... But "if everything aligns" == "only if you're inside Google".
Makes a lot of sense sense since Chrome OS is much easier to secure than a normal Linux distribution.