Alternatives to Emscripten logo

Alternatives to Emscripten

WebAssembly, Rust, WebGL, Modernizr, and Babel are the most popular alternatives and competitors to Emscripten.
18
20
+ 1
0

What is Emscripten and what are its top alternatives?

This allows applications and libraries originally designed to run as standard executables to be integrated into client side web applications.
Emscripten is a tool in the JavaScript Compilers category of a tech stack.
Emscripten is an open source tool with 25K GitHub stars and 3.2K GitHub forks. Here’s a link to Emscripten's open source repository on GitHub

Top Alternatives to Emscripten

  • WebAssembly
    WebAssembly

    It is an open standard that defines a portable binary code format for executable programs, and a corresponding textual assembly language, as well as interfaces for facilitating interactions between such programs and their host environment. ...

  • Rust
    Rust

    Rust is a systems programming language that combines strong compile-time correctness guarantees with fast performance. It improves upon the ideas of other systems languages like C++ by providing guaranteed memory safety (no crashes, no data races) and complete control over the lifecycle of memory. ...

  • WebGL
    WebGL

    It is integrated completely into all the web standards of the browser allowing GPU accelerated usage of physics and image processing and effects as part of the web page canvas. Its elements can be mixed with other HTML elements. ...

  • Modernizr
    Modernizr

    It’s a collection of superfast tests or detects as we like to call them which run as your web page loads, then you can use the results to tailor the experience to the user. It tells you what HTML, CSS and JavaScript features the user’s browser has to offer. ...

  • Babel
    Babel

    Babel will turn your ES6+ code into ES5 friendly code, so you can start using it right now without waiting for browser support. ...

  • Rome
    Rome

    It is a linter, compiler, bundler, and more for JavaScript, TypeScript, JSON, HTML, Markdown, and CSS. It is designed to replace Babel, ESLint, webpack, Prettier, Jest, and others. It unifies functionality that has previously been separate tools. Building upon a shared base allows us to provide a cohesive experience for processing code, displaying errors, parallelizing work, caching, and configuration. ...

  • Scala.js
    Scala.js

    It is a safer way to build robust front-end web applications. With it, typos and type-errors are immediately caught and shown to you in your editor, without even needing to compile your code. Refactor any field or method with ease, with the confidence that if you mess it up the editor will tell you immediately ...

  • Rome
    Rome

    It is an experimental JavaScript toolchain. It includes a compiler, linter, formatter, bundler, testing framework and more. It aims to be a comprehensive tool for anything related to the processing of JavaScript source code. ...

Emscripten alternatives & related posts

WebAssembly logo

WebAssembly

