woxi.ad-si.com

Show HN: Woxi - Open-source Mathematica / Wolfram Language reimplementation

adius · 310 points · 45 comments · Hôm kia · Open original

Woxi is an interpreter for the Wolfram Language written in Rust. It comes with Woxi Studio, a Mathematica-like GUI built with iced, but you can also use Woxi through a CLI, Jupyter kernel, Python package, npm package, or WASM module. Compared with wolframscript / Mathematica, the main differences are: - Free and open source - Very fast startup - Typically milliseconds rather than seconds for the Wolfram kernel, making Woxi practical for shell scripts, one-liners, and other short-lived processes - Embeddable - It can run in a browser via WASM or be embedded into another application as a scripting language A more detailed comparison with Mathematica is available here: https://woxi.ad-si.com/docs/comparison/mathematica/. Conformance is ensured with ~26'000 unit tests and ~900 .wls script snapshot tests. The current focus is on fixing remaining edge cases, improving performance, and growing the community. If you use the Wolfram Language, I'd be particularly interested in feedback on compatibility and missing functionality. Contributions and bug reports are also very welcome: https://github.com/ad-si/Woxi

Comments

5 preview comments · loading full thread
peterusHôm qua

I get the reasons for not supporting out of order execution and the % variable, it makes for more readable and usable notebooks. Unfortunately most of the time I use Mathematica it is not to make a readable and repeatable notebook but just to help with uni work, so I do take shortcuts like putting multiple statements in a block and using % frequently. If you are planning to add another component, I'd like to +1 the control systems module. It's a lot less clunky than Matlab in my opinion and faster to use. I've used the classical analysis, state space model and matrix equation solver features in that module, none of the microcontroller stuff https://reference.wolfram.com/language/guide/ClassicalAnalys... Either way, I'll probably be using this after I graduate and no longer have the site license, since I cannot imagine using a different CAS, so thanks for developing this

xvilkaHôm qua

Wish you luck. Hope one day instead of Sage that is a bunch of Python glue for completely different and disjointed systems like Maxima, SymPy, Octave, GAP, PARI/GP, etc we will get a one well-integrated (and blazingly fast because written in Rust). I am a big supporter of open-source but after struggling with Sage and Co, decided that buying Wolfram Mathematica license is well-worth it (never regretted since). It would be great if we don't need to do that anymore. As for the "most wanted" features, I would vote for PDEs, since most other systems (apart from Mathematica itself) do not support them well.

alex7oHôm kia

This was also posted 6 months ago: https://news.ycombinator.com/item?id=47155526

ethanc8Hôm qua

I tried out the multivariable calculus visualizations from https://nmd.web.illinois.edu/classes/2024/241/schedule.html (search for "visualization") and Woxi Studio seems to be able to display them. I'm not sure if it's entirely correct (there might be a few bugs) since I don't have Mathematica currently to serve as a comparison.

bobajeffHôm qua

As sometime who's never used Wolfram Languages before this project has gotten me interested. For sometime now I've been looking into a good CAS for my app. I've tried a few algebra problems with Sympy, Sage, Xcas, Maxima and Woxi. Of these only Sage, Maxima and Woxi were capable of giving the expected answers. After trying it out I became fascinated by Wolfram language and other term rewriting languages they are pretty interesting even though most have little to do with CAS like WL. Anyway I've been looking at this project and plan to seriously use it in the future. So, I've noticed a few things when attempting to run wljs (I had to wrap it with a shell script to get wljs to see it as wolframscript executable). First the version number system variable gives a string instead of the expected real number type (As a temporary hack I modified Woxi to give what wljs expects). There also is a variable that tells to the absolute path of the of the current file and it is wrong when it's used in an imported script. After working around that with hard coded paths things became more difficult. Edit: just checked my pc and the variables are called $VersionNumber and $InputFileName which is incorrect if the file is evaluated via Get["filepath"]. Anyways, I'm interested in helping out don't know if I can.