Did you know Node.js uses IEEE double (53-bit) to store an inode number (64-bit)? Well now you do. And if you ever wondered why I think Node.js is unsuitable for even basic usage and must be avoided for anything you intend to run in any capacity n>=0 times, here's another reason.
https://github.com/nodejs/node/issues/12115#issuecomment-290064494
@voidstar And I'm guessing this is because they're putting it in a JS numeric field somewhere, right? There's hundreds of other things I like about node.js, and inode numbers aren't really a thing I've ever needed to use so far... So I'm gonna disagree with you there.
@voidstar Note: I've got a fair bit of experience programming in C and C++ in desktop and embedded environments, high level and low level, so I understand exactly what you're saying here... yet I'm not really bothered by it. Perhaps they could create an opaque object type for it...