Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Built a v0 that implements precise collision detection with momentum for more accurate prefetching in Next.js v0 flawlessly bootstrapped the demo sections, intersection logic, debug panel…

Guillermo Rauch

316,978 subscribers

66,856 views • 1 year ago •via X (Twitter)

Science & Technology News & Politics Education

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

New Next.js e-commerce template by Blazity: ◆ Built with v0, shadcn UI, and Turborepo ◆ AI (search, image captioning) ◆ Enterprise-ready (A/B testing, scalable redirects, tests, etc) ◆ And more Try it out: `npm create commerce`

New Next.js e-commerce template by Blazity: ◆ Built with v0, shadcn UI, and Turborepo ◆ AI (search, image captioning) ◆ Enterprise-ready (A/B testing, scalable redirects, tests, etc) ◆ And more Try it out: `npm create commerce`

Delba

60,102 views • 2 years ago

drei/view got a massive update. mix webgl/three right into your html as views, as many as you want. they're self contained. events, controls, everything works. it's driven by a single canvas split into chunks via webgl_skissor. the demo is made with Next.js shadcn v0

drei/view got a massive update. mix webgl/three right into your html as views, as many as you want. they're self contained. events, controls, everything works. it's driven by a single canvas split into chunks via webgl_skissor. the demo is made with Next.js shadcn v0

☄︎

70,510 views • 2 years ago

I rebuilt one of the prototypes I made for Attio with v0. It's coming out surprisingly easily now that I know the technical solution. The code looks really clean and matches about 90% of how I originally built it.

I rebuilt one of the prototypes I made for Attio with v0. It's coming out surprisingly easily now that I know the technical solution. The code looks really clean and matches about 90% of how I originally built it.

Alex Krasikov

68,906 views • 1 year ago

Smart parking pipeline in real-time with Ultralytics YOLO26 🚗 🅿️ Over the weekend, I built a parking management system that monitors slot occupancy (occupied vs available). In busy parking areas where vehicles partially overlap slots or enter at angles, the system still maintains accurate detection and status updates in real time. More information 👇 #yolo26 #parkingproblem #machinelearning

Smart parking pipeline in real-time with Ultralytics YOLO26 🚗 🅿️ Over the weekend, I built a parking management system that monitors slot occupancy (occupied vs available). In busy parking areas where vehicles partially overlap slots or enter at angles, the system still maintains accurate detection and status updates in real time. More information 👇 #yolo26 #parkingproblem #machinelearning

Muhammad Rizwan Munawar

37,684 views • 3 months ago

I don't know what a vestaboard is here's a component that flips characters - Pass in an array of messages / a single message to display - Import via shadcn CLI or Open in v0 - Light and dark mode - Mobile responsive Built with Claude Opus 4.6 High + Composer 2 in around an hour, 40 minutes out of which were spent on detailing of individual box and their colors

I don't know what a vestaboard is here's a component that flips characters - Pass in an array of messages / a single message to display - Import via shadcn CLI or Open in v0 - Light and dark mode - Mobile responsive Built with Claude Opus 4.6 High + Composer 2 in around an hour, 40 minutes out of which were spent on detailing of individual box and their colors

Manu Arora

32,300 views • 4 months ago

I’ve built a background daemon that connects to Linear for one of my enterprise clients (multi-billion company). It runs autonomous AI workflows: – Creates PRDs from tickets – Waits for human review – Implements, verifies, and opens PRs automatically Built with LangGraph for orchestration, Codex + Claude for deep code understanding, direct LLM's API calls (via OpenRouter) for more deterministic tasks. It’s pretty cool watching the whole flow execute live in the console ⚡️

I’ve built a background daemon that connects to Linear for one of my enterprise clients (multi-billion company). It runs autonomous AI workflows: – Creates PRDs from tickets – Waits for human review – Implements, verifies, and opens PRs automatically Built with LangGraph for orchestration, Codex + Claude for deep code understanding, direct LLM's API calls (via OpenRouter) for more deterministic tasks. It’s pretty cool watching the whole flow execute live in the console ⚡️

