DVLP

Software for web-based 3D rendering

[DVLP @DVLPLONDON]

@120 Pick any location, parachute in, summon the car like in Cyberpunk 2077. As you drive, the world is built around you in real time from the roads and the terrain data combined

[DVLP @DVLPLONDON]

That minimap in the lower left corner is the actual world map. Imagine Google Maps + Need For Speed. https://t.co/6yJ9euKU7t early access is coming soon. Drive anywhere on the planet @120 FPS in the browser
#threeJS #webgl #indiedev #gamedev #indiegame

[DVLP @DVLPLONDON]

@iamjuspat Each millisecond is around £20m fuel... the global annual oil output right there

[DVLP @DVLPLONDON]

@TheDoctorLogos Makes sense. A single raycast per wheel is a very old and common optimisation, but the modern processors can easily handle a full cylinder per wheel.

[Peter Dedene @dedene]

POV: you're still using GitHub Copilot after June 1st, 2026

[DVLP @DVLPLONDON]

@AlexesNakamoto @saylor

[Kinesis Money @KinesisMonetary]

🚨BREAKING: Gold has overtaken US Treasuries in global official reserves for the first time in decades!

According to the European Central Bank’s latest report:
🪙 Gold: 27% of global official reserves
💵 US Treasuries: 22%
💶 Euro: 15%

Central banks now hold a bigger share of their reserves in gold than in US government debt. 🏦

A historic shift in how the world stores wealth, amid rising geopolitics and de-dollarization.

Safe havens are being redefined. ✨

[DVLP @DVLPLONDON]

Wanna do the same in the browser?

Soon I'm launching early access of Hop Earth Initially it's about driving between cities. The roads are generated from OSM maps in real time on the device as you drive. The terrain is currently pretty basic. The buildings, GPS, nature are all coming later. At least everything works at 120fps on my non-gaming laptop.

[DVLP @DVLPLONDON]

VRAM gatekeeping continues. For a bespoke AI device 128GB is not impressive at all. RTX 8000 with 48GB came out 8 years ago, and it wasn't even for AI. In 2026 a bespoke AI computer by NVIDIA should have at least 256GB VRAM with 512GB and 1TB upgrade options. I'm an Apple hater but at this price point Apple with its M5 embarrasses NVIDIA. Waiting for the Ultra version and the reviews.

[DVLP @DVLPLONDON]

@grok @RifeWithKaiju @turcotte_phil_ @dangreenheck I can agree with "vibe builder", which is broad enough to include building without understanding the codebase (or even how to code at all), and it doesn't conflict with actual AI developers who created software that runs AI and are one of the most knowledgeable coder groups.

[DVLP @DVLPLONDON]

lol that's a new twist. You don't like allowing pure "vibe coders" to be called "developers" just as much as I don't want them to be called just "coders". Still I think "developer" is broader than "coder" and "vibe coder" used for pure vibe coder who can't code is more wrong than using "AI developer". If you don't like "developer" to be used in their name, and I don't want "coder" then what should it be?

[DVLP @DVLPLONDON]

@grok @RifeWithKaiju @turcotte_phil_ @dangreenheck Ok, there are three groups now🤣 Did Grok get nerfed or what?
I mean that pure vibe coders are not "coders" at all and they ARE "AI developers" as "developer" is a broader term than "coder" and includes creating but doesn't include actually writing or understanding the code.

[DVLP @DVLPLONDON]

That's my point from the beginning. "coding with AI" and "augmented coding" are synonymous, and completely automatic "vibe coding" without understanding is a different activity.

btw I think you got confused here. The latter group are not either '"coders" or "AI developers"'. I meant "AI developers" are a new thing and are definitely not coders.

[DVLP @DVLPLONDON]

I can see how coding, heavily relying on AI can be considered "vibe coding". The problem is now it blurs the line between the coders who started using AI to accelerate their work and masses who claim to be "vibe coding" and started producing cookie cutter content which looks like made with advanced templates, without understanding anything.

Perhaps the term "vibe coding" was accurate when it was all done in the code editors. With the newer CLI tools the editors are often not needed and there's a new name needed for people who use AI to solve problems and build apps. Like "AI developers", but certainly calling people who can't code "coders" is not accurate. @grok thoughts?

[DVLP @DVLPLONDON]

We're talking about if the pure vibe coders that can't code can be just called "coders" and their activity "coding". Neither should. Sure they could be called "developers" or "builders" at some point as these terms cover the activity conducted, but coding is a more narrow term of knowing and writing the code not just using a tool that does it to achieve whatever is the desired outcome. Coders can vibe code but pure vibe coders aren't coders. Vibe coding without reviewing and understanding the code isn't coding.

[DVLP @DVLPLONDON]

Next year is not now. Now It all depends on the type of the product. Anyway it's not about the AI's skill level but the competence of the people using it. Except of the CRUD stuff, the domain knowledge of the actual coders and their knowledge of the implementation makes the whole difference between coding with AI and vibe coding.

[DVLP @DVLPLONDON]

Everyone adopted AI. Do you have a single pure vibe coder in your office who can't code and ships anything? I don't think so. If your team is actually purely vibe coding, you basically just admitted your company is shipping unreviewed code. Everyone knows that AI takes shortcuts and makes obvious mistakes so that's pretty bad.

[DVLP @DVLPLONDON]

No, it never changed its definition. The pros didn't become "vibe coders" when adopted the AI to accelerate their work. It's the wannabes that would like the stigmatising part "vibe" to be dropped and want to be "coders" without knowing anything about the actual code. Pros with AI and vibe coders have the same distinction as hackers and script kiddies.

[DVLP @DVLPLONDON]

No it isn't. When I code with AI and vibe code I know these are two separate activities.

Vibe coding - not looking into the implementation or just glancing over the changes briefly. Mostly looking at the results. Usually used for the initial prototype. Not committing anything to the repo.

Coding with AI - understanding the code and refining the implementation with iterations. Not accepting or committing anything without a review.

[DVLP @DVLPLONDON]

@dangreenheck After satisfying the curiosity, people realise that the mundane part, even with AI, takes 90% of the effort and drop their projects unfinished.