4 ms·
I kinda enjoy working with React (because of JSX simplicity and composability). I think you could add easy support for some styling solution like it's done in V
by machiaweliczny 8y ago
I kinda enjoy working with React (because of JSX simplicity and composability). I think you could add easy support for some styling solution like it's done in Vue.
I would focus on making React stable, fast and lightweight but improve on tooling and ecosystem around it.
* I would like blessed way of extracting React components, so they can be reused between projects (like right click in IDE and share) - something like https://bitsrc.io/ https://bitsrc.io/
* react addon for chrome could be much nicer (I have to dig through so many unnamed HoC sometimes).
* you could favor more beginner friendly state solution - something like https://github.com/solkimicreb/react-easy-state https://github.com/solkimicreb/react-easy-state
* you could embrace typescript for easier usage experience
There could be some React plugin(kinda like http://demo.rekit.org/ http://demo.rekit.org/) for editors that would allow for:
* adding mock props to component and preview it on hover, click for example (kinda like styleguidist but with less setup overhead)
* abuse above to provide out of the box image snapshot testing
* simpler ability to add tests (like right click on component and "add assertion", "go to test")
* some structured way of making components
* swap between style, tests, data sources and logic
* run tests only for this component
* etc - basically more streamlined creation experience
Also please focus on debugging when introducing async rendering. (so there won't be errors out of nowhere in stack trace)
- dantheman 8y agotypescript++
- gpmcadam 8y agoI'd just like to voice a -1 for TypeScript (or Flow for that matter) In my experience it doesn't help people, especially at an earlier stage, but rather clutters what people already know about JavaScript. It causes tooling to slow down and ultimately doesn't prevent bugs that could not already be caught by good design and linting. I'm much more of a fan of something like PropTypes, which isn't just superficial, but actually runs on your code in all places and will stop you passing the wrong types to components, regardless of what environment you're in. Otherwise everything else on this list is a +1
- simplify 8y agoTypeScript has been very helpful in our react projects. There isn't much clutter, as usually the only types you define are props and state – things you want to know anyway. TypeScript doesn't prevent any bugs that tests would not, but it does so faster and more concisely. Tooling slowdown depends on your tooling setup; TypeScript can compile JSX on its own. PropTypes are useful if you're transitioning from a plain JS codebase. But if you can start with and go full TS, I highly recommend going that route.
- leeman2016 8y ago+1 for typescript
- rasikjain 8y ago+1 for typescript support. This helps in reducing compile/build time errors and for the devs who are from java/c# background.
- revskill 8y agoPlease no typescript. Instead make Javascript better.