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

There's some CSS properties specifically for doing 3D, yeah. You use perspective and perspective-origin to create the view frustum, and then CSS transforms to place your elements in 3D space.

Query DSLs are designed to simplify query planning by intentionally avoiding certain language features. You have many different choices on how to execute a query - in SQL for example, there's table scans, index seeks/scans, joins, etc. and you can execute them in different order. By being able to analyze the query upfront you can estimate the relative costs of different plans and choose the best one. Less powerful languages result in more predictable estimates because they're simpler to analyze.

Mr. Doob has been doing experiments like this for at least a decade, glad to see that he's still at it.

He's the creator of three.js, and it looks like this uses that for rendering instead of being a straight port.


He also remade quake a couple weeks ago (on three.js as well I believe).

https://mrdoob.com/#/160/threejs_quake

(It's also his homepage now, but I included the full link for posterity.)

--

Edit: How do you actually play? I keep getting trapped in the Shareware Dimension!


I think you can avoid the pain by thoughtfully designing it to avoid lock-in. You want it so that if needed, a dev can vibe-code a migration tool to the equivalent SaaS offering. AI lowers the barrier for creating these in-house replacements, but it also lowers the barrier for scrapping them too.


The thing about lower barriers is that it makes it easier for e.g. Salesforce to raise the level of expectations. And that's the moving target. New employees will come from elsewhere and wonder how a company is operating using tools from 2020 when X, Y, Z are becoming industry standard.

The key here is that the moving target will _never_ be "what can 1-2 people vibe code without any expectation of being the best at what it does?"

(Also: training people on bespoke tools takes much longer than training on configurations of standard tools. Imagine if you had to learn a new source control system at every job, like in the '80s.)


Nice find! That looks like Cooper Black, which the article cites as inspiration.


In the US, there are several thousands of banks and credit unions, and the smaller ones use a patchwork of different vendor software. They likely don't have to write COBOL directly, but some of those components are still running it.

From the vendor's perspective, it doesn't make sense to do a complete rewrite and risk creating hairy financial issues for potentially hundreds of clients.


You're probably thinking of the Himba tribe color experiment - which as it turns out, was mostly fabricated by a BBC documentary:

https://languagelog.ldc.upenn.edu/nll/?p=17970


Yes, I think this was it! Thanks for sharing the link. I had no idea that part was fabricated.


Cool site! Reminds me of tsubuyaki processing, which is a similar "code golf that fits in a xeet" type of challenge.

https://xcancel.com/search?q=%23%E3%81%A4%E3%81%B6%E3%82%84%...


Well technically you can still use Flash via Ruffle, a WebAssembly-based emulator:

https://ruffle.rs/

Sites like Kongregate amd albinoblacksheep are using it to revive their old catalog.


The toy with the most longevity from my childhood were those cardboard bricks. Could be used for anything from forts, towers, hamster mazes, throwable weapons...

Not the quickest toy to clean up, but still fun since it's a building activity of its own, stacking them against a wall or something.


I had the same experience, loved my cardboard bricks. My kid never connected with them the same though even though my kid is big on building toys. Now they mostly just take up space, should probably give them away.


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

Search: