4d ago

Evil Ones

74 comments

Every programming language has it's own weakness but we still learned it and pretend it will never happened to us.
Moral of the story : JUST LEARN PROGRAMMING LANGUAGE THAT CAN MAKE YOU MORE MONEY NOT THE ONE YOU LIKE, BECAUSE YOU NEED MONEY
- “JavaScript” isn’t so bad with React + Next + Typescript + Lodash + …

If a chicken could code, it would probably work like JavaScript. This is accurate.
When I had a flock, for example, sometimes one would flip over a bucket onto itself and then decide it must be night and go to sleep.
- if a chicken could code, it would use CHICKEN.
  
  Oh this is actually a real thing I was rolling my eyes like "just show me the clicks and clucks in the code"
  
  Chicken chicken chicken
- What if it was on purpose?
  
  I wouldn't put it past them. The one I saw climb into the hay loft on an upright human ladder knew what it was doing. Ditto for the time they excavated out a secret base under the deck and started laying eggs inside.
  Never a dull moment with those guys.

of there was proof that chickens could contribute to the Ecmascript standard I would probably stop being vegan tbf
- if cows could be on the C++ committee i would eat nothing but hamburgers

Wait, do vegetables have good feelings or evil ones??
- Even more evil, trust me, I lived with one once
  
  I find the hardest part about eating vegetables is getting around the wheelchair.
  
  Hol' up a minute

Javascript and not Coq?
- There is also PHP
- You Coqsucker.

I’ve been programming in typescript recently, and can I say. I fucking hate JavaScript and typescript. It’s such a pain so much odd behaviors.
- I like custom types and them being able to follow custom interfaces; it makes for great type safety that almost no other language can guarantee!
  What I'm saying is I'm learning Rust.
  
  Exactly
- Lol name one outside of it's well known equality rules that linters check for.
  Also, name the language you think is better.
  Because for those of us who have coded in languages that are actually bad, hearing people complain about triple equals signs for the millionth time seems pretty lame.
  
  Recently I encountered an issue with “casting”. I had a class “foo” and a class “bar” that extended class foo. I made a list of class “foo” and added “bar” objects to the list. But when I tried use objects from “foo” list and cast them to bar and attempted to use a “bar” member function I got a runtime error saying it didn’t exists maybe this was user error but it doesn’t align with what I come to expect from languages.
  I just feel like instead of slapping some silly abstraction on a language we should actually work on integrating a proper type safe language in its stead.
  
  @masterspace "Undeclared variable" is a runtime error.
  Perl.
  
  JavaScript only has a single number type, so 0.0 is the same as 0. Thus when you are sending a JS object as JSON, in certain situations it will literally change 0.0 to 0 for you and send that instead (same with any number that has a zero decimal). This will cause casting errors in other languages when they attempt to deserialize ints into doubles or floats.

JavaScript bad!
- Hahaha! True

Our mass media can incite fear of chickens, pigs, and cattle. Then their existence itself can be defined as a terrorist act. We'll redefine vegan to mean only those that eat terrorists to save the other animals. Actual vegans can call themselves "vegetablers". Nothing changes and everyone feels good because if they don't feel good then they're not human.
- If the existence is a terroristic act how do you call farmers who breed these creatures on purpose? I guess the new 'vegans' could then eat the very last generation of terroristic animals and then everyone needs to go 'vegetabler'. I guess that doesn't sound too bad to those that are vegetabler on purpose. ;)
  
  If the existence is a terroristic act how do you call farmers who breed these creatures on purpose?
  Capitalists.

Plants are alive!

why do beards make men shitheels ?
even santa only gives the good stuff to rich kids
- Look at those butthurt downvotes, haha. Currently 2 - 4.
  Let me reach around mine to give you an upvote.

