4 ms·

More abstraction. What happens when you need to debug this?

by Xiol32 3y ago

graypegg 3y ago
It does seem to output a regular web application based on their description here. > v0 produces code using open-source tools like React, Tailwind CSS, and Shadcn UI. So you can just debug it as always. I guess this product is for someone that COULD make the app they’re generating, but chooses not to. Rather they want an app, that they then only have to refactor.
- leerob 3y ago
  The intention is the output is quite literally your v0. It’s a normal React application, so you’d debug it and build it as such. It’s unlikely you’d take the output and launch right away. You’d probably have other refactoring and modifications first.
prng2021 3y ago
You pay for their next AI service that helps you debug and refactor the code ;) Jokes aside, I think it’s an interesting use of generative AI.
danielvaughn 3y ago
I'm not the biggest fan of this product, but I do have to say that they're pretty intentional about this not being meant for production code. It's more for testing out ideas, hence the name "v0" as in "what happens well before a v1."
- anonzzzies 3y ago
  Sure, however, if you have been around longer, you will know that tons of these will end up in (critical) production anyway. It doesn't matter what label they put on it.
  - danielvaughn 3y ago
    This is indeed a fair point, and part of why I'm not really into it. In theory, you'd save a bunch of time and then use that extra time to add more polish to the product. But in practice, what you'd actually be doing is reading someone else's (or something else's) code, and people who want to rely on AI are not the same people who have the stomach to do that. So they're either going to (a) abandon the generated code and write their own, in which case, what was the point to begin with? Or (b) they're going to just say "fuck it" and push the generated code to prod. Neither of those are good outcomes.
    - gedy 3y ago
      I mean this is no different than life now. You have some MVP code patched up by startup hacker or "CTO", etc, then as team grows it's hard to work with.
cramforce 3y ago
<CTO of Vercel here> We're embracing copy-and-paste with the product rather than increasing abstraction. The tool provides the HTML or React code for building the generated UI. The way you actually use it, is by copy-pasting it into your app. From that moment on your workflow and specially debugging workflow is exactly as before. The tool just writes the first 100 lines of code to get you started with a great UI.
- meiraleal 3y ago
  Hi @cramforce. Vercel's greed destroyed React. You guys should be ashamed of it (but I'm sure you aren't).

More abstraction. What happens when you need to debug this?

by Xiol32 3y ago

More abstraction. What happens when you need to debug this?

It does seem to output a regular web application based on their description here. > v0 produces code using open-source tools like React, Tailwind CSS, and Shadcn UI. So you can just debug it as always. I guess this product is for someone that COULD make the app they’re generating, but chooses not to. Rather they want an app, that they then only have to refactor.

leerob 3y ago
The intention is the output is quite literally your v0. It’s a normal React application, so you’d debug it and build it as such. It’s unlikely you’d take the output and launch right away. You’d probably have other refactoring and modifications first.

prng2021 3y ago

You pay for their next AI service that helps you debug and refactor the code ;) Jokes aside, I think it’s an interesting use of generative AI.

danielvaughn 3y ago

I'm not the biggest fan of this product, but I do have to say that they're pretty intentional about this not being meant for production code. It's more for testing out ideas, hence the name "v0" as in "what happens well before a v1."

anonzzzies 3y ago
Sure, however, if you have been around longer, you will know that tons of these will end up in (critical) production anyway. It doesn't matter what label they put on it.
- danielvaughn 3y ago
  This is indeed a fair point, and part of why I'm not really into it. In theory, you'd save a bunch of time and then use that extra time to add more polish to the product. But in practice, what you'd actually be doing is reading someone else's (or something else's) code, and people who want to rely on AI are not the same people who have the stomach to do that. So they're either going to (a) abandon the generated code and write their own, in which case, what was the point to begin with? Or (b) they're going to just say "fuck it" and push the generated code to prod. Neither of those are good outcomes.
  - gedy 3y ago
    I mean this is no different than life now. You have some MVP code patched up by startup hacker or "CTO", etc, then as team grows it's hard to work with.

cramforce 3y ago

<CTO of Vercel here> We're embracing copy-and-paste with the product rather than increasing abstraction. The tool provides the HTML or React code for building the generated UI. The way you actually use it, is by copy-pasting it into your app. From that moment on your workflow and specially debugging workflow is exactly as before. The tool just writes the first 100 lines of code to get you started with a great UI.

meiraleal 3y ago
Hi @cramforce. Vercel's greed destroyed React. You guys should be ashamed of it (but I'm sure you aren't).