| ▲ | adius 4 hours ago | |
I think the Wolfram Language got 80–90% of it right, and that's why I want to reimplement and use it in the first place. It bothers me that I have to use inferior solutions, such as those implemented in Python and Julia, just because the better solution is prohibitively expensive. Of course, there are a few things I think we can do better than the Wolfram Language, but given all the available legacy code, there's really no point in making it slightly different and losing the ability to use that code. However, we might build an alternative syntax and frontend in the future that surfaces the capabilities of the Wolfram Language with a better UX. | ||
| ▲ | jshaqaw 4 hours ago | parent [-] | |
Good points all. Please understand this is more of a general open source friendly criticism I made. There is good value in preserving access to codebases made for Wolfram language which is expensive albeit they do offer decent licenses now to mess around with it. I’m curious abut benchmarking. Wolfram claims they put a ton of effort into optimizing the speed of at least certain types of mathematical computations. UX is an area I’d suggest working on. Wolfram was a real pioneer with the notebook style interface but nothing is meant to last forever. That might be an area to innovate without losing access to legacy codebases. | ||