These descriptions are helpful for a very focused view of one piece of a project. As somebody who writes lit-element every day, I miss React and Angular like crazy for everything else they solve and provide.
Interesting comment. Hopefully after building something with Ficus I can better appreciate Angular. The biggest issue I have is updating projects. Its fine if you only support 1 application but when you have 2 or 3, they start to end up on different versions and when you get back you have to spend a month updating to the latest versions, instead of adding tangible value to the product. Maybe I am just bitter as started on Angular 2 updated app to 3 then 4 then 5 then 6 then moved to another app for a year. Get back to app 1 and now we are 5 versions behind, and we are slowly moving forward again. Update to 7 this release and go from there, I guess.
Try React. Breaking changes are few and far between, generally very easy to update to (a few hours at most for a medium sized app), and they almost always introduce new "new way" of doing thing at least one release before the old way is removed (if it ever is).
Having worked in Angular 1 before there was such a distinction, and watched Angular as it exists now release and evolve... I hear you. React (and the huge JSX ecosystem) is much closer to what you created. And much more stable than all of that.
- Documentation outside of our own (O'reilly books, online courses, etc..)
- SO posts about issues and sticky points
- Patterns for implementation (lack of these is shitty for JR devs. The only place to learn is PR feedback)
- Popular style guides
- IDE plugins
...and many more. Like being able to list POPULAR_LIBRARY_FROM_JOB_DESC on a resume when I can finally leave this job where leadership prioritized the browser's needs over dev comfort and productivity
Also, the advantages of web components and shadow DOM have never shown up. They only make CSS and browser testing more difficult
