Did you read what this does? Because I get the feeling you didn’t…
This isn’t a library, you don’t include in your application, and it doesn’t try to replace an understanding of floating point issues on the programmers part.
It looks like there’s a download link that contains the source code. Presumably you untar it, follow any necessary build instructions, and then run it.
This very much depends on your definition of ‘best’. While your criticisms of the environment are valid, smalltalk is flexible in tangible ways that Java couldn’t match. Java took the OO model of smalltalk and make a bunch compromises that had big negative impacts on the language that are still there today.
Smalltalk was (and still is in some places) successful because of its portability, flexibility, etc. while it hasn’t enjoyed the degree of success as Java, ruby, perl, python, C++, and friends it would be a mistake to call it just a you.
I can’t be alone in this, but this seems like a supremely terrible idea. I reject whole heartedly the idea that any sizeable portion of one’s code base should specifically /not/ be human interpretable as a design choice.
There’s a chance this is a joke, but even if it is I don’t wanna give the AI tech bros more terrible ideas, they have enough. ;)
That kind of feedback is also possible within this framework in theory. It depends on at what level the abstract interpreter is operating. If it’s the source level then it’s easy, but propagating that from an IR to source code is, shall we say, an open question.