Software patterns and their contexts, a thread:pic.twitter.com/WUKFvyapfi
Show this thread
-
For the same reason, no small company should be using web components. They exist to solve big company organizational problems.
Show this thread
This statemenr doesn't make a lot of sense to me. Web components have many use cases. Maybe you mean small companies shouldn't use them instead of what?
-
-
Big companies need isolated contexts around portions of a page because they have dozens or hundreds of teams that each own little bits of UI, & they all need to do their work without breaking other teams.
-
If you have one team doing all your UI, all those isolation boundaries are unneeded overhead.
-
I get your premise, but the technology behind WC and the pattern of componentization is not bound to the multi-team paradigm. That's a little like saying OOP is overkill if you're doing everything by yourself; just use Pascal.
-
That’s kind of true tbh. A long procedure is better than the wrong set of small objects.
-
Procedures must be small and compact. Easy to read and reuse. That is what WC are all about. You may be a small company but overtime you may have many projects, where you want to reuse code.
-
You can do that in front end code without WC.
-
I still feel what you're really saying is that most UI developers you know are more comfortable with other tools. Those comfortable with web components would still choose them where they find them useful, whether working completely alone or in a megacorp.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.