3 ms·
"Hmm... How about "let's reduce the need for and dependency on multiple frameworks"? When will that ever be a goal?" That's not a realistic goal, because there
by nawitus 9y ago
"Hmm... How about "let's reduce the need for and dependency on multiple frameworks"? When will that ever be a goal?"
That's not a realistic goal, because there's no common agreement on the framework API. If there were, every framework would have the same API already.
"Surprise, Polymer's API provides a possibility to define that."
Your point being?
"Oh. Right. 6, not 8. I wonder if I ever complained about the number of methods required? Nope, what I complained about is the amount of tedious boilerplate you need to write to implement the most basic and common of things."
You're not intellectually honest, so I will stop this discussion.
- dmitriid 9y agoThe moment I call you out twisting my words, you call me intellectually dishonest. Suit yourself. This entire discussion shows the actual intellectual dishonesty of people who defend WebComponents. > Your point being You, and others are completely entirely blind to the fact that: - WebComponent API is horrible DX - WebComponent API can be made better within the platform, without the need to rely on third-party frameworks. However, if the goal is not to push WebComponents forward, but to sell Polymer to as many devs as possible, it’s not surprising.