News for hackers. Stuff that matters.
Re:If you had to start over, what technologies would you lea... by lstamour on Monday February 10, 2014 @11:01AM (#7211724)
Ah but then you get http://www.100percentjs.com/just-like-grunt-gulp-browserify-... (and HN discussion) ... of course, despite this, I'm in your camp. Even as I'm doing mobile and now learning modern/ISO C++ for cross-platform development, the strengths that originally got me hired were in web programming and you can always pick up enough to work with views in one of the big technologies, be it Wordpress/Drupal (sigh), Rails (half sigh) or more abstracted GWT/ASP.NET components. (meh)

That said, I'm not sure where the bar is, even in web. Writing Chrome extensions and apps? Javascript injection on mobile? Dart? Web Components? Ember? (ouch) Angular, or React.js? Or a certain company's stack like Closure? And don't forget security vulnerabilities and keeping up with OWASP checklists or UX improvements, prototyping in HTML. And then there's performance considerations, eg. what Ilya Grigorik writes about these days. And touch screens, mobile, responsive... Front-end has a lot of transferrable skills, but it's a complex beast too, often full of legacy code.

Re:If you had to start over, what technologies would you lea... by davidjnelson on Monday February 10, 2014 @07:43PM (#7214879)
Angular. Seriously.
Re:If you had to start over, what technologies would you lea... by lstamour on Tuesday February 11, 2014 @10:46AM (#7218113)
Today that makes sense. But the react guys (at Facebook) have a point, Angular (developed for LOB apps at Google) can be slow unless you write optimizations for update looping, etc. Eventually Angular directives might be better supported natively as polymer-style components (those are slower still now, and lack IE support), or Dart might rise in popularity, at least beyond that of Angular. And then you've Google Closure, which, like any company-sponsored project/library will get the job done but at the expense of some amount of lock-in, since these projects tend to already have lots of internal code to build with. I'm not sure the answer's that simple. That said, I agree that for today's mix of browsers, Angular has the best compatibility if you want more than React.js. Ember just took too long to settle down and still has oddities in data handling.