I think React and JSX somehow snuck in without having to take the cost on themselves. ESLint is required for hooks because of the hooks update model/syntax. If those arrays weren't there or Hook rules didn't exist (and that is 100% a runtime possibility, see MobX, etc...) then we wouldn't need ESLint.
I think this perspective is correct and that is what is being carved out but this is monumental undertakings spanning years. This can be a differentiator for these frameworks. But a framework could just pick up JSX, TypeScript, Prettier, and Babel and not have to deal with any of this and get more or less the same results and not have to re-invent the wheel. I'm not saying they would, but I wonder at times if the existing tools are not just sufficient, and then the developers could get back to working on features and the real things that matter like Concurrent Mode exit transitions. (I kid, CM is important).
I've worked under both paths. In Marko we've been working on the language from day one and in many ways it will be the thing to make the vision possible in terms of granular sub-component partial hydration. But in Solid, I, mostly on my own, used all premade stuff and in a short time re-implemented most features of all major frameworks because I wasn't trying come up with a DSL, or custom create TS support. I wouldn't say it's a React knockoff because of that either.
To be clear someone had to be making these tools, so it isn't like the work isn't being done in this regard. It's just as a framework spending their time here, it needs to be a deliberate calculated decision because it can be an expensive one.
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 think React and JSX somehow snuck in without having to take the cost on themselves. ESLint is required for hooks because of the hooks update model/syntax. If those arrays weren't there or Hook rules didn't exist (and that is 100% a runtime possibility, see MobX, etc...) then we wouldn't need ESLint.
I think this perspective is correct and that is what is being carved out but this is monumental undertakings spanning years. This can be a differentiator for these frameworks. But a framework could just pick up JSX, TypeScript, Prettier, and Babel and not have to deal with any of this and get more or less the same results and not have to re-invent the wheel. I'm not saying they would, but I wonder at times if the existing tools are not just sufficient, and then the developers could get back to working on features and the real things that matter like
Concurrent Modeexit transitions. (I kid, CM is important).I've worked under both paths. In Marko we've been working on the language from day one and in many ways it will be the thing to make the vision possible in terms of granular sub-component partial hydration. But in Solid, I, mostly on my own, used all premade stuff and in a short time re-implemented most features of all major frameworks because I wasn't trying come up with a DSL, or custom create TS support. I wouldn't say it's a React knockoff because of that either.
To be clear someone had to be making these tools, so it isn't like the work isn't being done in this regard. It's just as a framework spending their time here, it needs to be a deliberate calculated decision because it can be an expensive one.