5 ms·
He didn't even get to the part that I find confusing; the naming of things. componentDidMount? componentWillMount? Wtf is mounting? This isn't a goddamn harddri
by jbob2000 8y ago
He didn't even get to the part that I find confusing; the naming of things. componentDidMount? componentWillMount? Wtf is mounting? This isn't a goddamn harddrive. Props? Do you mean properties? or arguments? Wtf is a prop? Reconciliation? Portals? The fuck?
And then, to top it all off, you can't just use React, you need to pair it with a set of other libraries, each with their own set of ridiculous jargon and paradigms.
I honestly think a bunch of very talented Facebook devs got bored and decided to make something complex just so they could keep themselves entertained. And then other developers followed suit because it has cool words that make you sound important and inflate your ego, even though it's doing the same shit the web has been doing for 30 years.
- watty 8y agoIf you think React is complicated stay far far away from Angular.
- jbob2000 8y agoHa! I'm a full time Angular dev. It's full of the same kind of bullshit, but for some reason, I found it easier to "get".
- deleted 8y ago[deleted]
- chrisco255 8y agoNah, it solved huge problems in UI for complex projects. One-way data flow, functional component abstraction, virtual DOM, simple & minimal API (11 methods). It encourages componentization in a way that no other framework quite does as nicely. Because the components are one-way, it's trivial to break up a component that has gotten "too big". I mean, a simple react component is: const HelloPerson = ({ person }) => <div>Hello, {person}</div>; ReactDOM.render(<HelloPerson person="ChrisCo" />, document.getElementById("root")); That's elegant as fuck.