Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Tuesday April 02 2019, @08:04PM   Printer-friendly
from the java++ dept.

Mozilla Extends WebAssembly Beyond the Browser with WASI:

Mozilla’s WebAssembly started as an experiment, almost a question: is it possible to run arbitrary code in a browser without breaking the browser sandbox? A side benefit would be faster web applications that would outperform current web technologies, allowing developers to bring existing desktop applications to the web.

[...]Since its initial launch, WebAssembly has been adopted by all the major browsers, with support from Mozilla, Google, Microsoft, and Apple, who’ve all contributed code.

Best thought of as a definition of a virtual machine, WebAssembly works with the browser’s JavaScript engine to run code at speeds that compare well with native code. Instead of JavaScript’s byte code approach, it takes code written in familiar languages like C and C#, and converts it first to an assembly language-like bytecode before a final compilation as binary. WebAssembly executables are compiled before being delivered to browsers, making them a compact and efficient way of adding complex functionality to web applications.

[...]Experiments with WebAssembly outside the browser are all very well, but if it’s going to be a tool that supports cross-platform as well as cross-browser development, it needs to have new standards built around it. Mozilla recently announced the start of such an effort, with the first release of WASI: the WebAssembly System Interface.

You can perhaps consider WASI as the boundary between system level code running on the host platform and applications running in user mode.

Where WebAssembly works as an implementation of a virtual processor, WASI goes a step further and offers developers an entire conceptual operating system. With a virtual processor, there’s only one target architecture, and the JavaScript engine can handle translation between its implementation and ARM, Intel, Power, or whatever hardware you have. WASI does the same, offering WebAssembly programs its own low-level implementations of common OS functions, that are then translated into OS calls via the host JavaScript engine. Target WASI in your code, and you’re able to produce applications that run identically on macOS, on Windows, on UNIX, and more, even on mobile operating systems.

[...]It’s also important to note that you won’t be writing code that accesses the WASI interfaces directly. Instead, these will be what’s implemented in the WebAssembly equivalents of the standard libraries we use in most common languages. That way we’ll know that if we’re running a C application in WebAssembly through WASI a printf command will write to a console, no matter if it’s on Windows or UNIX. WASI implements the interfaces for WebAssembly compilers and the underlying JavaScript engine handles the actual system calls to whatever OS it’s running on. You don’t need to install the appropriate standard libraries for each target OS for your code, and you only need to compile once.

[...]There are already three implementations of WASI, Mozilla’s own implementation and a polyfill that will allow anyone to experiment with WASI in a browser. Perhaps the most interesting from a developer standpoint coming from edge delivery network Fastly. Its Lucet WebAssembly compiler is now also a runtime, with an open source release on GitHub. Currently used in Terrarium, Fastly’s experimental edge service, it’s seen as a fast alternative to JavaScript running on Google’s V8 engine.

