Hate: 'cause of all of its akward things and shitty type system (and I regret some choices made by the community that built tools for its ecosystem).
Love: This is one of few languages that let me program how I want and doesn't make choices for me (I can choose between promises and callbacks, between OOP and FP, etc...).
So, I still enjoy teaching it but when I need to build a robust frontend app, I prefer Elm (and I keep an eye on PureScript).
Four or five years here, after years more with Java, C#, and others; I have complicated feelings about it. I miss strong typing, but not enough to throw TypeScript or Flow on top of it, and then again the borderline-crazy way it works is eminently exploitable on the off-chance you need to make the same object think it's three different things at the same time (which I have). I like the functional aspects with map and reduce and so forth in the standard library. I wish there were fewer gotchas like nested brackets not counting, string addition, and return-on-its-own-line. Overall I think it's a reasonably expressive language and it's been making some big improvements lately but it's never going to escape the history holding it back.
3 years - definite love-hate. It's quirky and frustrating, but useful and powerful. Between ES6, TypeScript, Node, and others it's become a very useful tool.
I love that it's the native language of the browser since I use that for productivity. Bookmarklets and one-off servers for tools and utilities, scripting and automating everything I do - it's the same reason I fell in love with Bash and the terminal.
Been coding in JS for over 15 years and recently having fun with Canvas, the Audio API, and some 3D libraries such as Babylon JS.
I think the only really bad thing about frameworks is that people think they need to use them all the time. Not every website needs to be a web app.
The kind of work you mention is a great example of when you don't need a framework, and it's better to stick to the essentials.
I've been dealing with js off and on for ~5 years. I used to really dislike it, but then ES6 came along and solved a lot of the problems I had with it (wacky scoping, this). I'm coming around to the opinion that ES6 is Good Enough for most things. The problem now (imo) is pushing back against the overproliferation of frameworks that were developed in the Bad Old Days.
Yeah it's ok. 10 years, main language used.
Some of the things people complain about here are real risks, but haven't bothered me in years. It's like working on a farm and getting kicked by a cow. It's a risk, it's a bad thing about cows, but with a bit of experience you learn to avoid it. Or you can take a shortcut and use a linter to tell you what to do.
2 years in.
ES2015: not bad, not bad at all.
Typescript: OH YES!
A resource for anyone wanting to stand out from other candidates while also getting information about the companies they might join.
We’re a place for programmers to stay up-to-date, learn new skills, and share ideas.
We’ll never post without your permission.