Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Codux: Visual IDE for React

codux.com

Post reply on HN
Print view View original

31–40 of 51 posts

Re: Codux: Visual IDE for React

#31

Post by benatkin »

nadawix wrote: post #10
CharlesW wrote: post #5

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)?

This is the first visual IDE to edit React Typescript code. Even code you created outside of it. 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 wh…

That seems like an arbitrary standard

Re: Codux: Visual IDE for React

#32

Post by preommr »

nadawix wrote: post #10
CharlesW wrote: post #5

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)?

This is the first visual IDE to edit React Typescript code. Even code you created outside of it. 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 wh…

> This is the first visual IDE to edit React Typescript code. Even code you created outside of it.

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?

Re: Codux: Visual IDE for React

#33

Post by Caseee »

nextaccountic wrote: post #15

Is it open source, open core, or just proprietary? How much does it cost?

Codux dev team member here.

During the beta phase Codux is free for use, and open source projects will always have free access. In regards to open sourcing the actual project and code, we plan on releasing some of its parts back to the community, other parts will remain closed.

Re: Codux: Visual IDE for React

#34

Post by xet7 »

kneebonian wrote: post #4

I get a vaguely MS Access/Windows Forms feel from this, "Now you too can build Frontend Website design and not have to spend so much on developers!" I also have to wonder if you still have to hack the code and what not how does this make it so much different from just using hot reloading features to see things?

For MS Access feel, there's also this PHP/MySQL GPLv3 FOSS project:

https://www.nubuilder.com

Re: Codux: Visual IDE for React

#35

Post by Caseee »

kneebonian wrote: post #4

I get a vaguely MS Access/Windows Forms feel from this, "Now you too can build Frontend Website design and not have to spend so much on developers!" I also have to wonder if you still have to hack the code and what not how does this make it so much different from just using hot reloading features to see things?

Codux isn't meant to replace developers, we made it for them (including ourselves). And sure, it gives you a hot-reloading experience, but also much more, like the ability to visually edit your components on stage in the same place you're viewing them.

Re: Codux: Visual IDE for React

#36

Post by no_wizard »

This is something I wish could mash with Figma in some way, so Figma edits could be reflected back into the application in an intelligent way.

I really like this. I think some folks have correctly identified that it may be incorrectly used (my opinion) as a low-code editor. It very well could be however I see it living in a different space:

There has long been attempts at getting tools like Figma to produce assets that work with engineers. What I haven't seen until Codux is a tool that takes my work as an engineer and (mostly) correctly makes it editable and "design ready" for designers.

Thats the niche I see this living in, and is one I'd like to use it for, is to take the React components created for our design system and give designers the ability to run with it to create mock ups etc. This would cut alot of translation overhead and boilerplate significantly while keeping design and engineering on the same "page" because it reflects the changes correctly based on the source and available props, bringing things closer to usable.

Re: Codux: Visual IDE for React

#37

Post by yaaang »

no_wizard wrote: post #36

This is something I wish could mash with Figma in some way, so Figma edits could be reflected back into the application in an intelligent way. I really like this. I think some folks have correctly identified that it may be incorrectly used (my opinion) as a low-code editor. It very well could be however I see it living in a different space: There has long been attempts at getting tools like Figma to produce assets th…

It depends on how extensive the edits/created components are that you want to allow the non-developer to make.

https://plasmic.app experimented with bringing together design+code in this way, but we found it didn't take hold outside of small visual tweaks. We ended up taking a different approach to this specific problem - letting you build screens out of React components from your codebase (and have the screens rendered back into your app). This has worked out much better for us, as the surface area for coordination between the developer and non-developer is much narrower and less brittle as a workflow (and at the same time doesn't put an IDE in front of the non-developer).

Re: Codux: Visual IDE for React

#38

Post by MuffinFlavored »

no_wizard wrote: post #36

This is something I wish could mash with Figma in some way, so Figma edits could be reflected back into the application in an intelligent way. I really like this. I think some folks have correctly identified that it may be incorrectly used (my opinion) as a low-code editor. It very well could be however I see it living in a different space: There has long been attempts at getting tools like Figma to produce assets th…

> There has long been attempts at getting tools like Figma to produce assets that work with engineers.

How many engineers would prefer fumbling through Figma output instead of just writing it themselves?

I guess the answer to that depends on the quality of the Figma output, which is probably measured in maintainability?

Re: Codux: Visual IDE for React

#40

Post by falleng0d »

After messing around with the tutorial project I think that this is a great tool that has a lot of potential.

As developers are very particular and tend to customize their IDEs with a lot of extensions, I don't think this will replace the tools we have.

But I do think that we should be able to customize a lot more

The code editor especially should be able to receive most of the common settings such as font, theme, ...

I would also like to see some support for common utilities such as prettier and eslint. This will not replace the primary IDE but when I need to use it I expect it to do a proper job.

Post reply on HN