5 ms·
The article is fucking crazy. Web apps and software in general should be about separations of concerns not technologies. When in React you define the structur
by gaastonsr 10y ago
The article is fucking crazy.
Web apps and software in general should be about separations of concerns not technologies.
When in React you define the structure + the events your component can receive you are wrapping up that concern nicely in a component.
And BY NO MEANS React is solving any data modeling problem, conversely, they have left that part out of the scope of React and some REALLY NICE options have come out. The most famous is Redux.
And by the way React is not a framework is just a library.
- mbrowne 10y agoI had some other doubts about the article as well, but didn't make any other comments yet because I am still researching React and web components. It appears you may be right that React does not force you into an overly coupled design, but I still think the article makes a good point about how people are writing React components (among many other library-specific component libraries) instead of native web components, which may be contributing to web components lagging behind. But I was just reading that web components can be used quite successfully as building blocks for larger React components or integrated with React in other ways, so I don't see why it has to be one or the other. And yes, sorry to call React a framework - I know it's a library and should not have called it a framework.
- grifter2000 10y agoYep. Trash article is trash.