emscripten

Emscripten[1] comes with SDL support (cf its test suite [2]). Not sure how complete it is. [1] http://kripken.github.io/emscripten-site/ [2] https://github.com/kripken/emscripten/blob/master/tests/hell...

Clearly, it means you write database logic using C++ extended stored procedures [1], business logic in C++ middleware using something like CppCMS [2], and then write all your front end code in C++ and deploy it to the browser using Emscripten [3] Realistically, though, it's probably just a misinformed/careless/hopeless recruiter. Most likely misinformed, or inadequately informed. The recruiter's client probably has something specific in mind when if the asked for a 'full stack' C++ developer. Since you'll find C++ running in everything from embedded devices to phones to cars to airplanes to mainframes, there are so many 'stacks' that one could be referring to when talking about 'full stack'. Usually, full stack developer is used to describe someone who does both front and back end web development. While you could be a full stack dev who w

As sunfish mentions below, this spec document is being conservative in describing things that are still being discussed. There are experimental implementations in Firefox, Chrome and Edge. See https://webassembly.github.io/demo/. There's more information about the current binary format here: https://github.com/WebAssembly/design/blob/master/BinaryEnco... There's a prototype spec interpreter here: https://github.com/WebAssembly/spec/tree/master/ml-proto There's a build waterfall testing multiple tools here: https://wasm-stat.us/console, including the experimental LLVM toolchain, the emscripten-wasm toolchain[0], binaryen[1], and sexpr-wasm[2]. WebAssembly is still under development, but I don't think it's fair to call it an early prototype. [disclaimer: I'm a WebAssembly contributor] [0]: https://github.com/kripken/emscripten/wiki/WebAssem

Hi, I'm one of the main authors of Browsix. One of our goals is to run C code - we have simple utilities from sbase running, and more complex code like latex and GNU make (the README needs updating). The main complication is that C code does system calls, which are traditionally blocking, and there isn't a good way to achieve that in current browsers with just ASM.js. So, we currently use the Emterpreter[1] (which is much slower) to make sure that anything on the stack underneath a system call can be saved and restored. SharedArrayBuffers should let us implement something faster in the near future. 1 - https://github.com/kripken/emscripten/wiki/Emterpreter

It's in development, as many others software projects are, and is far from complete. The goal is to translate as much of core semantics as possible, but i doubt that all the core semantics will be translated. One for all is multi inheritance which is currently unsupported by current Javascript syntax. Even more, when you use an object such a list, it's really a JS Array that will be manipulated in the end, so you will have to use array.push() to add instead of python's list.append() But Translating something like Django is out of scope for all the transpilers, it would mean also converting sql drivers and so on? Does this really make any sense? Maybe you have a look at emscripten https://github.com/kripken/emscripten/wiki

It's a little early, so things are not easy to use yet. Spec still changes, tools still change and break, nothing is optimized for convenience yet, etc. But here is how to use emscripten to emit WebAssembly currently, https://github.com/kripken/emscripten/wiki/WebAssembly

The Emscripten toolchain can be used to produce both WebAssembly and asm.js from the same codebase [0]. There are also the nascent beginnings of a translation tool from WebAssembly to asm.js here [1] (look for wasm2asm). Ultimately, it should be possible to write a streaming polyfill for WebAssembly, but no one has gotten around to making anything suitable for production yet. You're better off producing a separate fallback asm.js bundle for now. [0]: https://github.com/kripken/emscripten/wiki/WebAssembly [1]: https://github.com/webassembly/binaryen

Emscripten can already compile to both asm.js and WebAssembly, with just flipping a switch between them. All the JS library support code is unchanged, so Emscripten's OpenGL to WebGL layer is used just like before, and the same for all the other libraries. The WebAssembly backend in LLVM will eventually be used by Emscripten as another way to emit WebAssembly (right now it translates asm.js to WebAssembly), but the new backend is not ready yet. See also https://github.com/kripken/emscripten/wiki/WebAssembly

Some notes: 1. Emscripten/asm.js supports the defined behavior case of setjmp/longjmp. What is not supported is jumping up an already unwound stack, which is undefined behavior. This is somewhat commonly-seen undefined behavior, though. 2. I don't think it's fair to say that function pointers are "hairy at best, broken at worst." Again, this is a case where we do not support undefined behavior. But perhaps most importantly, most real-world code is properly portable and just works. When not, we have tools that help figure things out. 3. It's not true that everything must be compiled into one massive JS file, Emscripten/asm.js also supports dynamic linking, [1]. However, the default is a single file, because then it can be more fully optimized. 4. There is already threads support, [2]. It works, and progress in the standards bodies is going