If the creators are hanging out, what does "first visual IDE for React" mean when there have been other visual IDEs for React (and React frameworks like Next.js)?
You can run it on an existing project, and start creating pull requests to your existing code. as long as the project fits our supported technologies.
The other tools you mentioned create code, but cannot edit existing code.
This becomes a real problem when a developer changes this exported code, which causes conflicts when someone edits it in the editor.
We edit the code directly, with visual changes translated into code changes, letting developers and designers collaborate on code and through pull requests.
Utopia had two-way sync, but that project may be in a coma. Henosia I just learned about today. It's a tough-but-important problem to solve — best of luck building a successful solution!
tbh I find this to be misleading then. Me, and I am sure many others interested in web dev, have seen products that focus on react with a visual IDE, maybe this product is way better, but it seems like a poor first impression when I immediately think "that's bullshit" about the first thing I see.
Also how does this handle complex project setups? Like lets say i have a constant that gets injected by my bundler (e.g. webpack) that produces different results based on the environment, or middlewares? How does it display individual components when it might need to load a bunch of dependencies?
An IDE should have the text in the forefront, enable all the things an IDE normally does, as well as have a preview mode where you can visually edit.
A Dreamweaver for React.
In their defense it looks like they expect you to focus on the text part in your normal editor.
But at that point they should make this a VSCode extension or something.
Having your source being modified from two programs is... silly.