Hacker Newsnew | past | comments | ask | show | jobs | submit | MaxLeiter's commentslogin

LLM generated READMEs hurt my eyes

But maybe there is some cool stuff here. A lot of prolific AI-assisted engineers I know have their own advanced plan modes, and the CEO plan mode in the repo is interesting (although very token heavy)

https://github.com/garrytan/gstack/blob/main/plan-ceo-review...


MCPs are great for some use cases

In v0, people can add e.g. Supabase, Neon, or Stripe to their projects with one click. We then auto-connect and auth to the integration’s remote MCP server on behalf of the user.

v0 can then use the tools the integration provider wants users to have, on behalf of the user, with no additional configuration. Query tables, run migrations, whatever. Zero maintenance burden on the team to manage the tools. And if users want to bring their own remote MCPs, that works via the same code path.

We also use various optimizations like a search_tools tool to avoid overfilling context


I can add Supabase or Stripe to my project with zero clicks just by setting up a .envrc.


But then the LLM needs to write its own tools/code for interacting with said service. Which is fine, but slower and it can make mistakes vs officially provided tools



My friend and I were able to give claude a (no longer updated) unity arcade game. It decompiled it and created a one-to-one typescript port so it can run in the browser and now we're adding multiplayer support (for personal use, don't worry HN - we won't be distributing it). I'm very excited for what AI can do for legacy software.


v0 actually can directly copy files out of its examples and then apply edits. This saves it from having to write out the long examples verbatim. The rest of your comment is accurate


The comments are pretty good

From @dangs_successor in the first post:

  We've merged several duplicate threads on this topic. Please keep the discussion substantive and avoid personal attacks.

  Also, yes, my username is silly. The previous dang retired in 2031 and I lost a bet.


We changed the link in the post to go direct to the app store, which has more info. Thanks for the feedback


A lot of react native apps do not feel native. Even more are just low quality. Many v0 users were asking us how exactly we did X or Y to make it feel so good, which is what this post is for.


I like it. This post is the perfect level of detail for people obsessed about UX minutiae.

Personally, I'm not a huge Vercel fan (IMO: lots of hype, business model encourages developer ecosystem lock-in), but this post gave me more trust in the design/UX care that goes into their products (which is a core Vercel strength).


I am obviously bias as a Vercel employee, but I think we actually do a lot to avoid locking our users in. You can read more about our approach here: https://vercel.com/blog/vercel-the-anti-vendor-lock-in-cloud

If that doesn't alleviate your concerns or you disagree, I'd love to hear your thoughts about how we can improve


Are you serious? Your whole business model is built on locking in users and then selling them expensive hosting.


If you can point out how we actually lock you in, that would be more constructive than blanket accusations. I recommend reading the linked post


You accumulate web frameworks and maintainers similar to the winning strategy at Monopoly, until you have implicit control over entire ecosystems. Whether you actually seize that control or not doesn’t even matter, because you are in a position to do so—by strategic neglect, or increased attention to whatever project supports your current business goals best.

No single entity should have that much power, especially no venture-capital backed one.


No sorry, I'm not going to read your PR fluff.

You might want to look at the comments in this thread [1], to get a feeling of the "accusations", as you want to call it... I'm not "accusing" anything, I really couldn't care less, I don't use Vercel/Next.js and never will, but maybe you should read the linked thread, too see how people (at least on HN) see your company.

[1] https://news.ycombinator.com/item?id=45099922


I find the existence of opennext convincing proof of lock-in: https://blog.logrocket.com/opennext-next-js-portability/

Personally, I don’t bother with nextjs at all.


I think the fact that OpenNext can exist speaks to the opposite

A Next.js project can be deployed to a Docker image very easily [1]. If you want to use a provider that has their own infrastructure setup, then yes you need to do some work (that OpenNext does for you). But that's true of practically any framework deploying to a host that does more than just serve the docker container.

[1]: https://nextjs.org/docs/app/getting-started/deploying


Looks good, I appreciate the level of detail especially as bad UX can cause churn on mobile. Since it's React Native, are there plans for an Android version? I guess you guys wanted to get an iOS version out first instead of releasing both in parallel, for bug testing, improvements etc?


Overall, our focus right now is iOS, but we want to do Android at some point. Even though we used React Native, we also wrote a good amount of native Swift code under the hood to power native modules.


Ok, well good luck


We've added support for opus 4.5 to v0 and users are making some pretty impressive 1-shots:

https://x.com/mikegonz/status/1993045002306699704

https://x.com/MirAI_Newz/status/1993047036766396852

https://x.com/rauchg/status/1993054732781490412

It seems especially good at threejs / 3D websites. Gemini was similarly good at them (https://x.com/aymericrabot/status/1991613284106269192); maybe the model labs are focusing on this style of generation more now.


FYI your code examples were being rendered as a bunch of [Object object], then it fixed itself after a refresh

https://neutron-engine.vercel.app/#code-examples


Cheers, I'll see what might've caused that.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: