js-in-css-rt
web2js
| js-in-css-rt | web2js | |
|---|---|---|
| 1 | 2 | |
| 22 | 107 | |
| - | - | |
| 10.0 | 1.8 | |
| over 5 years ago | over 2 years ago | |
| JavaScript | xBase | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
js-in-css-rt
-
The JavaScript Ecosystem Is Delightfully Weird
This took a different direction than I expected! I was hopping to see a bit more of the extreme weirdness of JS and not so much of "mainstream weirdness" though.
I've played with Javascript itself, brought it to extremes that were just funny and painful and it's amazingly weird. There's lots of experiments and pseudo-libraries out there exploring those as well like JS-in-CSS [1]. I've even wrote some of them, like Running PHP in Javascript [2] and a funny "jquery alternative" that allows you to do `dom.a._target = "blank";` [3] (for the equivalent of `$('a').attr('target', '_blank');`).
[1] https://github.com/walaura/js-in-css-rt
[2] https://francisco.io/blog/running-php-in-javascript/
[3] https://www.npmjs.com/package/superdom
web2js
-
The JavaScript Ecosystem Is Delightfully Weird
When I last looked, it seemed like WASM blobs just take arrays of numbers and return arrays of numbers. No objects, strings, or DOM elements, so I think it'd be tough to do web dev in wasm as it stands. And you need javascript glue if you want anything in the way of side effects.
There is, however, quite a bit you can do in it. TeX has been compiled to wasm[1], it's about 600kb uncompressed 90k compressed (the memory image with latex loaded is about 6MB compressed though - latex is a beast). I think anything computationally intensive would be a good candidate for wasm (it has int64).
1: https://github.com/kisonecat/web2js
-
Math Rendering Is Wrong
I implemented a TeX engine in WebAssembly so you really can run TeX in the browser. You can see a demo of this at https://tex.rossprogram.org/ and at https://github.com/kisonecat/web2js you can find a Pascal compiler that targets WebAssembly which can compile Knuth's TeX. Interesting primitives like \directjs are also implemented, so you can execute javascript from inside TeX. The rendering is handled with https://github.com/kisonecat/dvi2html for which I finally fixed some font problems.
To make it relatively fast, the TeX engine gets snapshotted and shipped to the browser with much of TeXlive already loaded. So even things like TikZ work reasonably well. There is of course a lot more to do! The plan is to convert ximera.osu.edu to this new backend by the fall.
What are some alternatives?
quickjs - Public repository of the QuickJS Javascript Engine.
dvi2html - Device independent (DVI) file format parsing with node
javascript - Javascript client
KaTeX - Fast math typesetting for the web.
remark - markdown processor powered by plugins part of the @unifiedjs collective
latex2mathml - Pure Python library for LaTeX to MathML conversion
qubyte-codes - My personal site.
thatjdanisso.cool - My blog