I just glanced over the post, so I might be repeating something you already pointed out, but:
I will go all out and say, you don't need React, most times. This applies to almost any other big framework too.
For most people building small apps, the addition of a big framework might seem like a good idea, in the end it makes it so much easier to build right? Yes, but it also adds a lot of complexity, and unneeded clutter. Increasing the time needed to build your project. I've found out that most times I regret using React or Angular, etc... for small personal projects. I would much rather use something like Svelte, or similar low weight ones as you mentioned.
But, for medium/big apps, you most likely need one of the big ones. Which one, depends on a load of factors, from what your company uses, to what makes more sense for the specific purpose. A framework choice should always be evaluated before adopting.
I've made that mistake before, with Ionic, prematurely adopting it and building an app with it, which was re-written completelty in Flutter 2 years after. This could have easily been prevented if we would've tought about it for a minute, as it's quite obvious that Ionic was not a good choice for a big production app.
I totally agree, although you can use Svelte for large apps, in fact I do use Svelte often for those types of apps. As said in the article, I think the biggest reason people use React for things like large apps is that often they require lots of different tools, which aren't always offered by other frameworks like Svelte. Additionally, it can be harder for companies to find the right developers.
The point you bring up about Ionic and Flutter is interesting. Ionic is still used in some large apps, and I think it is starting to get into the same position that I think React is in. It has a much larger ecosystem (the web), but other frameworks like Flutter offer better performance and DX
Nice points, and yeah I think the same. Ecosystems are really important when deciding on a framework, and when one has the biggest ecosystem, it's normal for people to lean towards that framework. And in return more people add to that ecosystem, making it even bigger and so on.
I think it is starting to get into the same position that I think React is in. It has a much larger ecosystem (the web), but other frameworks like Flutter offer better performance and DX
Great way to put it, in terms of ecosystem Ionic and web based frameworks have the lead there, but in terms of DX things like Flutter are way ahead. For now at least, and hopefully the competition learns from them. (Flutter did, they mention React many times in the technical docs, using it as an inspiration on how to do and how to not do things, taking the best and learning from the worst part of it)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I just glanced over the post, so I might be repeating something you already pointed out, but:
I will go all out and say, you don't need React, most times. This applies to almost any other big framework too.
For most people building small apps, the addition of a big framework might seem like a good idea, in the end it makes it so much easier to build right? Yes, but it also adds a lot of complexity, and unneeded clutter. Increasing the time needed to build your project. I've found out that most times I regret using React or Angular, etc... for small personal projects. I would much rather use something like Svelte, or similar low weight ones as you mentioned.
But, for medium/big apps, you most likely need one of the big ones. Which one, depends on a load of factors, from what your company uses, to what makes more sense for the specific purpose. A framework choice should always be evaluated before adopting.
I've made that mistake before, with Ionic, prematurely adopting it and building an app with it, which was re-written completelty in Flutter 2 years after. This could have easily been prevented if we would've tought about it for a minute, as it's quite obvious that Ionic was not a good choice for a big production app.
I totally agree, although you can use Svelte for large apps, in fact I do use Svelte often for those types of apps. As said in the article, I think the biggest reason people use React for things like large apps is that often they require lots of different tools, which aren't always offered by other frameworks like Svelte. Additionally, it can be harder for companies to find the right developers.
The point you bring up about Ionic and Flutter is interesting. Ionic is still used in some large apps, and I think it is starting to get into the same position that I think React is in. It has a much larger ecosystem (the web), but other frameworks like Flutter offer better performance and DX
Nice points, and yeah I think the same. Ecosystems are really important when deciding on a framework, and when one has the biggest ecosystem, it's normal for people to lean towards that framework. And in return more people add to that ecosystem, making it even bigger and so on.
Great way to put it, in terms of ecosystem Ionic and web based frameworks have the lead there, but in terms of DX things like Flutter are way ahead. For now at least, and hopefully the competition learns from them. (Flutter did, they mention React many times in the technical docs, using it as an inspiration on how to do and how to not do things, taking the best and learning from the worst part of it)