This would be amazing if obsidian mobile did not take 10 seconds to start or even recover from being in the background and lose scroll position every time. For the desktop I would be absolutely happy with all todos in a simple markdown file. There can also be any number of UIs on top of markdown that people use over the years and grow out of but as long as the base system is markdown files you get the best of both worlds. I would never consider using an app for notes or todos that does not persist like that and no: ability export is not the same as native persistence in a human readable format. (Discovered the heard way multiple times when apps advertising with export failed or just lied.)

I think people are now ready for php. I bet it will be reinvented on top of nodejs.

This is the same guy, right? Who burned out so totally he ended up working in an Amazon fulfillment center for six weeks?

https://www.jasonshen.com/169/

Great sales pitch, but this is a key excerpt:

> What was the catch? It seemed most municipalities required you to renovate the house within a couple of years of its purchase, and due to high levels of interest, the houses often went to auction, ultimately selling for much more than a single euro.

You got downvoted for the snark, but damned if it ain't a reasonable opinion.

If you read the seminal "Design of Everyday Things" by Norman Rockwell you'll come away annoyed at half the physical _doors_ you walk through... here in 2025.

I've been pushing these terms to help us talk about and design better interfaces at work...

Static Interfaces - Your supermarket's pretty much a static interface. The frame of whatever website you're looking at. These are static. They've very powerful and were pretty much all you had before digital interfaces became ubiquitous. There's an initial learning curve where you figure out navigation, and then for the most part it's fairly smooth sailing from there provided the controls are exposed well.

Adaptive Interfaces - These interfaces attempt to "adapt" to your needs. Google is probably one of the most successful adaptive interfaces out there. A query for "Shoes" will show a series of shopping results, while a query for "Chinese food" will show a map of the restaurants nearby. The interface adapts to you.

I call this narrow adaptive because the query triggers how the UI adapts. I think "wide area" adaptive interfaces where the interface attempts to meet your needs before you've had a chance to interact with the static interface around it are tremendously difficult and can't think of examples of them being done well.

Adaptable Interfaces - This last interface bucket includes controls which allow a user to adapt the interface to their own needs. This may include dragging icons into a particular order, pinning certain view styles or filters, or customizing the look or behavior of the applications you're working with.

Finder, the iPhone's basic UI, terminal, basic music catalog management (e.g. iTunes)... these are interfaces which are created once with an initial curve of varying difficulty to learn and then live on for decades without much change.

Conclusion - The best interfaces combine an intuitive static frame, with queried adaptive elements, and adaptable features to efficiently meet the needs of a diverse group of user flows instead of attempting the one size fits all approach (which leaves 2/3rds of people annoyed).

I don't have a personal site yet. But when I do, I plan to make it with HTML+CSS+JS/JQ only

Maybe apache or nginx as webservers

host it on shared stuff or AWS free tier

I just need to figure out how to center a div, and then I'll be in the business.

Can still recover the gold from old parts though.

Quite fitting actually, alchemists scamming investors with needing a "starting" amount to get their reaction going