Why is starting a new project in React beyond your comprehension? Have you actually tried starting a new project? A serious one, not a personal blog, etc. The new frameworks have amazing DX -- I've used them all (Solid, Qwik, Svelte) and I wouldn't think twice to commit to any one of them over React, but only if ignoring ecosystem. Somebody is going to comment that React eco is just a bunch of wrapped JS libs but that's horsesht. I'm still more productive with React because of eco despite wanting nothing more than to use the shiniest newest tech. Is all this to say one cannot build a serious app modulo React? Of course not. But for me, productivity wins out over DX.
Regarding perf, if the app truly requires the added perf that SQS provide then, yes, pick the best tool for the job, naturally, but I venture to say a lot of devs seek added perf whether they need it or not. React is perfectly capable of delivering performant experiences for a wide variety of app categories.
The only valid scenario would be if React can do something that cannot be done with anything else. This scenario, however, doesn't exist.
You're "more productive" because of the large ecosystem. I bet other allegedly smaller ecosystems like Vue make you as productive. So why stick to the losing horse?
Furthermore, this is your case. Your personal situation makes you more productive in React. I largely don't care about ecosystem as I enjoy programming, so if I have to create a reusable something, I'll enjoy it, and also, I am capable of coding pretty much anything that I need. I rarely need specialties catered by third parties. So your argument, while holds some value in your case, can only extend to the general public if React held something unique, something that only exists for React.
I bet you'd be as productive with other ecosystems, while freeing yourself from the chains of React. All you have to do is get through the learning curve.
Don't go to Vegas. Did you read the part where I stated that I've used Solid, Qwik, and Svelte? Great DX, but, again, I'm simply more productive on React.
I have zero interest in Svelte after using it -- I agree it's a great DX but it's not my cup of tea (prefer JSX) and it's associated with Vercel. Qwik is my favorite of the three, but it's been a year since I was last deep into it and Qwikui is still struggling to get out of beta (with dev team seemingly all but disbanded), nor has Qwik itself gained any traction in terms of adoption, which makes it too risky. Solid seems the most promising because the community seems to love it, but, again, there needs to be something more than one-man shadcn ripoff UI frameworks and the like avail before I can consider moving over. Example, Kobalt was arguably the best option at the time I was last using Solid and it's still a one-man show with with a whole three issues closed in the past month (out of a paltry 8 active issues) -- meaning it's dormant. And I'm just using UI framework as an example.
It seems you're also assuming that that persons not wishing bridge gaps are incapable of doing so. By all means, if it brings you joy, go developer your own UI framework or take a dep on a one-man show, or bring Motion up to parity with Framer/Motion (react flavor), or roll your own TanStack Query tools (because TSQ tools are only supported on React), and so on. I can better spend my time elsewhere.
I see. It sounded like you really wanted out of React, but seems that 2 issues get in your way: You don't wish to put an extra effort, even if it is a one-time thing (i. e. create a component library for your preferred technology that can be reused many times), and your preferred technology is not popular at all.
My advice under these circumstances would be: If you have the time, contribute to the greater good of your favorite technology. Do open-source. Give back to the community since the community (albeit of a different technology) has had your back for years.
Yes, it does bring me joy to program. I spent today creating the POC of a router library for Svelte v5. The most satisfactory part is its intellisense around the route parameters:
Just by typing the path prop, TypeScript will infer the parameter names. Definitely satisfactory.
If you, reader, are interested in this router, wait a week or so. I have only finished the POC. Monitor the repositories of the WJSoftware organization. It will appear there.
It was less about wanting out of React versus my natural inclination to chase shiny object. It cost me too much time so I'm sticking w/ React for now. I gets the job done. As an aside -- open-source is not exclusive to non-React projects and/or you're assuming I haven't open sourced anything.
Well, with your "I have better things to do than give my time away to a bunch of unknowns out there for free" attitude, one is inclined to think that, but please, by all means, correct me. Show me the marvels you have contributed.
I came here at 4 AM , planning to start building an app , but im sleeping depressed :( (Currently an react developer, hvnt explored much outside other than what my job asks me to do.- U can call me an mediocre developer)
Nice roast btw.
Why are you with intel if you don't like losing horses ?;)
It's just a job. I'll contribute to it so long IT wants it. I'll have no issues going elsewhere when the time comes. Don't think I have any sentiments towards the company I work for, since no company has ever had any feelings for me or any other employee.
Why is starting a new project in React beyond your comprehension? Have you actually tried starting a new project? A serious one, not a personal blog, etc. The new frameworks have amazing DX -- I've used them all (Solid, Qwik, Svelte) and I wouldn't think twice to commit to any one of them over React, but only if ignoring ecosystem. Somebody is going to comment that React eco is just a bunch of wrapped JS libs but that's horsesht. I'm still more productive with React because of eco despite wanting nothing more than to use the shiniest newest tech. Is all this to say one cannot build a serious app modulo React? Of course not. But for me, productivity wins out over DX.
Regarding perf, if the app truly requires the added perf that SQS provide then, yes, pick the best tool for the job, naturally, but I venture to say a lot of devs seek added perf whether they need it or not. React is perfectly capable of delivering performant experiences for a wide variety of app categories.
The only valid scenario would be if React can do something that cannot be done with anything else. This scenario, however, doesn't exist.
You're "more productive" because of the large ecosystem. I bet other allegedly smaller ecosystems like Vue make you as productive. So why stick to the losing horse?
Furthermore, this is your case. Your personal situation makes you more productive in React. I largely don't care about ecosystem as I enjoy programming, so if I have to create a reusable something, I'll enjoy it, and also, I am capable of coding pretty much anything that I need. I rarely need specialties catered by third parties. So your argument, while holds some value in your case, can only extend to the general public if React held something unique, something that only exists for React.
I bet you'd be as productive with other ecosystems, while freeing yourself from the chains of React. All you have to do is get through the learning curve.
This is why it is beyond comprehension.
Don't go to Vegas. Did you read the part where I stated that I've used Solid, Qwik, and Svelte? Great DX, but, again, I'm simply more productive on React.
I have zero interest in Svelte after using it -- I agree it's a great DX but it's not my cup of tea (prefer JSX) and it's associated with Vercel. Qwik is my favorite of the three, but it's been a year since I was last deep into it and Qwikui is still struggling to get out of beta (with dev team seemingly all but disbanded), nor has Qwik itself gained any traction in terms of adoption, which makes it too risky. Solid seems the most promising because the community seems to love it, but, again, there needs to be something more than one-man shadcn ripoff UI frameworks and the like avail before I can consider moving over. Example, Kobalt was arguably the best option at the time I was last using Solid and it's still a one-man show with with a whole three issues closed in the past month (out of a paltry 8 active issues) -- meaning it's dormant. And I'm just using UI framework as an example.
It seems you're also assuming that that persons not wishing bridge gaps are incapable of doing so. By all means, if it brings you joy, go developer your own UI framework or take a dep on a one-man show, or bring Motion up to parity with Framer/Motion (react flavor), or roll your own TanStack Query tools (because TSQ tools are only supported on React), and so on. I can better spend my time elsewhere.
I see. It sounded like you really wanted out of React, but seems that 2 issues get in your way: You don't wish to put an extra effort, even if it is a one-time thing (i. e. create a component library for your preferred technology that can be reused many times), and your preferred technology is not popular at all.
My advice under these circumstances would be: If you have the time, contribute to the greater good of your favorite technology. Do open-source. Give back to the community since the community (albeit of a different technology) has had your back for years.
Yes, it does bring me joy to program. I spent today creating the POC of a router library for Svelte v5. The most satisfactory part is its intellisense around the route parameters:
Just by typing the
pathprop, TypeScript will infer the parameter names. Definitely satisfactory.If you, reader, are interested in this router, wait a week or so. I have only finished the POC. Monitor the repositories of the WJSoftware organization. It will appear there.
It was less about wanting out of React versus my natural inclination to chase shiny object. It cost me too much time so I'm sticking w/ React for now. I gets the job done. As an aside -- open-source is not exclusive to non-React projects and/or you're assuming I haven't open sourced anything.
Well, with your "I have better things to do than give my time away to a bunch of unknowns out there for free" attitude, one is inclined to think that, but please, by all means, correct me. Show me the marvels you have contributed.
I came here at 4 AM , planning to start building an app , but im sleeping depressed :( (Currently an react developer, hvnt explored much outside other than what my job asks me to do.- U can call me an mediocre developer)
Nice roast btw.
Why are you with intel if you don't like losing horses ?;)
It's just a job. I'll contribute to it so long IT wants it. I'll have no issues going elsewhere when the time comes. Don't think I have any sentiments towards the company I work for, since no company has ever had any feelings for me or any other employee.
Truth has been spoken.