6 ms·
The sheer amount of Java code written is nearly unfathomable. Maybe 3 million developers each churning out 20000 lines a year. That's about 60 billion lines of
by nrjdhsbsid 10y ago
The sheer amount of Java code written is nearly unfathomable. Maybe 3 million developers each churning out 20000 lines a year. That's about 60 billion lines of Java code per year. There could easily be over a trillion lines of Java out there.
- nom 10y agoIf that is true, it's stuff for nightmares. Here is something I made to lighten the mood: https://i.imgur.com/qzOPn85.png https://i.imgur.com/qzOPn85.png .. or maybe this is even scarier. I'm not sure. edit: downvotes from java devs incoming :D
- nrjdhsbsid 10y agoHahahaha Edit: I'm a Java guy too, don't get why some people get so butthurt over things :) At least it's not JavaScript with infinity,null,undefined, and NaN. Oh and null!=null which is hilarious
- nom 10y agoLOL yeah.. don't get me started about JS :D. I more of a C++ guy, but I like Java very much and have used it extensively in the past. I personally like a good C/C++ joke and can't understand why the Java devs are so serious. Apparently nobody is allowed to joke about Java, it's serious business :D
- mhink 10y agoFor what it's worth, you should _always_ be using triple-equals in Javascript unless you have an overwhelmingly good reason not to. Many of the weird Javascript-isms people like to complain about are due to surprising type coercions, which don't happen with triple-equals (which behaves as you would expect- value equality without type coercion for primitive types and reference equality otherwise.)
- echelon 10y agoFor someone who uses a more than one language on a regular basis, triple equals is an annoying break with convention. It shouldn't be that easy to make a mistake by simply missing an extra character. This is one of many reasons I've taken to using TypeScript for all of my web frontend projects.
- robocat 10y agoHowever you still run into the same problems with > , < , <= , and =>. So you need to really really understand the corner cases (same as with C++).
- crazy2be 10y agoYou mean NaN != NaN. null == null is true, and null != null is false. NaN != NaN is surprising, but is not unique to JavaScript. As far as I know, this is the case in every language, and is mandated by the IEEE 754 specification. However, it does come up in JavaScript more often than other places, since NaN is really easy to get (+{} => NaN, 1 - '' => NaN, etc, etc).
- grkvlt 10y agoIn SQL, 'NULL <> NULL' is true as well, you have to use 'NULL IS NULL' instead, so the concept has a long and somewhat respectable pedigree...