30 ms·
Give react.js a try. I am not a web developer either. Saw Angular first. Got lost in the soup of new terminology -- digest cycles, dependency injections, servic
by rdtsc 12y ago
Give react.js a try. I am not a web developer either. Saw Angular first. Got lost in the soup of new terminology -- digest cycles, dependency injections, services, factories, scopes. I suspect Angular probably made sense to already experienced JS developers who had to struggle with jQuery before...
But then I tried react and the whole idea of unidirectional event flow made sense, JSX was a little confusing but it was simple to grasp the need and use of it.
- jdlshore 12y ago> I suspect Angular probably made sense to already experienced JS developers who had to struggle with jQuery before... Not really. Angular is its own little world of terminology and ideas. I've heard it said that Angular users don't learn JavaScript, they learn Angular.
- pyre 12y agoYou could say the same thing about (e.g.) Ember.js. It comes with all sorts of 'goodies' in its class hierarchies.
- taurath 12y agoAbsolutely the case - I enjoy Javascript coding but can't stand having to follow Angular's opinions on everything that should be done to the DOM. Having a consistent model of interaction is great, and Angular enforces that while giving you quite a few nice tricks, but it does it in a way that feels so far away from JS itself that I'd bet it actually hurts your Javascript composition to know Angular.
- saosebastiao 12y agoThat is the route that I'm currently going down. So far, it has been a joy to work with. My only complaints to date about React have been the incompleteness in the documentation about events, and the jsx attribute renaming (ex. className="foo" => class="foo"). I also worry (but haven't been disappointed yet) about pre-1.0 instability. I really like the acknowledgment that UIs are fundamentally state machines, and React's explicit connection between state and rendering. I do wish they would introduce more featured state transition/events modeling...Something similar to Jake Gordon's javascript-state-machine[1] library would be amazing. [1] https://github.com/jakesgordon/javascript-state-machine https://github.com/jakesgordon/javascript-state-machine
- grayrest 12y ago> jsx attribute renaming (ex. className="foo" => class="foo") That annoys everybody. It's that way because the JSX attributes map directly onto the DOM attributes which in turn are named that way to avoid ES3 reserved keywords. It's supposed to be less magic/surprising but far more people interact with JSX (e.g. designers) than work with raw DOM manipulation.
- serve_yay 12y agoTo me Angular seems like a bunch of Java folks took a look at font-end programming and decided it should be more like Java.
- HashHishBang 12y agoAs a Java programmer I'm reasonably confident that didn't happen.
- emilis_info 12y agoPlease explain. The concepts on Angular have nothing to do with JavaScript. The new changes they propose to JavaScript borrow most from Dart, which in the eyes of a JavaScript programmer is an attempt to turn JavaScript into Java.
- aliakhtar 12y agoJava devs have far better options than writing javascript: http://www.gwtproject.org/learnmore-sdk.html http://www.gwtproject.org/learnmore-sdk.html