4 ms·
Right, so the restrictions on at the bottom seem pretty meaningless, and that matches the migration off of C. So how do we justify this JavaScript as forced la
by remline 9y ago
Right, so the restrictions on at the bottom seem pretty meaningless, and that matches the migration off of C.
So how do we justify this JavaScript as forced labor argument?
The programmer can decide to do webapps that run atop C and get assistance from a backend that ultimately runs on C.
The programmer can use backend frameworks that deliver incantations in JavaScript much like their downcalls to C.
If the migration were toward metal we would be hearing that C has to be excluded. Really how the Buffalo herd is moving does matter in a discussion of what ditches they are stuck in in the middle Savannah.
- Sir_Substance 9y ago>The programmer can decide to do webapps that run atop C Please explain how to make a slippymap[1] in C. For srs, I'm making a hobby project at the moment that needs a dynamic, interactable map on a webpage, and as a long time noscript user it galls me a little to use JS. The only compromise I can come up with is re-hosting the JS libraries I use and ensuring they don't have their own dependencies so that users only need to enable my domain for the site to work. If you can tell me how to do the same thing in C, I'll swap to it immediately. [1] http://wiki.openstreetmap.org/wiki/Slippy_Map http://wiki.openstreetmap.org/wiki/Slippy_Map
- homarp 9y ago>Please explain how to make a slippymap[1] in C. The same way Doom has been compiled and run in the browser. https://github.com/kripken/emscripten/wiki/Porting-Examples-and-Demos https://github.com/kripken/emscripten/wiki/Porting-Examples-...
- Sir_Substance 9y agoBut emscripten compiles...to javascript. I guess that meets the criteria of "programming for the web but not making github commits in javascript", but it doesn't really solve my problem. Oh well.
- pjmlp 9y agoNo, it also compiles to WebAssembly.