I use Soulver with a file for each month’s expenses as well as a file for overall assets and liabilities. If you already have that app, it’s a great solution. It supports (global) variables and has natural language support.

https://soulver.app/

It’s not plain text, but it feels like plain text.

The wording on the site/blog was confusing. The homepage says "Download Beta" and the blog says "purchase". Sure enough, when you click "Download Beta" you're asked to pay $10.

I've updated the button to reflect reality.

Yeah, I’m not gonna go back on a desktop later.

Elly De La Cruz mashed two 400+ plus bombs to dead center with a torpedo bat today. Whatever helps the Reds hit homers I’m fine with.

I threw away all my personal productivity crap a couple years ago and still get the same amount of stuff done. I just converted the fiddling time into free time.

Would you say fiddling time was in some way pleasing for you? Maybe it was free time all along and still is for people who like that?

> The core issue, however, is the inability to participate in the actual craft. Design decisions are buried in React components with cryptic expressions like flex items-center shadow-lg p-6 hover:bg-gray-50 dark:bg-gray-800 py-[calc(theme(spacing[2.5])-1px)]. This might make sense for JavaScript engineers, but it's an insult to systematic design.

This is Tailwind nonsense—not JavaScript.

Agreed. Definitely feels like a workplace-only project.

Is it any worse than Singles Day?

It’s a lot bigger than Singles Day. In Germany if you work in e-commerce it’s the busiest time of the year.

I’m holding out for the one written for immortals.

I am not waiting for Janet for Ethereals. Once it ships, it will always have been available.

Meanwhile I'm waiting on "Janet for Normies" for myself

Ooooh, is this the start of a series - who's going to do those two, and then "Janet for Aliens", "Janet for the Rest of Us", "Janet for Dummies", and so on. The titles write themselves!

Preorder now, delivery in 10,000 years.

If you want to maintain state across navigations and share that state with a server it’s the best we’ve got.

Server can store session state

You just described how the whole web operates. It works just fine.

Even if you want client side, we have better ways now than cookies.

We do, but only cookies are universally available. Plenty of unusual user-agents in the world, or people like me that browse with JS off by default.

I add some products in phone. Then I login to desktop later for modification and order. Cart is empty. That's engineering smell. A really bad one.

Thats nothing more than UX/UI.

> In computer programming, a code smell is any characteristic in the source code of a program that possibly indicates a deeper problem. Determining what is and is not a code smell is subjective, and varies by language, developer, and development methodology.

- https://en.wikipedia.org/wiki/Code_smell

Wait, you can't shard on session ID?

And this is an ephemeral key-value store here, which is basically a best-case scenario from a performance standpoint. It's basically the last thing you're going to need to think about sharding, which is why session stores traditionally cohabitate(d) with web servers.

No, session storage doesn't get expensive fast. It's extraordinarily cheap unless you screw up the configuration very badly indeed (Apparently PHP still defaults to writing session data to disk?!)