Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Creating a multiplayer game on v0 using Three.js and Liveblocks Models/textures/tracks/environments/physics, everything is being created by v0. The key part was asking v0 to create automation scripts to export logs/screenshots so it can iterate on its own.

15,090 görüntüleme • 4 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

For the past few weeks I’ve been teaching 50+ kids how to create their own games with AI. The results have been incredible 🤯 I started with my 5 y/o nephew because I was worried about him spending hours doomscrolling and consuming brainrot content. He built his first game using v0, though I had to walk him through each step. Watching kids interact with these tools taught me so much about how they think, where they get stuck, and what keeps them motivated. The moment that really struck me came right after he finished that first game. Every time I saw him afterward, he’d run up and ask, “Did you bring your laptop so I can keep playing?”. For him, “playing” meant creating. That kind of excitement is organic pull. Don’t get me wrong, I love v0 and Lovable. They’re insanely powerful. Their UIs just aren’t designed for kids, and that’s totally fine. Kids still need guidance, structure, and a bit of tutoring to turn ideas into something playable. I’m seeing tech leaders push in this direction too, and I think there’s a real opportunity here (Matias Woloski Thomas Wolf). Kids are the future, and I don’t want to live in a world where they spend precious time consuming instead of creating. That’s why I love tools like v0, Lovable, wabi , Cursor . They’re empowering more people to become creators. I want that same feeling for kids. What Guillermo is saying is real. Kids need to be AI-literate from the outset. It honestly makes me sad to think about my nephew growing up and falling behind on AI and everything happening around him because he’s stuck in Roblox or TikTok. That’s why I built Rabbit 🐰 for him. It started as a simple prototype, but somehow I ended up talking with 200+ parents and kids, tech leaders, investors, and people I never imagined meeting around the world. Rabbit now has 100+ people on the waitlist, and 10 kids are using it two to three times per week on average to create their own games 🫡 I’m not sure yet if this will become my full-time project, but I deeply care about it. If you’re building in this space, I’d love to connect and share ideas. And if you’re a parent interested in Rabbit, I’d love your feedback. Sharing a short video of kids using Rabbit below:

Fausto

44,125 görüntüleme • 6 ay önce

Dagknight technical progress As would be mentioned in a still unshared post by Michael Sutton, the dagknight effort is split into v0 devnet, v1 testnet and v2 mainnet candidate. I’ve been testing the current v0-based implementation in a small devnet with the help of some testers who run nodes and miners with me. The DK work can be thought of as split into two parts: (1) implementing the actual protocol and (2) wiring it up and using it. The testing and development over the last month has been focused on (2). Obviously, DK is a consensus change for selecting parents. What’s not so obvious is that such a change affects DAA, coinbase, IBD, pruning and a lot more. Each of these areas is very sensitive and requires proper understanding to wire correctly. An important consideration and difference from GD is that DK does not focus on maximizing a property like blue work. So to maintain topological properties of blue work, an independent (free) GD implementation is kept running specifically for maintaining blue work. This allows us to keep using the property for topology. Coloring and blue score use the megachain induced by DK. The wiring around DK as of this posting is in a working state, but still needs to be reviewed. Next efforts will be focused on protocol specific components, particularly Tie-Breaking and incremental UMC. Attached are some captures from the internal devnet. The dense DAG image is what happens when things related to DAA or other similar consensus parameter causes a node to insist on their POV. The video is a recent snippet of the KGI running on the devnet showing (perhaps not obviously) DK at work. The current “dagknight” branch is now posted on the main repo. A topic in the Public R&D has been opened for Dagknight development.

coderofstuff

52,857 görüntüleme • 4 ay önce