Krzysztof Zabłocki

17,019 views • 9 months ago

Our demo is now LIVE, just in time for #SteamNextFest and beyond! Get a sneak peak at one of our favorite sections yet, get a feel for combat, platforming, and much more!! What kind of terrors await you in the depths? There's only one way to find out:

Our demo is now LIVE, just in time for #SteamNextFest and beyond! Get a sneak peak at one of our favorite sections yet, get a feel for combat, platforming, and much more!! What kind of terrors await you in the depths? There's only one way to find out:

Venture to the Vile, OUT NOW on Steam And PS!

17,947 views • 2 years ago

A simplified summary of my simulations of how drone detector antenna placement affects signal reception, expressed as a conditional drone detection range for different frequencies - obtained roughly by normalizing the square root of total gain to a typical drone detection range. Red line - detection distance for antenna on the roof, blue line - for antenna under the windshield. Considering that the main sector from which drones can approach the vehicle is elevation from 0 to 30 degrees, and also that in reality the glass will attenuate the signal more strongly than in my simulations - mounting the drone detector antennas inside the vehicle significantly reduces its practical drone detection range, especially in the rear hemisphere.

A simplified summary of my simulations of how drone detector antenna placement affects signal reception, expressed as a conditional drone detection range for different frequencies - obtained roughly by normalizing the square root of total gain to a typical drone detection range. Red line - detection distance for antenna on the roof, blue line - for antenna under the windshield. Considering that the main sector from which drones can approach the vehicle is elevation from 0 to 30 degrees, and also that in reality the glass will attenuate the signal more strongly than in my simulations - mounting the drone detector antennas inside the vehicle significantly reduces its practical drone detection range, especially in the rear hemisphere.

Alex

72,770 views • 2 months ago

Huge upgrade to loading speeds coming soon, especially with DLL-heavy codebases like UE! The primary reason PDB -> RDI conversion (or PDB parsing in debuggers more generally) is a big bottleneck in startup time is because they must be converted/parsed/loaded _serially_. This may seem surprising, since intuitively it'd seem like they can be converted/parsed/loaded/etc. in parallel. This is not true in the general case due to breakpoints, and how they relate to an API like `LoadLibrary`, and how it translates into debug events. When a debuggee runs `LoadLibrary`, the debugger will receive a debug event informing the debugger that the associated module was loaded. Any time a debug event is sent to the debugger, the debuggee stops running entirely. This is so that the debugger can make decisions about how the debuggee should proceed. For example, if I have a breakpoint on `foo.c:123`, that file name and line number can only be correctly interpreted (meaning resolved into code addresses) using debug information. The debugger only knows about that debug information from the PDB - without it, that file/line combo is meaningless. But importantly, the debugger cannot *resume* the debuggee until it has resolved that breakpoint - otherwise the debuggee may execute code which *would've* hit the breakpoint, *if* it were resolved in time. So, the debugger needs to ensure that all breakpoints are fully resolved before resuming. This is a correctness detail that everyone has to pay for, basically because `LoadLibrary`s are received one-at-a-time. Obviously, if it were instead an API like `LoadLibraries`, then the debugger could prepare all of the debug info in one batch before resuming - but it doesn't know what that batch would be, given just an initial `LoadLibrary`. This is unfortunate, because *generally* you are not debugging the code loading a bunch of DLLs, but the debugger can't really know that. (It is probably a good idea to provide a `raddbg_load_libraries` API at some point, so that we can resolve this issue on the debuggee side). In any case, RADDBG now resolves breakpoints much more quickly by avoiding 99% of debug info conversion work to do a common case of breakpoint resolution - you might call this "breakpoint disqualification". Basically, if a breakpoint is set, and we can quickly determine that that breakpoint's information (file location, expression, condition, etc.) *cannot apply* to some module's debug info - more quickly than doing a *full* PDB -> RDI conversion (which entails a full parse & a bunch of work) - then we can simplify the very common case in DLL-heavy cases: you put a breakpoint on `foo.c:123`, when 99% of the DLLs do not have any line info for that file, so the debugger can resume *knowing* that breakpoint will not resolve within that file. In this demo video, you can see I place a breakpoint that only resolves within the executable's debug info - it does not resolve within any of the 100 DLLs that are loaded serially. Within the `Modules` tab, you can see that as I run the target, most of the debug info is not loaded initially, even though the debuggee is running. That debug info is loading in parallel, as the debugger knows it does not need to wait for that debug info to be prepared for this breakpoint.

