Live data from Hacker News

Woxi: Wolfram Mathematica Reimplementation in Rust

github.com

121–130 of 141 posts

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#121

Earlier quoted context omitted.

are all the tests hand written or are some agent-contributed? curious

What’s the difference if you review the code getting merged?

Code review basically never actually means thinking through all the code again as if you wrote it

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#122
post #75

I love Rust for mathematical and scientific tasks (I am building the structural bio crate infrastructure), and I love Mathematica and have a personal sub. I should be the audience, but... What makes Mathematica great, IMO, is the polish and overall experience created by consistent work with applications in mind over decades. So, I look at this project with skepticism regarding its utility.

Half-assed reimplementations of existing software (often in the name of "memory safety") is what the Rust community is best known for.

Thanks for the sensible chuckle.

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#123

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

What's wrong with Maxima?

Maxima is a CAS. Mathematica is a complete programming environment with an insanely featureful standard library.

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#124

Earlier quoted context omitted.

Do you see why this perspective is a red flag on its own?

I certainly don't. If a software developer has found a way to use these tools that works well for them and produces good results, that's a good thing.

I have no dog in this fight, but simply claiming a count of tests get you anything is like saying your code coverage is 100% - it sounds really good until you think about what 5000 unreviewed tests actually... do.

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#125
post #119

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…

Sorry, perhaps, a dumb question: Is it not that Mathematica, and most of the Wolfram innovation, is about a smart way of applying some rule-based inference. I think of it as parametrized PROLOG rules, with large lib. So term rewriting all the way to the end, correct me if I'm wrong. Where does the mini-core+JIT come into this? Thanks for taking time to answer.

The interpreter / JIT is the one actually applying the rules.

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#126
post #103

Earlier quoted context omitted.

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

Err yeah that's the point.

You wrote: “If they hand wrote the code we know they at least looked at it once.”

But that’s not true, because even if they did indeed hand-write the code, we as third parties wouldn’t have any reliable proof of that, and therefore still couldn’t draw the conclusion that they looked at the code.

Them claiming to have hand-written the code isn’t any better than them claiming to have thoroughly reviewed the code. We can’t know in either case.

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#127
post #75

Earlier quoted context omitted.

Half-assed reimplementations of existing software (often in the name of "memory safety") is what the Rust community is best known for.

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

People who don't run proprietary software also don't get tech support :) wolfram's support team is very good

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#128
post #126

Earlier quoted context omitted.

Err yeah that's the point.

You wrote: “If they hand wrote the code we know they at least looked at it once.” But that’s not true, because even if they did indeed hand-write the code, we as third parties wouldn’t have any reliable proof of that, and therefore still couldn’t draw the conclusion that they looked at the code. Them claiming to have hand-written the code isn’t any better than them claiming to have thoroughly reviewed the code. We ca…

> Them claiming to have hand-written the code isn’t any better than them claiming to have thoroughly reviewed the code. We can’t know in either case.

It is better, because most people aren't out-right liars. If he said "I hand-wrote the code", sure it doesn't prove it, but I would believe him. When he says "I thoroughly reviewed the code"... yeah maybe. That's the sort of thing people do lie about (even to themselves).

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#129
post #119

Earlier quoted context omitted.

Sorry, perhaps, a dumb question: Is it not that Mathematica, and most of the Wolfram innovation, is about a smart way of applying some rule-based inference. I think of it as parametrized PROLOG rules, with large lib. So term rewriting all the way to the end, correct me if I'm wrong. Where does the mini-core+JIT come into this? Thanks for taking time to answer.

The interpreter / JIT is the one actually applying the rules.

So it is the tokenizer, and rule expansion, that gets JIT'd, right? I mean - there's no some secondary process running on top of the rule expansion?

Re: Woxi: Wolfram Mathematica Reimplementation in Rust

#130
post #112

Earlier quoted context omitted.

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.

Of course. The point is whether you interpret a call to arbitrary_precision_add or compile the call doesn't matter much.

[deleted]
Post reply on HN