You must log in or register to comment.
I personally think this comic would have been a lot funnier if it had no caption
Can someone help me understand this joke? Strongly typed languages generally have way better IDE support so this doesn’t make much sense to me at all
Theyre just bad at programming
The joke is taking “strongly typed” literally- by applying too much “strength” (force) physically on the keys and breaking the keyboards
Hey guys I think I might be stupid. Good lord, wow.
I thought it was because the protagonist isn’t familiar with strongly typed languages so that he get frustrated so much and he breaks his keyboards to let the rage out.
You are typing strongly, which breaks your keyboard.
Buy a Model-M and don’t look back. Things are built tough.
Plus vintage models were designed for folks that coded in C/C++. So you know they’re up to the task. ;)
The factory in Kentucky that used to make them was bought out by the employees when IBM stopped doing them and still makes new buckling-spring keyboards, so you can get new ones.
Called Unicomp.
They do have a nipple mouse variant with mouse buttons. I have one, and I don’t recommend that. The buckling spring keys are as good as the day I got it, but I eventually wore out the mouse buttons, and I’ve no idea whether they’ve moved to new switches for the mouse buttons.
That’s also why I love duck typing but don’t find it practical. I can only have so much bread lying around.
Turns out JS is strongly typed after all!
Can someone explain the term? I’ve been in IT for 25 years, but haven’t written anything but Powershell.
When programming, data is stored in variables. In a weakly typed language you define a variable and you can put anything in it. Numbers, text, whatever. In a strongly typed language when you define a variable you also have to define what it can take. If you define a variable that can hold numbers, it can only hold numbers and never text or anything else.
Weak typing makes code easier to write and more flexible while strong typing makes code more secure and harder to accidentally break. It’s mostly a preference thing in the end.
Just to add to this all data is ultimately stored as ones and zeros. In order to translate it to a piece of text or some type of number the computer needs to determine what type of data it represents. If the computer guesses the wrong type you just get garbage. Languages like C allow you to store data without rigid type definitions, it is up to the programmer to make sure the code gets the type right. In a strongly typed language you are not allowed to use variables of one type as some other type without some explicit conversion. It is safer but a little annoying.
It should be noted that “strong typing” and “weak typing” don’t have the same precise definition as static/dynamic typing.
It normally means either some point on the strict/lenient/unityped spectrum the author thinks is strict typed, or static typed.
And yeah, it’s a useless name, we could as well use it for languages that make the developer break keyboards.
I learned to type on an IBM Selectric that weighed more than a Volkswagen. Godzilla couldn’t have broken that thing.
Those things were marvelous. You could hear each keystroke slam into the platen two houses down.
When you hate typed, you could vent your fury!
Using CamelCase or snake_case?
spOnGebObcASe
SQL won’t judge you.
