anutron
Re:Why It’s a Good Idea to Be a JavaScript Developer, and What it Take...
on Monday December 16, 2013 @12:17PM (#6916162)
I (the author) would agree that it's insane, but it's often the case that when products get created, there's only one UI developer at the start. More importantly, if you DO have all those skills, you'll keep getting those kinds of opportunities.
Re:Why It’s a Good Idea to Be a JavaScript Developer, and What it Take...
on Monday December 16, 2013 @12:16PM (#6916148)
note: I'm the author of the article here.
I'd say rather than chase after things for their perceived value, do what you love. A lot of that esoteric knowledge is just the byproduct of doing what you like to do for years on end. If you like what you're doing now, keep doing it, get better, learn more.
As for few products being built around one superhero, that's absolutely true. But it's often the case that when products get created, there's only one UI developer at the start. In the article, the guy I'm referring to was one of the first developers at simple.com - how cool is that?
Re:Why It’s a Good Idea to Be a JavaScript Developer, and What it Take...
on Monday December 16, 2013 @12:13PM (#6916128)
JavaScript has been around long enough to arguably be called a mature language. It doesn't really need to be "better" (any more than any other language). It's the environment that's crappy - the Browser. But those aren't going anywhere. You're going to be waiting a long time before something supplants it.
Re:Why It’s a Good Idea to Be a JavaScript Developer, and What it Take...
on Monday December 16, 2013 @12:07PM (#6916076)
Not always an option for startups... When you have a super small team, this role is often filled by only one hard-to-find person.
Re:Why It’s a Good Idea to Be a JavaScript Developer, and What it Take...
on Monday December 16, 2013 @12:03PM (#6916050)
I believe I say in the article that if you have 5 of the 7 things that you're in solid shape. You certainly don't have to have any of these things, but having them helps...
/the author
Re:MooTools: The Open Source Magic Behind Cloudera Desktop UI
on Monday October 19, 2009 @07:51PM (#891373)
If you can't be bothered to author your code using only ONE JavaScript library, then yes, name space "pollution" is not very friendly. But if you write all your code using one framework, then the name space is yours to use, which to me is not pollution. It's only a pain when you want to use several frameworks, and the only reason I can imagine to to do that is to use plugins from more than one. That's laziness if you ask me; rather than ask your users to download two libraries, you should author your own version for your framework of choice.