- Do not make tapping the text act as selection. I was trying to scroll and accidentally advanced twice.

- Add back and/or reset test buttons.

- Give immediate feedback, rather than asking me to read 10 x 3 long texts.

Very frustrating. I was very interested in the results but this combination of problems made this site worthless.

I hope my prediction is wrong.

He says it “feels like 007 stuff.” “AI will never trick me!”

We also have a duress code word, listed in the notes of that KeePass(ium) entry with the TOTP.

Surely this was considered earlier within Apple. I wonder what changed that they decided to do this now.

I’ve been trying to find a good way to let my Dad keep tweaking the new version but haven’t so far. For now he continues to work (using CD) on the jsx prototype. I can do another export later and CC could use git diff to see what changed and realise those same changes in the “real” version. But there has to be a better way.

My 76yo Dad just used Claude Design to make a simple commercial tenancy/lease management CRUD app. We handed what he built to Claude Code to implement within my existing business tech stack. It perfectly followed my coding & testing playbooks (basically a multi-file CLAUDE.md with prompt & command hooks to evaluate conformance). It works… exactly as my Dad imagined.

Now, mind you, my Dad had some outdated UI expectations (he asked Claude Design to style use a Windows 98 aesthetic!), but my point is: we just built a fully-functional, deeply tested, domain-expert-designed app, in less than a day.

I tried this on a local project. It looks very jank and the math falls apart quickly. Unfortunately, using a fixed axis-aligned grid for rotating reference frames is not practical.

One to thing I wanted to try but didn’t, was to use dynamic axes. So once an entity is created (that is, a group of voxels not attached to the world grid), it gets its own grid that can rotate relative to the world grid. The challenge would be collision detection between two unaligned grids of voxels. Converting the group to a mesh, like Teardown does, would probably be the easiest and most effective way, unless you want to invent some new game-physics math!

Fusion 360’s heuristics are so good that I rarely run into these problems. When I do, it’s usually because it was a drastic change to a previous feature in the timeline and I’m expecting to encounter issues because it’s a really fundamental change.

Just my whacky conspiracy theory of the day!

Maybe that's why they behave differently?

As you’re a solo dev, one of your most important resources is your mental capacity. Native platforms & their dev stacks are a world of their own.

Going with WebView allows you to spend your time on other things that matter more. It also helps you prototype quickly and get a feel for what works.

Later, after you have a better, more solid idea of what your game is, if performance is an issue, then you can convert parts of it (or all of it) to native.

(By the time your game is done, I suspect the mobile app dev landscape is going to be quite different than what it is now.)

(I'm not associated with Zed, just a happy user looking to share the goodness.)

We can speculate all day, but we should try to analyse these sorts of things from a learning perspective. What can we learn from Russia, China, etc? How are they better?

https://faiface.github.io/par-lang/introduction.html

Comments URL: https://news.ycombinator.com/item?id=45993087

Points: 2

# Comments: 1

I just open a Claude Code Thread, tell it what I want, bypass permissions (my remote is a container), and let it work. And it works wonderfully!

I guess the “integrated” part of IDE is pretty important.

Native experience for users, where the app appears in their app drawer/library. The app doesn’t disappear randomly like shortcuts do on iOS (maybe this is fixed now?).

Better DX for certain features, like notifications, storage, control of caching, local network device access, etc.