Hahaha oh man... A devrant user just deleted one rant because of “toxic” comments on it😂

That’s what happens when devs try JS for the first time. It drives you mad.

I recorded a video of the whole rant by the way... not sure if I should share it tho 👀

Life is toxic

>__>

@iiii you are the one to blame 😂 don’t even consider leaving your toxicity here, get out of my rant!! 😂

@codepotato <__<

I can relate to being a bit triggered by people elaborating on why I was wrong after I acknowledge I was wrong, but that's why I can't resist doing it myself.

Damn, I missed a juicy rant!
@stuxnet
ǝǝƎǝǝǝƎǝǝǝƎǝƎǝƎǝƎǝǝǝǝǝǝǝǝǝɹ/

@devnulli yes

Waiting for a link

You shouldn’t share it. It t author doesn’t want his data to be online, they shouldn’t be online.

As long as he’s not a public figure, which I assume he’s not.

@just8littleBit
Philosophical:

Does his right to hide his data supercede the rights of others to share theirs?

This instance is closer to, "I am one author of a paper, and I don't want to share it. In the process I am denying the other contributors exposure they want or need."

@SortOfTested it is for sure. But personally I’m all pro ‚right to be forgotten‘

Dicking (meant to be Fucking, but keyboard wants this to be typed) hell dude! Just give us the video!

@Cyanide iPhone?

@just8littleBit Witch?

Was it just another idiot with no fucking idea on how computers even work who blamed JS for floating point rounding?

@Fast-Nop
A webshit was enraged that javascript doesn't implement array comparison via the equality operator like his favorite language.

Rants point out that this may not be ideal for the users of other languages, and many other #goodLanguages also lack this feature.

The thread descends into a war between webshits who love JavaScript and webshits who have to javascript. The needle remained unmoved.

@Cyanide autocorrect from fucking to ducking.. happens to me all the time with the Apple autocorrect.

@Fast-Nop or just new to js.. most backend devs get confused as fuck when using js for the first time. Or second time. Or 10th time😅

@just8littleBit I was demonstrating a common gotcha in VueJS to our dotnet backend devs the other day since it's useful to know for future debugging.

Specifically, there was a property on the component which got set during runtime but various events related to it weren't firing. You js devs out there probably already know what's going on.

To reproduce I removed the initialization of the property so that it wasn't defined during build (I refuse to call it compile) time, and one of the backend devs enthusiastically interjected "That won't run!".

It was adorable.

@ltlian why so condescending?

@iiii Was it? My bad then. It was funny to see that they had an expectation for js to complain about undefined properties like other languages, not that they didn't know about it.

@ltlian the last sentence seems so.

yeah, after working with more "limited" languages with strong and/or static typing, JS feels chaotic AF. Even Python at least fails if something was not created in the constructor and then used elsewhere.

@just8littleBit not Node.js back end devs apparently

Tried Node in uni. Was confused AF and said "fuck that!" and made back end in python for the assignment. I was the only one allowed the privilege of using anything other than Node.

@iiii well yea, if a nodeJs dev gets confused by JS, I’d question his competence 😂