Same. We use 64-bit ints as "Entity IDs", and countless other stuff. Saying that it's a "parser problem" is not really helpful, bc many parsers refuse to support 64-bit ints, even if they could, bc compatibility with…
Even if you force them to give you a raise now, that doesn't mean you "won". They might just skip you when they finally "give a raise to everyone".
I decided to become a programmer, the first time I got an "Out of memory error", bc the code was too big. But the computer had 8K or something :D
I work for a German company. They run their own DC (unfortunately, I'm not privy to precise numbers I could share, but we must be in the 1000s of hardware servers). Why? Because our (German) clients don't thrust US…
OmniTracker, the web UI! Imagine how fun it is to type a "stack-trace" into your issue tracker, because it doesn't even support copy-and-paste... Luckily, unknown to most people, I guess.
Same. We use 64-bit ints as "Entity IDs", and countless other stuff. Saying that it's a "parser problem" is not really helpful, bc many parsers refuse to support 64-bit ints, even if they could, bc compatibility with…
Even if you force them to give you a raise now, that doesn't mean you "won". They might just skip you when they finally "give a raise to everyone".
I decided to become a programmer, the first time I got an "Out of memory error", bc the code was too big. But the computer had 8K or something :D
I work for a German company. They run their own DC (unfortunately, I'm not privy to precise numbers I could share, but we must be in the 1000s of hardware servers). Why? Because our (German) clients don't thrust US…
OmniTracker, the web UI! Imagine how fun it is to type a "stack-trace" into your issue tracker, because it doesn't even support copy-and-paste... Luckily, unknown to most people, I guess.