Type Shit

Content 3rd - Follow Software Engineer 3d 4 In 2021 a research paper was published showing most efficient programming languages. Paper is here, but sadly behind the paywall. Gotta love "free academic pursuit" where they take in public money and then hide the results. https:Inkd.ingFTCtMzU Anyway: It shows that if people care about energy footprint of their systems, they need to ditch things like ruby, python and perl. Typescript also is super inefficient too. (e) C (e) Rust (e) C (e) Ada (v) Java (e) Pascal (c) Chapel (v) Lisp (c) Ocaml (c) Fortran (e) Swift (c) Haskell (v) C (e) Go (i) Dart (v) F 6) JavaScript (v) Racket (i) TypeScript (i) Hack 6) PHP (v) Erlang G) Lua (i) Jruby G) Ruby G) Python G) Perl Energy 1.00 1.03 1.34 1.70 1.98 2.14 2.18 2.27 2.40 2.52 2.79 3.10 3.14 3.23 3.83 4.13 4.45 7.91 21.50 24.02 29.30 42.23 45.98 46.54 69.91 75.88 79.58 (c) C (c) Rust (e) C (e) Ada (v) Java (c) Chapel (c) Go (c) Pascal (c) Ocaml (v) C (v) Lisp (c) Haskell (c) Swift (c) Fortran (v) F (i) JavaScript () Dart (v) Racket (i) Hack G) PHP (v) Erlang (i) Jruby () TypeScript (i) Ruby G) Perl (i) Python (i) Lua Time 1.00 1.04 1.56 1.85 1.89 2.14 2.83 3.02 3.09 3.14 3.40 3.55 4.20 4.20 6.30 6.52 6.67 11.27 26.99 27.64 36.71 43.44 46.20 59.34 65.79 71.90 82.91 (c) Pascal (e) Go (e) C (c) Fortran (c) C (c) Ada (c) Rust (v) Lisp (c) Haskell G PHP (c) Swift (i) Python (c) Ocaml (v) C (i) Hack (v) Racket (i) Ruby (c) Chapel (v) F (i) JavaScript (i) 'TypeScript (v) Java G Perl (i) Lua (v) Erlang (i) Dart (i) Jruby Mb 1.00 1.05 1.17 1.24 1.34 1.47 1.54 1.92 2.45 2.57 2.71, 2.803 2.82 2.85 3.34 3.52 3.97 4.00 4.25 4.59 4.69 6.01 6.62 6.72 7.20 8.64 19.84 gO 56 23 comments 6 reposts

Ah, the duality of developer brain function. When naming regular variables, it's absolute chaos - a street brawl of creativity where we somehow end up with monstrosities like tempVarHolder2Final_REAL . But iteration variables? Suddenly we're sophisticated diplomats at a UN summit, unanimously agreeing that a single letter i is the pinnacle of naming convention. And heaven help the junior dev who tries using index instead. We didn't spend years mastering our craft to type five whole characters.

The subtle art of variable naming strikes again. Someone discovered that validateDate() sounds like you're checking if a date is valid, but valiDate() sounds like you're going on a date with someone who's actually worth your time. It's the programming equivalent of realizing you can make your function names do double duty as puns. Why settle for boring technical accuracy when you can have camelCase wordplay that makes your code reviews 10% more entertaining? Your linter won't catch it, but your teammates will either love you or silently judge you. Pro tip: This also works with isValid() vs isVali() for when you need to check if someone's vali-d enough to merge their PR.

Sleeping peacefully until your brain jolts you awake at 3:27 AM because you realized you used = instead of == in that authentication code. That single equals sign just gave admin access to literally everyone. Sweet dreams! Nothing quite like the cold sweat of realizing you've accidentally created the world's most generous authorization system. The fix takes 2 seconds but the existential dread lasts forever.

Content Extreme A Arrays start at 0 e.g: C Statically typed e.g: Rust snakecase variable names e.g: C Current object is self e.g: Rust One number type e.g: TypeScript Garbage-collected e.g: C Objects passed by value e.g: C Tiny standard library e.g: C Extreme B Compromise Arrays start at 1 e.g: Lua Dynamically typed eg: Python camelCase variable names e.g:java Current object is this e.g: C Separate integer and float types e.g: C Manual resource management e.g: C Objects passed by reference e.g: Python Giant standard library e.g: Python Arrays start at 0.5 Changing a variable's type requires calling .changeType () stretchyCamelCase Current obiect is seis "Separate" integer and float types (by name) but they behave the exact same Manually mark resources to be garbage collected Odd arguments by value, even arguments by reference Giant standard library, but it's full of niche stuff and has none of the commonly used stuff

OMG the JavaScript family portrait we never asked for but DESPERATELY needed! 😂 JavaScript: The innocent baby who has NO IDEA what chaos it's about to unleash on the world. Just sitting there like "undefined is not a function? Never heard of her!" TypeScript: The SAME CHILD but with sunglasses because it thinks it's SO COOL with its static typing. "Look at me, I can catch errors at compile time!" WHATEVER, show-off. React JS: JavaScript wearing a beanie because it went to art school and now won't shut up about "components" and "virtual DOM." We get it, you're SPECIAL. Next JS: The emo sibling with the side-swept bangs who thinks it's revolutionary for adding server-side rendering. Honey, Apache was doing that in the 90s!