Fuck JavaScript!

Seriously, it's always like this:
> "Hey, look <module name> seem cool, let's try it!"
> Find a tutorial
> Tutorial is 3 to 6 months old
> Should be good
> Everything is deprecated
> Come on...
> Back to C I guess.

It's moving waayyyy to fast.
It's frustrating...

If i write a shitty module in C, then the language itself is shitty, right?

@plusgut I never said JavaScript is shitty or that modules are bad, I'm just saying it's frustrating that things change so fast tutorials become to quickly irrelevant. It's like your local store change the layout of the aisle and how customer check-out is handled every time you go, wouldn't that be unbearable ?

@Hallelouia it's your responsibility as a developer to decide what modules you trust, and that's completly independently true from the language.

@plusgut the problem is finding something you can trust it wouldn't come to my mind to use something unmaintainable becomes everything changes all the time, yet finding a pearl in the sea of modules takes time I don't always have.

@Hallelouia when your employer doesn't give you the time needed it's his fault. That's still no reason to hate the language itself. And it's just not true that *everything* changes

@plusgut I don't hate JavaScript, I was just venting frustration. I thought that was the point of this app =).
I actually really like JavaScript. But we have to "teach" it where I work and seeing things go "whoops that doesn't work like that anymore" in the span of four months is a drag and we are jumping between so many techs we can't be always up to date, here is a non exhaustive list of what we have to "teach" C, PHP, SQL, JavaScript, Python, Ruby, Rails, Flask, MEAN stack. I say teach because the course is there more to provide a frame for self learning, with daily exercises and projects, and we're here to assist our "students" not give them lecture.

@Hallelouia it sure is the purpose of this app. And I usually am frustrated by people who hate on js. That's why rant about this ;)

It's true that there is lots of garbage out there. If you are a teacher and your students want to learn js, then you should teach them the language itself. The fundamentals of the language don't change at all, only features get added but thats it.

And do yourself and the students a favor and teach them how to research libraries/Frameworks and how to find out whats going wrong.

Don't teach them a thousand libraries that won't be much help for the students, when the library doesn't exist in a few years. Teach them the basics and how to maintain and produce quality.

But that's just my 5 cents and how I teach my trainee. Do whatever feels right to you.

@plusgut I saw your love for JS the way you got intense in your comments, I cannot change what we teach. Thanks for the advice, it's been a while since I had construction discussion over the internet =)

@Hallelouia you are welcome :)

Although I am not against @plusgut, this thread might be of interest

https://devrant.io/rants/811732/...

@Hedgepig that's a damn cool shirt, I would wear it.

Yeah, and I do agree with you, I liked js even before the new standards, now it is incredibly expressive.

@Hedgepig I like the old and the new stuff, but I believe that it's important to understand prototypical inheritance and its prototype chain, to understand how the language itself works. And if you know how it works you have an easier job to build stuff, especially with all the new syntactic sugar.

@theScientist nowadays I especially like typescript, it is unbelievably good.

@plusgut I agree with that, typescript is very nice, and visual studio code as such good support it's amazing, guess that's because they're developed by the same company =)

@Hallelouia I would even say that ts is the best thing Microsoft ever did. The only thing that bugs me is, that Function.prototype.bind always returns any, if they fix I see no downsides at all.

@plusgut yeah definitely. People come from classical OOP and expect everything to be the same. Like the "this" keyword is very difficult to grasp but when one really utilises context it becomes incredibly powerful. Functional programming is just win.

@Hedgepig why do you need *this* at functional programming?
I actually think that it's understandable that people think its broken. In my opinion call and apply should be the only way to explicitly change *this* and *this* should not automaticly be the context from the calling function. But it makes sense in a prototype language

Sorry, should have been a separate paragraph @plusgut, it was just it's own point in favour of JS.