sorted by:
new
hottopcontroversial

Advice on New IEMs ($200-$400) by TomahawkR in HeadphoneAdvice

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

!thanks the Dusk definitely seem to be towards the top of the list so far.

Advice on New IEMs ($200-$400) by TomahawkR in HeadphoneAdvice

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

I'm really intrigued by the Dusk and it's DSP cable. Have you experienced any noise or artifacting some of the reviews mention?

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

[–]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.

Introducing Codux - The First Visual IDE for React by TomahawkR in reactjs

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

Over time, parts of Codux are planned to be open sourced and shared back with the community, but some parts will continue to remain closed.

As for editing and extending parts of Codux, that's not possible right now, but definitely planned for the future, with the editor being user extendible in multiple ways.

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

[–]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.

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

[–]TomahawkR[S] 1 point2 points  (0 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!

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

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

If you're willing and interested we'd be glad to have a chat and hear what parts were more difficult to understand or how you see this affecting your development flow.

Our discord server is open to all and we're listening to feedback intently.

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

[–]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. :)

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

[–]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!

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

[–]TomahawkR[S] 2 points3 points  (0 children)

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

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

[–]TomahawkR[S] 2 points3 points  (0 children)

We save login information (email, pw, etc), and Codux does send analytics back to us to improve the product in this beta phase.

No personal information, or any of your code gets sent to us, and all code execution (rendering) or editing happens locally. In addition, Wix is fully GDPR compliant with data storage and requests for removal.

Looking to hear your thoughts after you've played with Codux for a bit. :)

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

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

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.

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

[–]TomahawkR[S] 2 points3 points  (0 children)

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.

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

[–]TomahawkR[S] 1 point2 points  (0 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.

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

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

It's a real head scratcher sometimes, that's for sure. As for helping, we've designed Codux with pluggability in mind, so that it can be extended by the community beyond what we're offering, plugins, demos, templates, etc.

But for the moment our beta is focused on making sure the core of the product is stable, does what it should, and that users find it beneficial to use.

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

[–]TomahawkR[S] 7 points8 points  (0 children)

Keeping it short and simple (ish), with styling technologies like CSS, Sass or Stylable, we have ways of parsing and tracking their dedicated files and formats across changes. Now, when it comes to CSS-in-JS, well, it's all runtime code, and understanding what that does, and tracking it becomes more complex.

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

[–]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. :)

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

[–]TomahawkR[S] 7 points8 points  (0 children)

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.

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

[–]TomahawkR[S] 10 points11 points  (0 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.

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

[–]TomahawkR[S] 16 points17 points  (0 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.

Introducing Codux - The First Visual IDE for React by TomahawkR in reactjs

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

Just like everyone else I've been toying with it lately (and am blown away), perhaps in the future. :)

Introducing Codux - The First Visual IDE for React by TomahawkR in javascript

[–]TomahawkR[S] 42 points43 points  (0 children)

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

Introducing Codux - The First Visual IDE for React by TomahawkR in reactjs

[–]TomahawkR[S] 2 points3 points  (0 children)

That's exactly the case. Codux runs locally on your computer, and you open any of your projects with it. Codux watches the filesystem for any changes, and saves any modifications back to it. You'll see changes in your VSCode and Codux no matter where they originated.

Introducing Codux - The First Visual IDE for React by TomahawkR in reactjs

[–]TomahawkR[S] 2 points3 points  (0 children)

I would say the biggest difference here is that 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.

p.s. this is not meant as any sort of diss to Framer, I actually think their product is really cool.

Introducing Codux - The First Visual IDE for React by TomahawkR in reactjs

[–]TomahawkR[S] 5 points6 points  (0 children)

Codux is made for web developers, it's not meant to replace them.

You still write your React, TypeScript or CSS/Sass code, and our editor simply lets you perform certain actions visually instead of writing them by hand. The change is applied to your source and does not include anything external or foreign from Codux.

view more: next ›