here, 6yr ago... http://2ality.com/2012/07/large-integers.html …
-
-
Replying to @jasonmulligan
You do not understand floating point numbers. 2^53 is not the largest integer that can be represented accurately in 64-bit floats. *All* the integers *from zero to 2^53* can be represented, but *many more larger than that* can too. Just not all of them.
2 replies 0 retweets 4 likes -
Replying to @marcan42
just read the URL i linked, it explains things very well
1 reply 0 retweets 0 likes -
Replying to @jasonmulligan @marcan42
Jason Mulligan Retweeted BrendanEich
or... i dunno, argue with brendanhttps://twitter.com/brendaneich/status/526826278377099264?lang=en …
Jason Mulligan added,
2 replies 0 retweets 0 likes -
Replying to @jasonmulligan @marcan42
I worked on Int64/Uint64 until others were inspired to see-and-raise by doing BigInt. Win-win, no hat eating.
1 reply 0 retweets 0 likes -
Replying to @BrendanEich @jasonmulligan
Catching up with Python, eh ;-) Seriously though, lack of Uint64 (and ints in general) was a major pain point for a lot of binary processing in JS. The only problem now is that JS got a real int type so late that all the APIs take Number... is there a plan for that?
1 reply 0 retweets 0 likes -
Replying to @marcan42 @jasonmulligan
https://asmjs.org/ -- JS has int32 and uint32, modern engines optimize accordingly esp. when sourced/sunk via typed arrays. I suggest reading (including the issues) https://github.com/tc39/proposal-bigint … also.
1 reply 0 retweets 1 like -
It's true we could have added many numeric types ages ago, but browser wars I shut down JS standardization after 1999 ES3. When we got it restarted via Firefox it took too long, with divided member effort due to Silverlight, Dart, PNaCl, to find the champions and get tc39 moving.
2 replies 0 retweets 2 likes -
I'm not moaning about this, it is pointless to cry over spilled milk, but it seemed you were belaboring the lateness. Anyway, the history is what it was and the best time to have done BigInt was 1995, when (with only me working on JS) I had no time for it. Still sleep-deprived.
2 replies 0 retweets 2 likes -
Replying to @BrendanEich @jasonmulligan
History is what it is indeed. This whole discussion stemmed from an "other languages do/have done this better" talk, which, well, is the case, but fixing things now is better than never. I hope JS finds ways to evolve towards getting rid of these nits. It's definitely not easy!
1 reply 0 retweets 0 likes
My main beef isn't with the language (I can understand why it is what it is, and it's improving) but with those who defend its warts just because they like it. Those people are rarely the ones actually working on the language :-)
-
-
Replying to @marcan42 @jasonmulligan
In my experience the worst belly-aching comes from those who haven't done JS in years -- or ever. But YMMV. “There are only two kinds of languages: the ones people complain about and the ones nobody uses.” ― Bjarne Stroustrup, The C++ Programming Language
2 replies 16 retweets 31 likes -
I've been really trying to empathize with those that aren't able to see JavaScript for what it is and not for how it isn't like _insert language here_. I wish there was more compassionate learning material to share that taught the whys in a less dogmatic way. Any suggestions?
1 reply 0 retweets 0 likes - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.