3 ms·
I generally agree with him regarding the picking your tools part, but some of it seems a contradiction. Tools where you build the app by writing code in
by GhotiFish 12y ago
I generally agree with him regarding the picking your tools part, but some of it seems a contradiction.
Tools where you build the app by writing code in
JavaScript files, not by trying to declare too much of
your app logic in your HTML (no AngularJS, sorry).
The DOM is simply a view of the state and reacts to
changes in the model layer.
That's pretty much Angular's philosophy as well.
that said, this:
People who already know JavaScript should be able to
work on the app without lots of knowledge about a
specific tool or framework.
IMO trumps all.
- HenrikJoreteg 12y agoMy main point was just that it's never felt right for me personally when I try to write too much logic into templates directly. Because at the point where you hit the limit of what that abstraction supports you now have to solve that problem outside of the abstraction, fragmenting your code. /me shrugs It's all about how much you actually need to customize beyond what you get from something like angular out of the box. I'm not wanting to fight a framework war, that's for sure. If angular works well for someone, that's awesome they should keep using it. The item you pointed out in the second quote, yup... that's a big deal for us.