Huge upgrade to loading speeds coming soon, especially with DLL-heavy codebases like UE! The primary reason PDB -> RDI conversion (or PDB parsing in debuggers more generally) is a big bottleneck in startup time is because they must be converted/parsed/loaded _serially_. This may seem surprising, since intuitively it'd seem like they can be converted/parsed/loaded/etc. in parallel. This is not true in the general case due to breakpoints, and how they relate to an API like `LoadLibrary`, and how it translates into debug events. When a debuggee runs `LoadLibrary`, the debugger will receive a debug event informing the debugger that the associated module was loaded. Any time a debug event is sent to the debugger, the debuggee stops running entirely. This is so that the debugger can make decisions about how the debuggee should proceed. For example, if I have a breakpoint on `foo.c:123`, that file name and line number can only be correctly interpreted (meaning resolved into code addresses) using debug information. The debugger only knows about that debug information from the PDB - without it, that file/line combo is meaningless. But importantly, the debugger cannot resume the debuggee until it has resolved that breakpoint - otherwise the debuggee may execute code which would've hit the breakpoint, if it were resolved in time. So, the debugger needs to ensure that all breakpoints are fully resolved before resuming. This is a correctness detail that everyone has to pay for, basically because `LoadLibrary`s are received one-at-a-time. Obviously, if it were instead an API like `LoadLibraries`, then the debugger could prepare all of the debug info in one batch before resuming - but it doesn't know what that batch would be, given just an initial `LoadLibrary`. This is unfortunate, because generally you are not debugging the code loading a bunch of DLLs, but the debugger can't really know that. (It is probably a good idea to provide a `raddbg_load_libraries` API at some point, so that we can resolve this issue on the debuggee side). In any case, RADDBG now resolves breakpoints much more quickly by avoiding 99% of debug info conversion work to do a common case of breakpoint resolution - you might call this "breakpoint disqualification". Basically, if a breakpoint is set, and we can quickly determine that that breakpoint's information (file location, expression, condition, etc.) cannot apply to some module's debug info - more quickly than doing a full PDB -> RDI conversion (which entails a full parse & a bunch of work) - then we can simplify the very common case in DLL-heavy cases: you put a breakpoint on `foo.c:123`, when 99% of the DLLs do not have any line info for that file, so the debugger can resume knowing that breakpoint will not resolve within that file. In this demo video, you can see I place a breakpoint that only resolves within the executable's debug info - it does not resolve within any of the 100 DLLs that are loaded serially. Within the `Modules` tab, you can see that as I run the target, most of the debug info is not loaded initially, even though the debuggee is running. That debug info is loading in parallel, as the debugger knows it does not need to wait for that debug info to be prepared for this breakpoint.

Ryan Fleury

17,527 views • 1 year ago

Train a TensorFlow object detection model – then deploy it on a robot 🤖 Iulia Feroli (Iulia Feroli) shows how to turn a notebook into a real-time object detection app. This tutorial works for any project – though we demonstrate the deployment on (and assisted by!) the #ReachyMini, an open-source robot from Pollen Robotics. Built with PyCharm + Claude Code. 👉 Watch it in action:

Train a TensorFlow object detection model – then deploy it on a robot 🤖 Iulia Feroli (Iulia Feroli) shows how to turn a notebook into a real-time object detection app. This tutorial works for any project – though we demonstrate the deployment on (and assisted by!) the #ReachyMini, an open-source robot from Pollen Robotics. Built with PyCharm + Claude Code. 👉 Watch it in action:

