Smalltalk, Lisp, Prolog(?) have had better ways of handling the issue for a very, very, long time. Simple integer values, floats, complex, very large
integers ... all dealt with in a nice unifying framework.
Sadly none of those languages took off as explosively as many others.
You want a precise value for 453 factorial? Try doing that with only 64 bit float representation.
No problem. Just use a big number library, like one does in C/C++ whatever. The only language in common use that can do that is Python.
C makes life very unpleasant but at least tries to do something close to reasonable for integer/float issues. Of course it completely screws us for signed unsigned stuff, though given that they forgot to make pointers something separate to numbers I guess it had to be that way.
I'm not sure I follow you. C is about the simplest abstraction over common machine architecture features that you can have that enables the creation of portable code. As such C is great.
I don't ever recall having much of a problem with signed, unsigned or pointers in C. Do you have an example of what is bugging you there?
Whilst I think that is daft, it doesn't alter the fact that JS can be used to do some impressive things, including, by the way, writing a VM to run Smalltalk.
Yes! Now you got it.
Amazingly the performance of this was in the "useful ball park". About half the speed of the natively compiled C++.
Memory in C++ is a leaky abstraction .