Live data from Hacker News

Woxi: Wolfram Mathematica Reimplementation in Rust

github.com

101–110 of 141 posts

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#101
post #2

Hi, I'm the main developer. We're steadily getting closer to the next release which will support most features of Mathematica 1.0 plus some of the most popular newer functions (> 900 overall!). AMA!

Why would I use this and not Wolfram Script? Better license? Allowed for commercial operations?

License is a big deal, and not just for cost and openness, but also for practical use in pages like docker, ci/cd pipeline, cloud deployments, or other places licenses need to be dynamic.

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#102

Earlier quoted context omitted.

Mathematica is proprietary software. Any reimplementation is better than nothing at all, at least for people that don't run proprietary software

Useless thing is not less useless by the virtue of being FOSS. That's something FOSS folks have yet to understand. All the best to the author, they definitely have fun doing this, but I've seen enough of such attempts. Having agents doesn't make much difference.

The difference is huge - It burns money quicker and nobody understands the code

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#103
post #95

Earlier quoted context omitted.

To be fair, we also couldn’t tell for sure if they hand-wrote the code.

If they hand wrote the code we know they at least looked at it once.

Since we can’t know whether they really hand-wrote the code, we also wouldn’t know whether they looked at it.

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#104
post #92

My Bona fides: I've written my own Mathematica clone at least twice, maybe three times. Each time I get it parsing expressions and doing basic math, getting to basic calculus. Then I look up the sheer cliff face in front of me and think better of the whole thing. There is an architectural flaw in Woxi that will sink it hard. Looking through the codebase things like polynomials are implemented in the rust code, not in…

I noticed the same thing, having also written an interpreter for the Wolfram language that focused on the core rule/rewriting/pattern language. At its heart it’s more or less a Lisp-like language where the core can be quite small and a lot of the functionality built via pattern matching and rewriting atop that. Aside from the sheer scale of WL, I ended up setting aside my experiments replicating it when I did perform…

I’ve personally had luck at correcting the complex one-off logic the agents produce with the right prompting.

and when I say prompting, I just mean code review feedback. All of this is engineering management. I review code. I’ll point out architectural flaws if they matter and I use judgement to determine if they matter. Code debt is a choice, and you can afford it in some situations but not others. We don’t nit over style because we have a linter. Better documentation results in better contribution quality. etc.

Agent coordination? Gastown? All I hear is organizational design and cybernetics

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#105

Earlier quoted context omitted.

How does it compare to mathics? How close is it to being able to run rubi: https://rulebasedintegration.org/ ?

You can find the whole integration routine here https://github.com/ad-si/Woxi/blob/36343ab2cbc97e5081f7c811e... . It's essentially a test mock-up (not even trying partial fraction decomposition for rational functions).

    // ∫ tan(x) dx = -ln|cos(x)| - not implemented (requires Log)
This really doesn't bode well... I'm no expert in CASes, but everything I've looked at seems very naive. Vibe coding a Mathematica replacement makes zero sense to me.

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#106
post #99

Earlier quoted context omitted.

implementing addition in woxilang itself?? this gotta be terribly slow. am i missing something?

Mathematica has symbolic and infinite-precision addition, so you can't automatically take advantage of obvious compiled code.

What? Arbitrary precision arithmetic implemented in a compiled language will be faster than the alternative. This is no great mystery. The same is true of essentially all low-level symbolic or numerical math algorithms. You need to get to a fairly high level before this stops being true.

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#108
post #2

Hi, I'm the main developer. We're steadily getting closer to the next release which will support most features of Mathematica 1.0 plus some of the most popular newer functions (> 900 overall!). AMA!

What is your plan for long term support?

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#109

Earlier quoted context omitted.

> what's stopping some employee from something like Mathematica from taking the source code and having an agent port it to open source Laws against theft. Also the same reason employees don't release the code on pastebin or something. > Who owns an algorithm? The org or person who was granted the software patent. https://en.wikipedia.org/wiki/Software_patent > Will everything get copied eventually? If we're lucky. Mo…

https://en.wikipedia.org/wiki/Illegal_number

honestly one of my favorite Wikipedia articles. It's silly, but it is a logical conclusion to the existence of secret information.

45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B1

REDACTED

45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B3

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#110

Earlier quoted context omitted.

implementing addition in woxilang itself?? this gotta be terribly slow. am i missing something?

You are missing the term "JIT", which would enable a host of runtime optimizations which include generating calls to some static piece of native code which performs addition.

But surely you can have a "fast path" that is implemented in the host language, right?
Post reply on HN