holg

9 ms·

61.
by holg 10mo ago
Just the simple interpreter, built in Rust, but yes we can also use the real xlisp, it is pure c, so easy to handle for emscripten, i built in the Benchmark, the original xlisp c in wasm vs the homebrewn interpreter
62.
by holg 10mo ago
You are right, i did not target mobile, but will fix some
63.
by holg 10mo ago
This is beautiful. Schematic capture, PCB layout, broadcast facilities - and 3D cable routing with auto-generated cut lists and labels. That's the workflow taken to its full potential. 64K RAM, 8086 with math coprocessor, ACAD 1.0. Mem
64.
by holg 10mo ago
Fun idea: I'll try to compile Betz's original XLISP (C) to WASM too. Then we can benchmark 1980s C vs 2024 Rust, both running in the browser. Will probably be a crappy benchmark, but entertaining - and a nice tribute to the source
65.
by holg 10mo ago
Wire harness specs in part numbers - elegant. Same pattern, different purpose: you generated final documentation, we generated DXF that fed back into CAD workflows. And what's running on this page is the same - a real interpreter execu
66.
by holg 10mo ago
Ha, so I wasn't alone! Conveyors are a perfect fit - standardized components, parametric variations. The pattern was obvious once you saw it. Good to know it worked for you too.
67.
by holg 10mo ago
Thanks! You nailed it - AutoLISP was the right abstraction. Direct DXF/PostScript meant entity tables and coordinate gymnastics. (command "LINE" p1 p2) just did the thing. What's running here: real WASM interpreter execu
68.
by holg 10mo ago
Thanks for the link! I didn't know about the XLISP controversy. My interpreter doesn't aim for full compatibility - just enough to run the schematic generation workflow from 1991. The core is: defun, setq, car/cdr, recursion,
69.
by holg 10mo ago
sure it does, but Lisp is special, and for those times it was very special. I did not want to show how it is done nowadays, but how we had done it 33 yrs ago... And now there is the emulator as the web-page, this is what i wanted to share (
70.
by holg 10mo ago
fixed it, thx for the notice
71.
by holg 10mo ago
In the early 90s I wrote AutoLISP code for AutoCAD 9/10 that enabled a CSV → template → parametric drawing workflow. You could define components in spreadsheets, feed them through templates, and generate complete technical drawings au
72.
Show HN: AutoLISP interpreter in Rust/WASM – a CAD workflow invented 33 yrs ago(acadlisp.de)
137 points by holg 10mo ago|44 comments
73.
by holg 10mo ago
Hi thx for sharing, in general about concurrency Rayon excels on CPU-heavy tasks, but this is more IO for traversal avoid any extra round-trips, simple the metadata already given edge-cases would be infinite loops on symlinks, the Windows 2
74.
by holg 10mo ago
Thanks! For gaming: the Bevy demo shows how to calculate real lighting using exact technical parameters from actual products. for sure it is technical, but the point is it doesn't have to be a big Windows-only app – an installer can es
75.
by holg 10mo ago
Oh well, it is open source, you are welcome to have a look.. the web part is done in Leptos, the 3D part in Bevy. Most of it (as much as possible, to share across) is simple Rust. pyo3 makes it the python-module uniffi makes the bindings, t
76.
by holg 10mo ago
Thanks! For gaming: the Bevy demo shows how to calculate real lighting using exact technical parameters from actual products. for sure it is technical, but the point is it doesn't have to be a big Windows-only app – an installer can
77.
by holg 10mo ago
The technical pivot to live yeast is notable because it solves the survival problem (gastric acid) but introduces a massive Quality Control variable. You effectively trade 'hard manufacturing' for 'inconsistent dosing.'
78.
Show HN: Rust/WASM lighting data toolkit – parses legacy formats, generates SVGs(eulumdat.icu)
52 points by holg 10mo ago|5 comments