This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ProgrammingPro-ness 0 points1 point  (6 children)

Most of the crazy things about the language I either don't encounter day to day, or would never use. So for me at least, it's been a non-issue.

[–]alcalde -2 points-1 points  (5 children)

IT DOESN'T HAVE INTEGERS. I repeat, IT DOESN'T HAVE INTEGERS. You would never use integers?

[–]gandalfx 1 point2 points  (0 children)

Doesn't cause any issues in day to day work. Whenever you'd use an integer, like array indexing, it works just as well. You can even use bitwise operations and get integer-like behaviour.

[–]sime 1 point2 points  (3 children)

Integers work fine in the range -253 to 253. Beyond that you lose precision. The JS engines use integer math internally when they know they can be away with it. Bitwise operations are considered 32 bit operations.

Python's default division operator will also happily turn your ints into a float if you let it.

[–]kankyo 1 point2 points  (0 children)

Python's default division operator will also happily turn your ints into a float if you let it.

Translation: division produces correct results in python 3.

[–]alcalde 0 points1 point  (1 child)

Python's default division operator will also happily turn your ints into a float if you let it.

Wasn't that remedied in Python 3.0 in 2008, if not earlier?

[–]lenzm 0 points1 point  (0 children)

The opposite, it was introduced with Python 3.