Honestly the meme of 'JavaScript bad' is so tired and outdated it's ridiculous. It made sense 14 years ago before invention of Typescript and ES5/6+, but these days it basically just shows ignorance or the blind regurgitation of a decade old meme.
Typescript is hands down the most pleasant language to work in, followed closely by the more modern compiled ones like Go, Swift, C#, and miles ahead of widely used legacy ones like Java, and PHP etc. and the white space, untyped, nightmare that is python.
I'm like 99% sure that it's just because JavaScript / Typescript is so common that for anyone who doesn't start with it, it's the second language they learn, and at that point they're just whiny and butthurt about learning a new language.
- Nothing says language of the year better than a language that needs to be compiled to an inefficient interpreted language made for browsers and then grossly stuffed into a stripped out Chrome engine to serve as backend. All filled with thousands of dependencies badly managed through npm to overcome the lack of a standard library actually useful for backend stuff.
  
  Oh I'm sorry, I was waiting for you to name a more successful cross platform development language and framework?
  Oh, you're listing Java, and Xamarin, and otherwise rewriting the same app 4 times? Cool beans bro. Great resourcing choices you've made.
  All filled with thousands of dependencies badly managed through npm to overcome the lack of a standard library actually useful for backend stuff.
  Bruh, this is the dumbest fucking complaint. "Open source language relies on open source packages, OMG WHAT?!?!!"
  Please do go ahead and show me the OOTB OAuth library that comes with your backend language of choice, or kindly stfu about everything you need being provided by the language and not by third party libraries.
- As a TypeScript dev, TypeScript is not pleasant to work with at all. I don't love Java or C# but I'd take them any day of the week over anything JS-based. TypeScript provides the illusion of type safety without actually providing full type safety because of one random library whose functionality you depend on that returns and takes in any instead of using generic types. Unlike pretty much any other statically typed language, compiled TypeScript will do nothing to ensure typing at runtime, and won't error at all if something else gets passed in until you try to use a method or field that it doesn't have. It will just fail silently unless you add type checking to your functions/methods that are already annotated as taking in your desired types. Languages like Java and C# would throw an exception immediately when you try to cast the value, and languages like Rust and Go wouldn't even compile unless you either handle the case or panic at that exact location. Pretty much the only language that handles this worse is Python (and maybe Lua? I don't really know much about Lua though).
  TLDR; TypeScript in theory is very different from TypeScript in practice and that difference makes it very annoying to use.
  Bonus meme:
  
  I have next to no experience with TypeScript, but want to make a case in defence of Python: Python does not pretend to have any kind of type safety, and more or less actively encourages duck typing.
  Now, you can like or dislike duck typing, but for the kind of quick and dirty scripting or proof of concept prototyping that I think Python excels at, duck typing can help you get the job done much more efficiently.
  In my opinion, it's much more frustrating to work with a language that pretends to be type safe while not being so.
  Because of this, I regularly turn off the type checking on my python linter, because it's throwing warnings about "invalid types", due to incomplete or outdated docs, when I know for a fact that the function in question works with whatever type I'm giving it. There is really no such thing as an "invalid type" in Python, because it's a language that does not intend to be type-safe.
  
  Pretty much the only language that handles this worse is Python (and maybe Lua? I don't really know much about Lua though).
  This is the case for literally all interpreted languages, and is an inherent part of them being interpreted.
  However, while I recognize that can happen, I've literally never come across it in my time working on Typescript. I'm not sure what third party libraries you're relying on but the most popular OAuth libraries, ORMs, frontend component libraries, state management libraries, graphing libraries, etc. are all written in pure Typescript these days.
- That’s just what I’d expect an evil chicken to say.
- Few people use just Typescript, though - there's always dangerously exposed native libraries in the mix.
  
  I would somewhat disagree. These days virtually every popular library on npm is pure typescript and every new project I see at a company is pure typescript, with only legacy migrations of old systems still mixing the two.
- Typescript is hands down the most pleasant language to work in
  Agreed. But doesn't make "JavaScript bad" any less true..
- I learned today, that in JavaScript
  javascript
  
  [2,-2,6,-7].sort()
  
  WTF is it casting it to string or something?

74 comments