3 ms·
Also: >> "Bad developer experience." > Use a framework. What is the point of WebComponents, exactly? Let's quote from here: --- start quote --- Web compone
by dmitriid 9y ago
Also:
>> "Bad developer experience."
> Use a framework.
What is the point of WebComponents, exactly?
Let's quote from here:
--- start quote ---
Web components are a set of web platform APIs that allow you to create new custom, reusable, encapsulated HTML tags to use in web pages and web apps. Custom components and widgets build on the Web Component standards, will work across modern browsers, and can be used with any JavaScript library or framework that works with HTML.
--- end quote ---
They don't allow any of that, do they? Because, as you so eloquently put, "use a framework". As I'm already using a framework (there are dozens of them out there), what is the selling point of WCs exactly?
Oh, right. "Use Polymer", how can I ever forget.
- nawitus 9y ago"What is the point of WebComponents, exactly?" My point differs from the opinion of someone else (not sure who you quoted). " As I'm already using a framework (there are dozens of them out there), what is the selling point of WCs exactly?" To provide interop between frameworks, so that we don't need to write the same components 10 times for each framework. We can just implmenet it once, and use a native API to use it from any framework. "Oh, right. "Use Polymer", how can I ever forget." There are and will be other frameworks which support the Web Components API.