PyCharm, a JetBrains IDE

34,908 views • 2 months ago

This is a mobile app for fitness. I built it with plain text + AI in 20 mins. You can describe a product... and AI builds the full app, UI backend logic auth with insane speed & precision. Real examples + the workflow: 👇 (the 𝕏 clone feels illegal)

This is a mobile app for fitness. I built it with plain text + AI in 20 mins. You can describe a product... and AI builds the full app, UI backend logic auth with insane speed & precision. Real examples + the workflow: 👇 (the 𝕏 clone feels illegal)

EyeingAI

64,849 views • 1 year ago

Felipe Chavez is doing a great job today with a goal & assist in the 2nd half. Collecting positive momentum & arguments for him to be included more often to the matchday squad in the near-by future.

Felipe Chavez is doing a great job today with a goal & assist in the 2nd half. Collecting positive momentum & arguments for him to be included more often to the matchday squad in the near-by future.

Complaxes

29,678 views • 6 months ago

I built a tool that runs autoresearch 24/7 in the cloud. It can scale to thousands+ of parallel experiments. Uses Modal (for GPUs) and Cloudflare Workers. Wraps coding tools Codex/Claude. Here's a quick demo ▶

I built a tool that runs autoresearch 24/7 in the cloud. It can scale to thousands+ of parallel experiments. Uses Modal (for GPUs) and Cloudflare Workers. Wraps coding tools Codex/Claude. Here's a quick demo ▶

david

34,349 views • 4 months ago

A tragic end for talented footballer Emmanuel , who reportedly lost his life after a collision on the field with the goalkeeper during play, a heartbreaking moment that has left fans and the football community in shock and mourning.

A tragic end for talented footballer Emmanuel , who reportedly lost his life after a collision on the field with the goalkeeper during play, a heartbreaking moment that has left fans and the football community in shock and mourning.

CDR AFRICA

249,974 views • 1 month ago

Built with C and raylib, 100k enemies + 5k bullets, its not just enemy-bullet collision, theres also some enemy-enemy separation that happens, it uses a spatial grid internally, i havent made all the optimizations yet, not even render culling, i think i can push it more

Built with C and raylib, 100k enemies + 5k bullets, its not just enemy-bullet collision, theres also some enemy-enemy separation that happens, it uses a spatial grid internally, i havent made all the optimizations yet, not even render culling, i think i can push it more

Bones

252,978 views • 10 months ago

Nothing much - but for the sake of transparency and developing this game for, and with, you - we figured we wanted to start sharing more work in progress. Here is a look at the weapon collision system. We intend to provide you with much more behind-the-scenes footage and other updates in the near future. #gamedev #indiedev #unrealengine #ue5 #multiplayer #medieval #locomotion

Nothing much - but for the sake of transparency and developing this game for, and with, you - we figured we wanted to start sharing more work in progress. Here is a look at the weapon collision system. We intend to provide you with much more behind-the-scenes footage and other updates in the near future. #gamedev #indiedev #unrealengine #ue5 #multiplayer #medieval #locomotion

Blight: Survival

1,470,374 views • 3 years ago

Shared by Jo Murayama: "VFX work for Caliwater & Demi Lovato commercial 🌊 I handled the slowmo liquid CG and composited additional droplets rolling down her cheek. Simulated liquids in #LiquiGen, textured/lit/rendered in Blender, comped in After Effects. Shoutout to JangaFX Software for #LiquiGen, a powerful real time simulation software that merges physically accurate liquid simulations and precise creative control."

Shared by Jo Murayama: "VFX work for Caliwater & Demi Lovato commercial 🌊 I handled the slowmo liquid CG and composited additional droplets rolling down her cheek. Simulated liquids in #LiquiGen, textured/lit/rendered in Blender, comped in After Effects. Shoutout to JangaFX Software for #LiquiGen, a powerful real time simulation software that merges physically accurate liquid simulations and precise creative control."

JangaFX Software

26,547 views • 4 months ago