DecoPerson

Currently, if a government ordered a special virus with Ethnicity-based targeting, a 2-year timer, and castration-effects instead deadly-effects — it wouldn’t be possible. Human engineers would push back or sabotage the effort out of moral duty. Even if they cooperated, it’s too advanced for a team of humans to actually design.

I believe that in a few years, an AI could build such a thing. Maybe it’s told to, or maybe it decides itself to do it — it doesn’t matter. The capability will be there, and it can use the existing tooling at research facilities to fabricate such a thing.

That’s one example of something that was never possible before but will be possible at a certain point of AI development (which we will arrive at soon). There are many other examples.

- 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

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.

The platforms provide more than enough capability to build basic WebView apps with minimal effort, and usually the DX is good.

It’s called a “WebView app” and you can get a really good experience on all platforms using them. Just:

- don’t make any crazy decisions on your fundamental UI components, like breadcrumbs, select dropdowns, etc

- add a few platform-specific specialisations to those same components, to make them feel a bit more familiar, such as button styling, or using a self-simplifying back-stack on Android

- test to make sure your webview matches the native browser’s behaviour where it matters. For example, sliding up the view when the keyboard is opened on mobile, navigating back & forth with edge-swipes on iOS, etc

I also went the extra step and got service workers working, for a basic offline experience, and added a native auto network diagnostic tool that runs on app startup and checks “Can reach local network” “Can reach internet (1.1.1.1)” “Can resolve our app’s domain” etc etc, so users can share where it failed to get quicker support. But this is an app for small-to-medium businesses, not consumer-facing, and the HTML5 part is served from the server and cached. I haven’t thought much about what you might need to do additionally for a consumer app, or a local-first app.

Having used WebSockets a lot, I’ve realised that it’s not the simple fact that WebSockets are duplex or that it’s more efficient than using HTTP long-polling or SSEs or something else… No, the real benefit is that once you have a “socket” object in your hands, and this object lives beyond the normal “request->response” lifecycle, you realise that your users DESERVE a persistent presence on your server.

You start letting your route handlers run longer, so that you can send the result of an action, rather than telling the user to “refresh the page” with a 5-second refresh timer.

You start connecting events/pubsub messages to your users and forwarding relevant updates over the socket you already hold. (Trying to build a delta update system for polling is complicated enough that the developers of most bespoke business software I’ve seen do not go to the effort of building such things… But with WebSockets it’s easy, as you just subscribe before starting the initial DB query and send all broadcasted updates events for your set of objects on the fly.)

You start wanting to output the progress of a route handler to the user as it happens (“Fetching payroll details…”, “Fetching timesheets…”, “Correlating timesheets and clock in/out data…”, “Making payments…”).

Suddenly, as a developer, you can get live debug log output IN THE UI as it happens. This is amazing.

AND THEN YOU WANT TO CANCEL SOMETHING because you realise you accidentally put in the actual payroll system API key. And that gets you thinking… can I add a cancel button in the UI?

Yes, you can! Just make a ‘ctx.progress()’ method. When called, if the user has cancelled the current RPC, then throw a RPCCancelled error that’s caught by the route handling system. There’s an optional first argument for a progress message to the end user. Maybe add a “no-cancel” flag too for critical sections.

And then you think about live collaboration for a bit… that’s a fun rabbit hole to dive down. I usually just do “this is locked for editing” or check the per-document incrementing version number and say “someone else edited this before you started editing, your changes will be lost — please reload”. Figma cracked live collaboration, but it was very difficult based on what they’ve shared on their blog.

And then… one day… the big one hits… where you have a multistep process and you want Y/N confirmation from the user or some other kind of selection. The sockets are duplex! You can send a message BACK to the RPC client, and have it handled by the initiating code! You just need to make it so devs can add event listeners on the RPC call handle on the client! Then, your server-side route handler can just “await” a response! No need to break up the handler into multiple functions. No need to pack state into the DB for resumability. Just await (and make sure the Promise is rejected if the RPC is cancelled).

If you have a very complex UI page with live-updating pieces, and you want parts of it to be filterable or searchable… This is when you add “nested RPCs”. And if the parent RPC is cancelled (because the user closes that tab, or navigates away, or such) then that RPC and all of its children RPCs are cancelled. The server-side route handler is a function closure, that holds a bunch of state that can be used by any of the sub-RPC handlers (they can be added with ‘ctx.addSubMethod’ or such).

The end result is: while building out any feature of any “non-web-scale” app, you can easily add levels of polish that are simply too annoying to obtain when stuck in a REST point of view. Sure, it’s possible to do the same thing there, but you’ll get frustrated (and so development of such features will not be prioritised). Also, perf-wise, REST is good for “web scale” / high-user-counts, but you will hit weird latency issues if you try to use for live, duplex comms.

WebSockets (and soon HTTP3 transport API) are game-changing. I highly recommend trying some of these things.

    How to Write in Cuneiform, the Oldest Known Writing System in the World

You can argue that, "well, obviously!" but correctness and exactness are what makes science, history, journalism, etc good, and allowing incorrectness like this is a step backwards.

I read a history book when I was a teenager (can't remember which one, unfortunately), and the author wrote a preface that said something along the lines of "Everything in this book is based on the published information I could discover during my research period of April to September 1999. I have chosen to write in absolutes--stating many things as certain and clear--but in reality there is still much we do not know about this time period. No history author should say their writing is fact and any good historian will make it clear that their work is composed of assumptions layered on assumptions. Please read these works with this in mind."

If you don't have a preface like that, you should add "known" to your title/sentence! I will argue with someone all day over this! I will die on this hill!

I've found some of them to be surprisingly good. I keep a list of them, as I have future project ideas that might need a good one, and each has its own merits.

I'm yet to find one that does good spoken informal Chinese. I'd appreciate if anyone can suggest one!