121–130 of 279 posts
Note that Bellard already wrote a (small) HTML/CSS engine for his Emacs clone. So we're only a small step away from Bellard-Browser.
Wait, QEmacs was written by Bellard, too? I stumbled across it a while ago but I didn't pay attention to the author. Damn.
Is there anything that Fabrice can't do? I mean, FFMpeg is almost a PhD thesis in and of itself, and he still manages to find time to make TinyC, QEMU, and now this. To say I'm jealous of his skills would be an understatement.
Yeah this is just crazy. I think he and ludde together are responsible for like 90% of software I like and use very frequently. ;-)
I'm curious - what is/was the intended application of this?
If you want a very fast javascript engine and dont have problems with binary size, memory constraints and executable memory pages, you can pick a JIT like V8, Chakra or Spidermonkey. As those JITs are pretty advanced optimizing JIT compilers and will run javascript code very fast, much faster than the fastest interpreted VM implementation can.
People who tend to choose this instead of V8 for instance need to run this in a microcontroler for instance, or a OS without executable memory pages (and therefore where JIT´s are forbidden).
Undefined symbols for architecture i386 I get this error when attempting to make on macOS. I don't have very much experience with C, but is there a good resource to learn how to better deal with compiler issues and such other than googling specific issues?
Hacky workaround: comment out the "CONFIG_M32=y" line in the makefile. This will disable building the 32-bit versions of some tools. ("Edit the makefile" is, according to the docs, the canonical way to customize your build settings.)
And I don't think there's any real shortcut for dealing with compiler error messages. You've just got to learn what they mean and what sort of thing tends to cause them.
Worth noting: the demo is a WASM-compiled instance of this engine. I'm not sure, but I think this might be the first example of a fully featured, potentially production-ready, JS VM sandbox running in the browser. (We're looking into safe ways to enable third party scripting of our own application, and such a sandbox would be a very nice tool to have in hand.)
Worth noting: the demo is a WASM-compiled instance of this engine. I'm not sure, but I think this might be the first example of a fully featured, potentially production-ready, JS VM sandbox running in the browser. (We're looking into safe ways to enable third party scripting of our own application, and such a sandbox would be a very nice tool to have in hand.)
2019+ will Atwood's law compiled to WASM. My co-worker Jason wrote a JS engine in Rust, Boa ( https://github.com/jasonwilliams/boa ) and demoed it via WASM in the browser at the recent JSConf.EU 2019: https://www.youtube.com/watch?v=_uD2pijcSi4
Earlier quoted context omitted.
He has his own company now with another partner ( https://www.amarisoft.com/ ) where they work on and distribute the LTE software he wrote.
Well, the scrolljacking is evidence no one is infallible. ;)
Earlier quoted context omitted.
Yeah this is just crazy. I think he and ludde together are responsible for like 90% of software I like and use very frequently. ;-)
ludde who?