JS BLOCKER VS ANGULAR 2 CODE
It provides reusable code that sits there waiting for the consuming application to call into it.Ī framework takes the opposite approach. The fundamental difference between a framework and a library is that a library is passive.
![js blocker vs angular 2 js blocker vs angular 2](https://lh4.ggpht.com/_N9kpbq3FL74/TKN8Awgl3RI/AAAAAAAAED0/jPewRuUymfk/youtube_instant.png)
JQuery is not a framework / Ruby on Rails is a framework React is not a framework /Angular is a framework There seems to be a lot of confusion about what a framework is. I've shown one of those colleagues some standard Vue stuff - he 'gets' it, but thinks it's way too loose. A couple of colleagues have done Angular at big companies, and the structure (and extra layers) mapped very well to their existing way of thinking.
![js blocker vs angular 2 js blocker vs angular 2](https://www.alliancetek.com/blog/image.axd?picture=2020%2f7%2fEssential+Distinctions+Between+Angular+vs.+AngularJS.jpg)
Angular was getting overbearing for me (especially on projects where I'm the only/primary js person), but I understand the appeal. I've done some Angular (versions 1-5) but mostly Vue these days. "It's going to be easier once we convert all the legacy class -based components". "But you have no tests around the 4 functional ones -" "How do you know? You don't have any tests around them at all" "We're converting everything - class-based components are so hard to test" you have 85 class-based components already, and 4 functional ones." "Oh, we don't do class-based here - that's so outdated!". I've come in to a handful of React projects in the past 3 years, and each team says that "their" way is the "correct" way, and whatever I was doing elsewhere is just dumb/wrong/outdated/slow/bad/untestable, etc. Which, on its own, doesn't necessarily bug me as much as the attitude I've run in to. > Every React project that I've walked into has looked completely different from each other. In React apps you'll typically see low-level JavaScript code doing this type of stuff inside of markup. Formatting and manipulating string data is a very typical problem that views need to solve. They introduce tight coupling between the view and other app layers - I use them a lot, but they're no substitute for dependency injection).
![js blocker vs angular 2 js blocker vs angular 2](https://infostans.com/wp-content/uploads/2021/01/talk_with_min.png)
I like a framework that encourages developers to separate their concerns and get integration code, routing config, state management and the like into a separate layer of the app (and no, react hooks are not a good solution for this. I have yet to find a decent forms solution for React. Form controls are the standard way of interacting with the end-user and so the typical front-end application will work heavily with forms in some shape or form (no pun intended). Give me a sane, reactive forms module out of the box. Let me configure my routing without having to use components. Give me code splitting / bundles right out of the box. Give me a template language to keep my view logic separate from my markup.
![js blocker vs angular 2 js blocker vs angular 2](https://droidhere.com/wp-content/uploads/2017/02/AngularJS-vs-Angular-2-Which-One-Is-Better.png)
Give me view encapsulation so I can write straight-up SASS and have it scoped to a component. Most components I've seen are a large hodgepodge of markup, styles and logic. While you can separate your markup from your view logic and styles with discipline, most React devs don't. So you have massive bundles being pulled into the client and the majority of code contained in those bundles are not going to be needed for a given user session because no user is going to use all features when they login.Īlso, JSX reminds me of PHP code in the 90s. One common complaint about Angular is that it is "bloated." Yet every React project I've seen pulls in a million 3rd party libraries to solve the most trivial problems, and I've seen very few React apps that implement code splitting of features. Every React project that I've walked into has looked completely different from each other. I'll take an "opinionated" framework any day of the week over what I see in the React ecosystem. I've worked on more React projects than Angular, and am very competent in both.