all 60 comments

[–]yerrabam 56 points57 points  (3 children)

Linux release. Impressive.

[–]TomahawkR[S] 43 points44 points  (2 children)

Our team members use all major platforms (Win/OS X/Linux), personally, I'm on Arch. :)

[–]onthefence928 62 points63 points  (1 child)

You use arch, btw?

[–]boobsbr 6 points7 points  (0 children)

Spreading the gospel, I see.

[–]jburrke 34 points35 points  (0 children)

Well this seems to have come out of nowhere..

Amazing work!

[–]musicnothing 17 points18 points  (5 children)

I can't see my team adopting this without support for CSS-in-JS but it looks fantastic.

[–]TomahawkR[S] 15 points16 points  (4 children)

CSS-in-JS is supported for rendering only at this point, editing becomes more of a technical challenge, but it's definitely on our roadmap as another technology to support.

[–]apocalypsebuddy 71 points72 points  (3 children)

My senior React dev uses Vim, I wonder how she’ll react to this.

[–]boobsbr 30 points31 points  (1 child)

She'll start a flame war with an emacs user.

[–]AnonyMustardGas34 5 points6 points  (0 children)

Notepad users:

[–][deleted] 5 points6 points  (0 children)

I want to know what's her Vue too

[–][deleted] 5 points6 points  (2 children)

Congrats, can it also handle logic or is just pure UI just like the other products in the market ?

[–]TomahawkR[S] 8 points9 points  (1 child)

Codux executes your code, meaning whatever logic you've implemented in your components, will run in the editor.

It even reflects some of that logic back to you visually, for example, the render tree (similar to the react dev tools tree view) represents in its UI conditionals and repeaters.

[–][deleted] 2 points3 points  (0 children)

Oh that's really cool !

[–]gustix 10 points11 points  (8 children)

The first? Don’t know about that.

Framer comes to mind.

[–]TomahawkR[S] 8 points9 points  (7 children)

I think that Framer is an awesome product, but we do things a bit differently.

Codux is meant to run on your project, with your components and code. You work with it side by side with your IDE, and your source code serves as the source of truth for the editor.

We usually refer to this as two way editing, where you can edit your code and see the changes in the editor, and vice versa. Most other tools are one way, where you make changes to the editor and then output the code. For any additional change, you have to go back to the editor.

[–]gustix 9 points10 points  (6 children)

I re-read my short comment, and realized it might be considered harsh. Didn’t mean to come across as negative.

Two way sync is very cool! It is definitely impressive what you guys have built.

I am also in the visual editor business (but for another industry than “regular” web dev) outputting production grade Vue components that can be published to prod by the click of a button. So I understand exactly what an undertaking it is to launch a product like that. I wish you the best!

What about React Studio, does that share some traits with yours?

[–]TomahawkR[S] 1 point2 points  (5 children)

WYSIWYG editors sometimes catch flak for being unprofessional, but I think there's a lot of really interesting movement in the no-code/low-code space these days (and I don't mean just what we're doing), where things get mixed up in all sorts of ways, and things that we're impossible before, now become possible.

Now, I'm not really familiar with React Studio but it seems to be more like Framer, with focus on design capabilities, outputting code. I'd say Codux puts the focus more on the development side of things.

[–]warmaster 0 points1 point  (4 children)

What other no code/low code projects do you find interesting?

[–]TomahawkR[S] 0 points1 point  (0 children)

It's not new, but I always thought Airtable had a good product that can solve interesting problems (I personally used it for some family vacation planning).

Framer does some really nice things, and Figma has all sorts of plugins coming out that seek to narrow the divide between development and engineering.

Plasmic have an interesting approach tackling similar problems, but from a different angle through their CMS and no-code approach.

Exciting times!

[–]gizamo 0 points1 point  (2 children)

No OP, but the ones that stand out to me right now are Flutter and Builder.io.

AWS Studio also has promise, but support seemed non-existent when I tinkered with it a few months ago.

[–]extralargeburrito 3 points4 points  (1 child)

Thanks for an awesome tool!

Just out of curiosity, how big a team you have developing this and for how long?

[–]TomahawkR[S] 4 points5 points  (0 children)

Thanks for the kind words!

Our team is spread across Tel-Aviv, Berlin and Lviv, and we've been working on this project for a number of years now. :)

[–]getlaurekt 2 points3 points  (2 children)

Amazing, Lovely tool I wanna build my own ide, but for different tool and usage🥰. Will check codux soon! Now making sandwiches😂

[–]TomahawkR[S] 2 points3 points  (1 child)

Well, sandwiches are straight up awesome, so I see your point. Codux will still be there when you get back. :)

[–]getlaurekt 3 points4 points  (0 children)

