2 ms·
Ah yes, we've at least gotten over the inline css ... although we seem to have gotten back into inline javascript with various ng-click="doSomething()" thingies
by Swizec 12y ago
Ah yes, we've at least gotten over the inline css ... although we seem to have gotten back into inline javascript with various ng-click="doSomething()" thingies.
- agumonkey 12y agoSadly yes, and worse, people seem to enjoy this way. sigh
- Swizec 12y agoAs I wrote a few weeks ago[1], I hate this way but I can't argue with results. It's quicker and simpler to solve low-hanging fruit this way, which lets me spend cycles on application logic. [1] http://swizec.com/blog/i-was-wrong-about-angularjs/swizec/6602 http://swizec.com/blog/i-was-wrong-about-angularjs/swizec/66...
- DougBTX 12y agoA good talk about that is "Pete Hunt: React: Rethinking best practices -- JSConf EU 2013" http://www.youtube.com/watch?v=x7cQ3mrcKaY http://www.youtube.com/watch?v=x7cQ3mrcKaY
- ufo 12y agoWhen you do everything from inside JS (as Pete advocates) then you have a real programming language to work with. Inline JS in the HTML is much less expressive.
- deleted 12y ago[deleted]