John Peters. Angular, React, Typescript and JavaScript.
That explains everything lol :)
On a serious note: Always keep in mind that the world is HUGE and there are always millions of people and businesses with use cases, goals and requirements that vastly differ from yours. E.g. one of the reasons CSS frameworks will exist forever is they allow for rapid prototyping. As a backend developer I often need to mock some stuff quickly (including for production) and without Tailwind (or whatever framework a dev prefers) that would take much more time. And that's just one of the example use cases. And I personally am very skilled in pure CSS, been working with it since the early beginning, the cascade is in my blood etc - I do write vanilla CSS quickly. And yet, CSS frameworks save time (and money). Thus, they will continue to exist whether you like it or not.
I'd also rephrase mentions of SCSS/SASS - while pre-processors do have their place for some use cases, post-processors (hello PostCSS) are better for most. With CSS evolving on its own, PostCSS actually allows you to write cutting-edge CSS before it is even adopted by the browsers. Just like Babel.
Thanks for the tip Ihor, I've never heard of PostCSS, but will look into it. I mentioned SCSS because with Angular View Encapsulation developers can't go deep into CSS on current page. They once recommend using NgDeep for this but, it has been deprecated.
The only work around is to define the queries in the root; and using SCSS, it's simple to do.
Gosh this is one of the things about Angular that drives me bonkers. All these host elements that screw up any sense of positional CSS which is especially frustrating for things like tab components.
I actually like the ViewEncapluation as I can literally copy a CSS file and just import it and it's encapsulated (whereas in React I'd probably make a foo.css get wrapped by foo.modulecss if I'm using CSS Modules). Tradeoffs I guess. But in terms of CSS and HTML Angular is the most frustrating for me (vs. Vue 3, Svelte and React -- I code in all of these)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That explains everything lol :)
On a serious note: Always keep in mind that the world is HUGE and there are always millions of people and businesses with use cases, goals and requirements that vastly differ from yours. E.g. one of the reasons CSS frameworks will exist forever is they allow for rapid prototyping. As a backend developer I often need to mock some stuff quickly (including for production) and without Tailwind (or whatever framework a dev prefers) that would take much more time. And that's just one of the example use cases. And I personally am very skilled in pure CSS, been working with it since the early beginning, the cascade is in my blood etc - I do write vanilla CSS quickly. And yet, CSS frameworks save time (and money). Thus, they will continue to exist whether you like it or not.
I updated the article to reflect these ideas, Thanks!
I'd also rephrase mentions of SCSS/SASS - while pre-processors do have their place for some use cases, post-processors (hello PostCSS) are better for most. With CSS evolving on its own, PostCSS actually allows you to write cutting-edge CSS before it is even adopted by the browsers. Just like Babel.
Thanks for the tip Ihor, I've never heard of PostCSS, but will look into it. I mentioned SCSS because with Angular View Encapsulation developers can't go deep into CSS on current page. They once recommend using NgDeep for this but, it has been deprecated.
The only work around is to define the queries in the root; and using SCSS, it's simple to do.
This is actually a good example of where SCSS may be beneficial!
Gosh this is one of the things about Angular that drives me bonkers. All these host elements that screw up any sense of positional CSS which is especially frustrating for things like tab components.
I actually like the ViewEncapluation as I can literally copy a CSS file and just import it and it's encapsulated (whereas in React I'd probably make a foo.css get wrapped by foo.modulecss if I'm using CSS Modules). Tradeoffs I guess. But in terms of CSS and HTML Angular is the most frustrating for me (vs. Vue 3, Svelte and React -- I code in all of these)