4 ms·
I'm curious now, what disadvantages of React could outweight the entanglement of reactive state management and undocumented lifecycle. I could understand that y
by sesm 3y ago
I'm curious now, what disadvantages of React could outweight the entanglement of reactive state management and undocumented lifecycle. I could understand that you could have the same issues with state management if you were using MobX with React, but undocumented component lifecycle sounds crazy.
- adamnemecek 3y agoOut of the box, React provides much less than Svelte. Also the mental model of Svelte is one tenth of React. I was able to start building stuff after like 3 hours of reading Svelte tutorial. I have done the same with React several time and every time I left with “I kind of see how to do things but I’m unsure how to build larger things with this”.
- fullstackchris 3y agobut there are literally libraries on top of libraries to immediately provide in react what svelte might provide "out of the box". the best thing too is that these hooks are all open source - so you can either install a package directly, or pick and choose and install whatever hook you need. idk, i'm dying on the hill that react is unopinionated for a reason, i think it can be morphed and molded to so many use cases
- mschild 3y agoI agree, but what that freedom in reality often means, at least from what I've seen, is a patchwork of dozen libraries and dependencies that make large scale projects more complex than they need to be. That's not the fault of React, but it is a consequence of it.
- fullstackchris 3y agoand when you run into something svelte simply cannot do?
- adamnemecek 3y agoLike what?
- adamnemecek 3y agoThat’s the point. I don’t want libraries on libraries. I want an integrated approach. How are the use cases for these libraries different?
- satvikpendem 3y agoThen why not Angular?
- adamnemecek 3y agoBecause it’s terrible.
- satvikpendem 3y agoBut it's the integrated approach you're talking about, what is terrible about Angular?
- adamnemecek 3y agoI just checked it’s so much worse than I remember <div *ngFor="let product of products"> <h3> {{ product.name }} </h3> </div>
- satvikpendem 3y agoAnd that is why I use React instead.
- adamnemecek 3y agoNot integrated enough for me.
- satvikpendem 3y agoIf you want something that's not "libraries on libraries," use Angular. And if you don't like Angular, you have proved my point, that the "integrated approach" is simply not good, because you cannot make your own decisions to improve parts you don't like. Hence why I said I use React and not Angular.
- spuz 3y agoI said there was a reactive state model that you have to get your head around in Svelte, but this is still much easier and simpler to do than it is in React in my experience. I'm not trying to pursuade anyone either way but I do want to dispell the notion that the mental model of Svelte is so straightforward that there is nothing to "learn" as the article claims because that will eventually lead to disappointment. Like I said, I think Svelte as a technology is great, so I'd rather people had the right expectations if they are going to give it a go.