I agree, but really what is an ideal alternative to even the other major frameworks?
As I mentioned in the post I LOVED the idea of #UseThePlatform as a replacement to shipping these frameworks only to be met with frustration in development.
Not only a lack of solutions to common problems (external library support) but also the lack of community aka googling answers to commonly found problems/bugs in development.
I would much rather ship something to production that has a few performance flaws to later be optimized than delaying the release for months trying to find what I can use to replace it.
I agree with you completely. There are probably alternatives, but we go into "creating your own framework" territory, which is ridiculous if you need to create an app and ship it. Framework has thousands of developer hours invested into it, that provides a lot of value.
I didn't mean to attack you or anything, what I meant was that the author of that article should have listed more solutions, not that you didn't offer them in your article.
Oh no, I didn't take it like that at all. I was just giving my 2 cents on the fact that the "Stop Using" post was maybe steering people down a road I've traveled and experienced a lot of frustration with.
React has saved me countless hours in time and energy both in my personal & professional projects so I felt a strong need to post (some of) the benefits you gain from using 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 agree, but really what is an ideal alternative to even the other major frameworks?
As I mentioned in the post I LOVED the idea of #UseThePlatform as a replacement to shipping these frameworks only to be met with frustration in development.
Not only a lack of solutions to common problems (external library support) but also the lack of community aka googling answers to commonly found problems/bugs in development.
I would much rather ship something to production that has a few performance flaws to later be optimized than delaying the release for months trying to find what I can use to replace it.
I agree with you completely. There are probably alternatives, but we go into "creating your own framework" territory, which is ridiculous if you need to create an app and ship it. Framework has thousands of developer hours invested into it, that provides a lot of value.
I didn't mean to attack you or anything, what I meant was that the author of that article should have listed more solutions, not that you didn't offer them in your article.
Oh no, I didn't take it like that at all. I was just giving my 2 cents on the fact that the "Stop Using" post was maybe steering people down a road I've traveled and experienced a lot of frustration with.
React has saved me countless hours in time and energy both in my personal & professional projects so I felt a strong need to post (some of) the benefits you gain from using it.