4 ms·
The problem with all these frameworks is you end up with a huge mess of markup unrelated to your application, and then have to have another tab open the entire
by aphextron 8y ago
The problem with all these frameworks is you end up with a huge mess of markup unrelated to your application, and then have to have another tab open the entire time with documentation making sure you spell every class name right and dont miss a single <div> tag.
Native web components with shadow DOM styling are the way to go forward IMO. Otherwise stuff like this leads to namespace issues and horrible regressions caused when the inevitable need to override something occurs and your only option is to !important a property.
- coldtea 8y ago>Native web components with shadow DOM styling are the way to go forward IMO Frameworks like React and Angular are 10x more popular than "native web components". So if "having to have another tab open the entire time with documentation making sure you spell every class name right and dont miss a single <div> tag" is your concern, it's misplaced. People will be more familiar with those others than with native web components.