In a blog post, Pat Hickey, a senior software engineer at Fastly, describes Lucet as able to “instantiate WebAssembly modules in under 50 microseconds, with just a few kilobytes of memory overhead. By comparison, Chromium’s V8 engine takes about 5 milliseconds, and tens of megabytes of memory overhead, to instantiate JavaScript or WebAssembly programs.”


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by c0lo on Tuesday April 02 2019, @08:43PM (9 children)

    by c0lo (156) Subscriber Badge on Tuesday April 02 2019, @08:43PM (#823772) Journal

    Phone = consumer
    Computer = maker (potentially)

    You can't develop your own apps on a phone. You may not even be able to install or run on your phone apps that you developed yourself.

    --
    https://www.youtube.com/watch?v=aoFiw2jMy-0 https://soylentnews.org/~MichaelDavidCrawford
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 1, Offtopic) by PlasticCogLiquid on Tuesday April 02 2019, @08:45PM (7 children)

    by PlasticCogLiquid (3669) on Tuesday April 02 2019, @08:45PM (#823774)

    You just found the void that needs filled, go get rich.

    • (Score: 4, Interesting) by Unixnut on Tuesday April 02 2019, @10:33PM (5 children)

      by Unixnut (5779) on Tuesday April 02 2019, @10:33PM (#823833)

      > You just found the void that needs filled, go get rich.

      It is a void for a reason. Namely, it was tried before, and fell flat on its face. The Nokia N800 to N900 series phone/tablets ran a Debian derivative, and you had the full GNU toolchain on it. You could install most GNU apps (including openoffice!) on the phone, and with an X server, you could even have apps forwarded to a thin client from the phone. You had C compilers, Perl, Python, every single programming language Linux had, with all the standard libraries and APIs.

      And was it popular? Hell no, it flopped massively. Nobody apart from nerds bought it, and Nokia itself is no more. Normal people just could not understand the draw of being able to run vim on your phone to code up a Perl script to send SMS messages automatically.

      Android, which when it came out was lambasted by nerds for being inferior in almost every way, took over the mobile world, despite being a locked down spyware infested piece of crap, that was buggy as hell until KitKat (and is now only slightly less buggy in my experience). I can't see a future phone offering a similar OS experience to the old N900 becoming popular, most people don't want nor care about being able to hack their phone, or even so much about privacy and control. Many are happy as long as their social media, game and IM apps work.

      It is like the same thing with the iPod when it first came out. It wasn't the first portable mp3 player, indeed by specs it was ranked pretty poorly compared to the competition, yet decades later, most of the masses have never even heard of "iriver", but they all have heard of "ipod".

      • (Score: 1, Interesting) by Anonymous Coward on Wednesday April 03 2019, @05:03AM (1 child)

        by Anonymous Coward on Wednesday April 03 2019, @05:03AM (#823975)

        and now users can't disable google services it is perpetual spyware

        or uninstall apps like bixby

        or properly firewall apps so they can't connect to the internet

        yes, android is privacy destroying crap in this aspect

        what to replace it with though?

        • (Score: 2) by urza9814 on Wednesday April 03 2019, @03:17PM

          by urza9814 (3954) on Wednesday April 03 2019, @03:17PM (#824106) Journal

          and now users can't disable google services it is perpetual spyware

          or uninstall apps like bixby

          or properly firewall apps so they can't connect to the internet

          I currently have an Android device and have no problem doing any of those things. Just install a better distro -- LineageOS is my personal preference. But this is likely why Google is trying to kill Android now with this Fuscia crap.

          Or you could buy a Librem 5 if those ever become available. I'm hoping to, but the constantly shifting release dates makes it a bit difficult to commit....it'll never be more than a niche product, but maybe it could at least be a *healthy* niche...

      • (Score: 4, Informative) by coolgopher on Wednesday April 03 2019, @06:10AM

        by coolgopher (1157) on Wednesday April 03 2019, @06:10AM (#823983)

        Then N900 was my most feature-rich phone. That is, rich with features *I* wanted, not the ad-pushers.

      • (Score: 2, Funny) by Anonymous Coward on Wednesday April 03 2019, @07:57AM

        by Anonymous Coward on Wednesday April 03 2019, @07:57AM (#824008)

        You can just emulate an N900 on your phone using JavaScript.

      • (Score: 2, Informative) by Anonymous Coward on Wednesday April 03 2019, @05:55PM

        by Anonymous Coward on Wednesday April 03 2019, @05:55PM (#824173)

        uhh, it was purposely torpedoed by stephen elop who was sent in to nokia by microsoft for that express purpose. i think you know that with that nickname...

    • (Score: 2) by Bot on Thursday April 04 2019, @12:29PM

      by Bot (3902) on Thursday April 04 2019, @12:29PM (#824447) Journal

      The first smartphones, the nokias, were EXACTLY like that, linux on a phone. Dream came true, yet I NEVER saw one on sale. When the price dropped a bit I would have bought it without blinking.

      Fact, putting a fully programmable radio on a pocketable pc would have enable too many nifty things nobody really wanted. Not the carriers, not the hardware producers, not the police, not the guys in charge.

      So they toyfied the concept and promoted the heck out of it at the expense of PCs.

      --
      Account abandoned.
  • (Score: 2) by DannyB on Wednesday April 03 2019, @05:50PM

    by DannyB (5839) Subscriber Badge on Wednesday April 03 2019, @05:50PM (#824169) Journal

    Have you tried Android? You don't need anyone's (eg Apple) permission to download and use the development tools. You can install your own app onto your own phone through ADB. On your phone, you have to enable this and are clearly warned that you are installing an untrusted app that is not from the play store. But it will install and run just fine.

    With Apple, you have to bow down to them to get their tools, just out of spite they make you buy a Mac to develop on, and then you have to pay and bow down in order to even put your app onto your phone -- at Apple's pleasure. All this before you even try to submit your app to the iTunes store and hope and pray for acceptance.

    --
    The lower I set my standards the more accomplishments I have.