I assume you're running that test suite using a 3rd party 8051 emulator to avoid the potential for common-mode errors in both your compiler and emulator resulting in false confidence the compiler's correctness?
> two simulators used for testing, sim51 (a plain 8051) and minitel_sim
Would I be wrong to assume that you are building end-user applications?
If people use AI for libraries, OSs, and mission critical software, the apparent productivity gains would have to be weighed against the reliability and performance hits that bubble up to the things that are built on them and rely on them.
In my experience - a robust testing harness will get you the safety you need. And most software you describe has such testing.
I think the Bun port is a great example where testing enabled a very successful implementation. (Both the original tests themselves and runtime comparisons to the previous implementation.)
Yes of course, but you also understand that as Dijkstra said "tests cannot show the absence of bugs."
Tests can show you problems, if you can find them, but they cannot show that there are no problems. Property based testing or fuzzing gets your more coverage, and is a good step, but it is still nothing compared to proving things or understanding how something is built and that it is solid. Testing works towards checking for reliability and robustness, but often it's only 10% (?) of the job.
Well, yes, I understand that testing does not create a provably correct solution. But I'd love to hear the source of your "extremely inadequate" or your "10%" claims. I mean - there is a reason why it's used extensively in software engineering - right? Or don't you see value in that, either?
I'm curious - is there any data on the Bun port error rate? I think that would be very indicative of how successful or not the testing is.
This is an artifact of doing as the platform is documented to work. You can do what the man page says, or you can do the opposite. The whole article is about how forking on macOS is troublesome.
My most-common frustration with it is when products I want to compare don't have the same quantity-denominator. (Either a different unit, or sometimes a different dimension like weight versus volume.)
I've many times seen it wrong but more often the same item will have some tags expressed on cost per ounce, others per lb, etc. To discourage comparison. But I dont think people are paying much attention to those numbers anyway. Math has become a scary topic for them altogether.
> two simulators used for testing, sim51 (a plain 8051) and minitel_sim
Narrator: No, he was not.
reply