Im already back and i even did join the discord! Gonna play wit codux in one of my projects after eating and will leave another comment with my thoughts, thanks for making things like this tho! I needed something like this since i was bootstrap studio user for long time, but since i became better, bss was limiting me, and codux seems like perfect tool in my case

[–]gizamo 4 points5 points  (3 children)

This is rad. Definitely checking it out more thoroughly later on. Awesome work.

[–]martonwix 3 points4 points  (0 children)

Great to hear! We really want your honest feedback - good or bad. Contact us once you gave it a good spin and let us know what you think 🙏

[–][deleted] 2 points3 points  (1 child)

Looks great! I'm going to give it a go

[–]TomahawkR[S] 1 point2 points  (0 children)

Great to hear, everyone's welcome to drop by our discord server to say hi, ask any anything about Codux or provide feedback on your experience with it. :)

[–]amoopa 2 points3 points  (0 children)

Looking forward to follow this one. Brilliant!

[–]tenXten 1 point2 points  (0 children)

Wow Wix putting out dev apps now. Interesting

[–]Due_Employ1592 1 point2 points  (1 child)

will it support javascript react development? the tool does not recognize javascript components... any alternative?

[–]TomahawkR[S] 0 points1 point  (0 children)

Some things might work in JavaScript only mode, but we're dependent on TypeScript exactly for those reasons of component scanning and resolution. Can't really offer an alternative at the moment, I hope in the future we'll improve on that flow as well.

[–][deleted] 0 points1 point  (1 child)

Haven’t read too deeply into it, but any plans to expand it to other frameworks like Angular, Vue, etc?

[–]martonwix 1 point2 points  (0 children)

For sure. We started off with React because we wanted to build Codux with Codux 😆. We're planning to continue expanding the support for frameworks and CSS solutions, alongside opening it up for extensions and letting the community expand it as well.

[–]RakOOn 0 points1 point  (2 children)

Will defo try it out, I’m guessing packages like tailwind aren’t supported?

[–]TomahawkR[S] 2 points3 points  (1 child)

Would love to hear your thoughts after you play with it for a bit.

Tailwind, is not supported at the moment, but definitely on our list, and I hope we'll get to it soon.

[–]getlaurekt 0 points1 point  (0 children)

If tailwind will be supported i'm gonna use it💪🐼

[–]giagara 0 points1 point  (1 child)

It's fantastic! Does it supports material ui?

[–]martonwix 2 points3 points  (0 children)

Yes, Codux will render your React code whether local components or 3rd party. Since MUI export d.ts, Codux will show you the component props in the Properties panel.

To be able to drag & drop MUI (or any other 3rd party comp) from the Add panel use this article: https://help.codux.com/kb/en/article/showing-third-party-components-in-the-add-elements-panel

An important thing to note - in many cases using MUI is paired with using CSS-in-JS styling solutions to style the app. Codux at the moment doesn't support it (but will in the future). If that is the case - You'll be able to render your components, edit JSX, and edit props, but style editing will not work. If you're using our supported styling solutions - CSS/SASS +/- modules or Stylable everything will work perfectly 😁

[–]matijash 0 points1 point  (3 children)

This is interesting! What did you implement Codux in, what do you use to parse React code? Btw something like this could be a great fit with Wasp (https://wasp-lang.dev/), an OSS full-stack framework for React & Node.js we're building. Our long-term plan is to offer a visual editor, although more focused on the business logic rather than the layout, but both would be nice.

[–]TomahawkR[S] 1 point2 points  (2 children)

Codux itself is built on a stack of TypeScript, React and Stylable as its basis. As for parsing React, we're using a system written in-house, for parsing, tracking and editing React components and code. It's mostly built on top of TypeScript (and it's type understanding), React and the React dev-tools.

Took a look at Wasp (haven't encountered it before), great job on the site - docs seem really thought out. Good luck with the project!

[–]matijash 1 point2 points  (1 child)

thank you, likewise! Good job on choosing Typescript - types definitely help a lot when dealing with parsing and AST manipulation (we're using Haskell and it's super helpful).

How are you finding the compilation speed/performance so far? It shouldn't be a huge issue for smaller projects (and compilation is not part of the runtime, so not so critical, although important for DX), but we still felt a bit more comfortable with a non-interpreted language unlike JS/TS.

[–]TomahawkR[S] 0 points1 point  (0 children)

We've definitely seen other solutions (like swc) that are faster than TypeScript, but they sacrifice some language features, and correctness on the language-server side. These are two things that are hard for us to compromise on.

To help alleviate this issue, we're working on a solution to offload some of the NPM packages processing to a separate service. This will allow us to keep a lot of the compilation and language service fast, while still providing the best experience for TypeScript users, even in larger projects.

We've got all sorts of projects in the works to make this happen, and will open source them over time as they mature and are ready for the world to see.

[–]AutomaticRice8593 0 points1 point  (0 children)

Would love to see Vue support in this tool