Duktape – Embeddable JavaScript Engine Focused on Portability and Footprint
1–7 of 7 posts
Re: Duktape – Embeddable JavaScript Engine Focused on Portability and Footprint
#2How does svaarala do it? He's a one person coding machine. Fantastic work.
Re: Duktape – Embeddable JavaScript Engine Focused on Portability and Footprint
#3And that's something that you can use as a JavaScript engine in Rails, thanks to ExecJS (https://github.com/rails/execjs) and Duktape.rb (https://github.com/judofyr/duktape.rb).
Re: Duktape – Embeddable JavaScript Engine Focused on Portability and Footprint
#4How does svaarala do it? He's a one person coding machine. Fantastic work.
He is, which is a concern about the project's livability!
Re: Duktape – Embeddable JavaScript Engine Focused on Portability and Footprint
#5Older discussions:
Re: Duktape – Embeddable JavaScript Engine Focused on Portability and Footprint
#6«built-in CommonJS-based module loading framework»
I feel like this sort of project seems like a great place to try to get ES2016 modules working from day one, where users a little bit less likely to have existing code they need to run. I realize the Loader spec [1] is still not finished yet, but a project like this could be a good use case to help push it across the finish line.
[1] https://whatwg.github.io/loader/
Edit to add: I hadn't realized how old this project was, so some of this comment is clearly invalidated a bit.