5 ms·
The general idea behind directives is still there in 2.0. JSX does come with one fatal flaw in order to accomplish what it does - it requires extra build tooli
by Bahamut 12y ago
The general idea behind directives is still there in 2.0. JSX does come with one fatal flaw in order to accomplish what it does - it requires extra build tooling from the get go, which makes it that much more difficult for junior developers to pick it up, along with the assault of other technologies, code structure, and paradigms they have to pick up at the same time. The beauty of the declarative direction of Angular is that it still is just regular old HTML.
I do agree with #2, and it is a large part of why Angular is changing so drastically with 2.0 - part of this can be evidenced in 1.x with components being split into official optional modules (ngRoute, ngSanitize, ngAnimate, ngTouch, etc.).
I somewhat agree with #3 - I feel like in order to properly use any framework, there is no way around combing through documentation and the source code. I have found that true with most libraries I have used. Angular's documentation at least has the benefit of being very thorough compared to most at least. I do disagree that libraries should only use what programmers already know though - we should be pursuing how to best foster productivity in the long term, and sometimes this means exploring new patterns.
- colinramsay 12y agoI think JSX can be used by doing nothing more than including the JSX transformer via a script tag.
- Bahamut 12y agoYou're correct, but it is not recommended to use that in production.
- TheAceOfHearts 12y agoOf course not, but if you're working in a small development environment it's great :P.
- rdtsc 12y ago> JSX does come with one fatal flaw in order to accomplish what it does - it requires extra build tooling from the get go, which makes it that much more difficult for junior developers to pick it up, along with the assault of other technologies, code structure, and paradigms they have to pick up at the same time. However if they managed to understand directives, digest cycles, dependency injection, MVVM, angular services, $scope, controllers (confession: as an amateur I haven't been able too), handling JSX build step doesn't seem like a stumbling block.
- cmdkeen 12y agoIf #1 was a concern they wouldn't be pushing AtScript. Angular has already conceded that extra build steps are a good thing, so why not add JSX into the mix as well.
- Bahamut 12y agoFor the record, that is one thing I don't like about 2.0 - I rather have less required build tools. Frontend development is getting quite complex, and I fear that it makes it harder to build up competent developers in the long term - it's already hard enough to teach friends trying to learn about everything else in development. I am fine working with this sort of tooling myself, but it is more of a concern coming from a lead/senior engineer viewpoint.