Live data from Hacker News

Show HN: AI Tool Is Now Supporting React, Angular, CSS, Svelte, Vue

webcrumbs.org

1–10 of 79 posts

Re: Show HN: AI Tool Is Now Supporting React, Angular, CSS, Svelte, Vue

#4
I asked for an 'interactive particle simulation' and got a big gray rectangle. Then I clicked regenerate and the page crashed.

To me it's not clear how I would debug the component, I can ask for modifications but not like add log statements, inspect variables, and give feedback on errors.

Re: Show HN: AI Tool Is Now Supporting React, Angular, CSS, Svelte, Vue

#5
How about Svelte 5 with runes mode?

One of the biggest challenges I've encountered so far while working on my SvelteKit with Svelte 5 codebase is that all frontier models struggle to understand differences between major versions of languages and frameworks, leading to a lot of annoying hallucinations. They're fantastic at writing code, but the last mile of figuring out how to fix issues for incorrect APIs or syntax becomes very tedious.

Re: Show HN: AI Tool Is Now Supporting React, Angular, CSS, Svelte, Vue

#6
how hard would it be have a Phoenix .html.heex mode instead of your typical react/angular? .html.heex is really just plain old HTML with tailwind css classes. I could easily copy and paste your generated UIs into my views and play around there! thanks!

Re: Show HN: AI Tool Is Now Supporting React, Angular, CSS, Svelte, Vue

#8
Interesting. I like that better developer tooling is coming out.

That said, this particular tool seems like it's trying to be very hand-holdy, maybe not targeting developers?

For developers Claude Dev seems like a more functional equivalent: https://github.com/saoudrizwan/claude-dev

Re: Show HN: AI Tool Is Now Supporting React, Angular, CSS, Svelte, Vue

#10
I've been using AI models to do frontend design and candidly this doesn't hold a candle to just working directly with the base models.

With the base models you can ask: Hey, make me 5 designs that fit xyz requirements and it will go to work. If you already know front end design, you can take that up a level and pass it an emmet abbreviation of the rough code you want and say only use tailwind colors of sky, zinc, and blue.

I am decidedly not your audience, but if anyone on HN is thinking about how to speed up frontend dev and they are a frontend dev, I'd suggest just messing with the base models more.

Once you get the hang of it, it can be like working with a designer who's feelings don't get hurt... which I love.

"Meh, I don't like those designs, generate me 5 more and feel free to increase the model's temperature up quite a bit to see if you can come up with something cool."

Post reply on HN