212
214
0
A binary instruction format for a stack-based virtual machine
212
214
+ 1
0
PROS OF WEBASSEMBLY
    Be the first to leave a pro
    CONS OF WEBASSEMBLY
    • 2
      Security issues

    related WebAssembly posts

    Rust logo

    Rust

    5.7K
    4.7K
    1.2K
    A safe, concurrent, practical language
    5.7K
    4.7K
    + 1
    1.2K
    PROS OF RUST
    • 143
      Guaranteed memory safety
    • 130
      Fast
    • 87
      Open source
    • 75
      Minimal runtime
    • 70
      Pattern matching
    • 63
      Type inference
    • 56
      Algebraic data types
    • 56
      Concurrent
    • 46
      Efficient C bindings
    • 43
      Practical
    • 37
      Best advances in languages in 20 years
    • 32
      Safe, fast, easy + friendly community
    • 30
      Fix for C/C++
    • 25
      Stablity
    • 24
      Zero-cost abstractions
    • 23
      Closures
    • 20
      Great community
    • 20
      Extensive compiler checks
    • 18
      No NULL type
    • 18
      Async/await
    • 15
      Completely cross platform: Windows, Linux, Android
    • 15
      No Garbage Collection
    • 14
      Great documentations
    • 14
      High-performance
    • 12
      Super fast
    • 12
      Generics
    • 12
      High performance
    • 11
      Safety no runtime crashes
    • 11
      Guaranteed thread data race safety
    • 11
      Fearless concurrency
    • 11
      Macros
    • 10
      Compiler can generate Webassembly
    • 10
      Helpful compiler
    • 9
      Easy Deployment
    • 9
      RLS provides great IDE support
    • 9
      Prevents data races
    • 8
      Real multithreading
    • 8
      Painless dependency management
    • 7
      Good package management
    • 5
      Support on Other Languages
    CONS OF RUST
    • 26
      Hard to learn
    • 23
      Ownership learning curve
    • 11
      Unfriendly, verbose syntax
    • 4
      Variable shadowing
    • 4
      High size of builded executable
    • 4
      Many type operations make it difficult to follow
    • 3
      No jobs
    • 1
      Use it only for timeoass not in production

    related Rust posts

    Caue Carvalho
    Shared insights
    on
    RustRustGolangGolangPythonPythonRubyRubyC#C#

    Hello!

    I'm a developer for over 9 years, and most of this time I've been working with C# and it is paying my bills until nowadays. But I'm seeking to learn other languages and expand the possibilities for the next years.

    Now the question... I know Ruby is far from dead but is it still worth investing time in learning it? Or would be better to take Python, Golang, or even Rust? Or maybe another language.

    Thanks in advance.

    See more
    James Cunningham
    Operations Engineer at Sentry · | 18 upvotes · 313.6K views
    Shared insights
    on
    PythonPythonRustRust
    at

    Sentry's event processing pipeline, which is responsible for handling all of the ingested event data that makes it through to our offline task processing, is written primarily in Python.

    For particularly intense code paths, like our source map processing pipeline, we have begun re-writing those bits in Rust. Rust’s lack of garbage collection makes it a particularly convenient language for embedding in Python. It allows us to easily build a Python extension where all memory is managed from the Python side (if the Python wrapper gets collected by the Python GC we clean up the Rust object as well).

    See more
    WebGL logo

    WebGL

    178
    197
    0
    A JavaScript API for rendering 3D graphics within any compatible web browser
    178
    197
    + 1
    0
    PROS OF WEBGL
      Be the first to leave a pro
      CONS OF WEBGL
        Be the first to leave a con

        related WebGL posts

        Shared insights
        on
        WebGLWebGLthree.jsthree.js

        I want a advice on what to use as a beginner three.js or WebGL?

        See more
        Modernizr logo

        Modernizr

        28K
        2K
        0
        Respond to your user’s browser features
        28K
        2K
        + 1
        0
        PROS OF MODERNIZR
          Be the first to leave a pro
          CONS OF MODERNIZR
            Be the first to leave a con

            related Modernizr posts

            Babel logo

            Babel

            26.5K
            10.7K
            391
            Use next generation JavaScript, today.
            26.5K
            10.7K
            + 1
            391
            PROS OF BABEL
            • 165
              Modern Javascript works with all browsers
            • 77
              Open source
            • 60
              Integration with lots of tools
            • 56
              Easy setup
            • 26
              Very active on github
            • 2
              JSX
            • 2
              Love
            • 2
              Source maps
            • 1
              Extensions
            CONS OF BABEL
              Be the first to leave a con

              related Babel posts

              Jonathan Pugh
              Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 2.9M views

              I needed to choose a full stack of tools for cross platform mobile application design & development. After much research and trying different tools, these are what I came up with that work for me today:

              For the client coding I chose Framework7 because of its performance, easy learning curve, and very well designed, beautiful UI widgets. I think it's perfect for solo development or small teams. I didn't like React Native. It felt heavy to me and rigid. Framework7 allows the use of #CSS3, which I think is the best technology to come out of the #WWW movement. No other tech has been able to allow designers and developers to develop such flexible, high performance, customisable user interface elements that are highly responsive and hardware accelerated before. Now #CSS3 includes variables and flexboxes it is truly a powerful language and there is no longer a need for preprocessors such as #SCSS / #Sass / #less. React Native contains a very limited interpretation of #CSS3 which I found very frustrating after using #CSS3 for some years already and knowing its powerful features. The other very nice feature of Framework7 is that you can even build for the browser if you want your app to be available for desktop web browsers. The latest release also includes the ability to build for #Electron so you can have MacOS, Windows and Linux desktop apps. This is not possible with React Native yet.

              Framework7 runs on top of Apache Cordova. Cordova and webviews have been slated as being slow in the past. Having a game developer background I found the tweeks to make it run as smooth as silk. One of those tweeks is to use WKWebView. Another important one was using srcset on images.

              I use #Template7 for the for the templating system which is a no-nonsense mobile-centric #HandleBars style extensible templating system. It's easy to write custom helpers for, is fast and has a small footprint. I'm not forced into a new paradigm or learning some new syntax. It operates with standard JavaScript, HTML5 and CSS 3. It's written by the developer of Framework7 and so dovetails with it as expected.

              I configured TypeScript to work with the latest version of Framework7. I consider TypeScript to be one of the best creations to come out of Microsoft in some time. They must have an amazing team working on it. It's very powerful and flexible. It helps you catch a lot of bugs and also provides code completion in supporting IDEs. So for my IDE I use Visual Studio Code which is a blazingly fast and silky smooth editor that integrates seamlessly with TypeScript for the ultimate type checking setup (both products are produced by Microsoft).

              I use Webpack and Babel to compile the JavaScript. TypeScript can compile to JavaScript directly but Babel offers a few more options and polyfills so you can use the latest (and even prerelease) JavaScript features today and compile to be backwards compatible with virtually any browser. My favorite recent addition is "optional chaining" which greatly simplifies and increases readability of a number of sections of my code dealing with getting and setting data in nested objects.

              I use some Ruby scripts to process images with ImageMagick and pngquant to optimise for size and even auto insert responsive image code into the HTML5. Ruby is the ultimate cross platform scripting language. Even as your scripts become large, Ruby allows you to refactor your code easily and make it Object Oriented if necessary. I find it the quickest and easiest way to maintain certain aspects of my build process.

              For the user interface design and prototyping I use Figma. Figma has an almost identical user interface to #Sketch but has the added advantage of being cross platform (MacOS and Windows). Its real-time collaboration features are outstanding and I use them a often as I work mostly on remote projects. Clients can collaborate in real-time and see changes I make as I make them. The clickable prototyping features in Figma are also very well designed and mean I can send clickable prototypes to clients to try user interface updates as they are made and get immediate feedback. I'm currently also evaluating the latest version of #AdobeXD as an alternative to Figma as it has the very cool auto-animate feature. It doesn't have real-time collaboration yet, but I heard it is proposed for 2019.

              For the UI icons I use Font Awesome Pro. They have the largest selection and best looking icons you can find on the internet with several variations in styles so you can find most of the icons you want for standard projects.

              For the backend I was using the #GraphCool Framework. As I later found out, #GraphQL still has some way to go in order to provide the full power of a mature graph query language so later in my project I ripped out #GraphCool and replaced it with CouchDB and Pouchdb. Primarily so I could provide good offline app support. CouchDB with Pouchdb is very flexible and efficient combination and overcomes some of the restrictions I found in #GraphQL and hence #GraphCool also. The most impressive and important feature of CouchDB is its replication. You can configure it in various ways for backups, fault tolerance, caching or conditional merging of databases. CouchDB and Pouchdb even supports storing, retrieving and serving binary or image data or other mime types. This removes a level of complexity usually present in database implementations where binary or image data is usually referenced through an #HTML5 link. With CouchDB and Pouchdb apps can operate offline and sync later, very efficiently, when the network connection is good.

              I use PhoneGap when testing the app. It auto-reloads your app when its code is changed and you can also install it on Android phones to preview your app instantly. iOS is a bit more tricky cause of Apple's policies so it's not available on the App Store, but you can build it and install it yourself to your device.

              So that's my latest mobile stack. What tools do you use? Have you tried these ones?

              See more
              Simon Reymann
              Senior Fullstack Developer at QUANTUSflow Software GmbH · | 23 upvotes · 4.7M views

              Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

              • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
              • Vue Styleguidist as our style guide and pool of developed Vue.js components
              • Vuetify as Material Component Framework (for fast app development)
              • TypeScript as programming language
              • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
              • ESLint, TSLint and Prettier for coding style and code analyzes
              • Jest as testing framework
              • Google Fonts and Font Awesome for typography and icon toolkit
              • NativeScript-Vue for mobile development

              The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

              • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
              • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
              • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
              • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
              • Large scaling. Vue.js can help to develop pretty large reusable templates.
              • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
              See more
              Rome logo

              Rome

              53
              8
              0
              A linter, compiler, bundler, and more for JavaScript, TypeScript, JSON, HTML, Markdown, and CSS
              53
              8
              + 1
              0
              PROS OF ROME
                Be the first to leave a pro
                CONS OF ROME
                  Be the first to leave a con

                  related Rome posts

                  Scala.js logo

                  Scala.js

                  49
                  66
                  0
                  The Scala to JavaScript compiler
                  49
                  66
                  + 1
                  0
                  PROS OF SCALA.JS
                    Be the first to leave a pro
                    CONS OF SCALA.JS
                      Be the first to leave a con

                      related Scala.js posts

                      Rome  logo

                      Rome

                      26
                      12
                      0
                      All in one JS toolchain (By Facebook)
                      26
                      12
                      + 1
                      0
                      PROS OF ROME
                        Be the first to leave a pro
                        CONS OF ROME
                          Be the first to leave a con

                          related Rome posts