They (and Sask too) do swing on the higher end in GDP per capita, but it's not a 2:1 by any stretch.

Assuming they do ask in the first place.

The difference is removing friction, having a UI that shows me what's set up, that I don't need to hit the filesystem or git status to check in, that gives me _direct_ access to a shell/etc in that worktree path.

And then I guess setting up tasks for the cleanup part, but it'd be great to see that get automated too so I don't need to remember it.

Specifically for me that means that after I create a worktree I get some local config files copied over and Postgres duplicating my local dev and test databases so I can test in isolation, and then when I close out a worktree it deletes those databases.

The best at that that I've found is Conductor, but I can't use it at work because we only have Copilot and they're locked to a Claude/Codex backend. Arbor is close, but it's not under as active development and has a lot of rough edges. Opencode GUI has create hooks but not teardown.

If Zed can hook that up _and_ also keep its great editor roots, that'll definitely be a game changer.

Managing exclusions is something to keep vaguely on top of (I've accidentally had a few VM disk images get backed up when I don't need/want them) but the default exclusions are all very reasonable.

The player first revealing Checkmate ends the game. They win if their opponent's currently-chosen card is also a Checkmate, otherwise the opponent wins.

Both players choose a card. Players then in turns reveal their card, and if Check, make another choice. The player first revealing Checkmate wins if their opponent's currently-chosen card is also a Checkmate.

OK that roughly lines up - the Model Y doesn't quite get there (on expected range) and it's apparently 40% of the market, but it's also pretty close.

I'm just gonna call bullshit on that one. https://ev-database.org/cheatsheet/range-electric-car looks like it's got a bunch of recent vehicles, and pegs average range at 390km or 242mi. The _highest_ range there is 720km or 450mi, and a 300KW charge runs it 10-80% (+500km range, not miles) in a half hour.

If you _don't_ have the absolute best range + infrastructure to support the charge at that rate: I've got a 2020 Kia Soul w/ 64kWh battery and lines up with the 390km range rating. Did a road trip last year. My charger caps out at 73kW or so on a DC charge, and a charge at that rate (40%-80%) gave me ~150km in a half hour. 10-80% is ~220-250km and takes an hour.

Now, I did the road trip with two kids and a dog, so an hour's potty/walk break every 2-2.5h driving worked out for us, but I don't think that's entirely generalizable. I do also agree that unless we're road-tripping, it's a nonissue. We put a level 2 charger in the garage, and plug in overnight once or twice a week and no range stress at all.

Right now it's hosted externally (in our "blessed" knowledge base) but if it could be pulled into the repo, and we set an AI reviewer on every pull request to sanity check that if the changes we're doing have a material impact on the feature as described in those docs that it should be flagged (or changes proposed) that'd be a nice win for keeping them up-to-date, and it's easy enough to publish markdown as html or even script an update to the canonical site when we merge to main.

But also, all the opinion polling (business and individual) was like over 90% in favour of year-round daylight time, so here we are.

If you're the kind of person who would manually queue up 100% of your songs for the day then Spotify Generic songs aren't an issue. If you just hit a "2020s R&B" playlist and go that's where it feels more sketchy.

Especially anything that Mac Steam natively calls out lack of 32bit support has good support.

https://kenney.itch.io/kenney-game-assets

Presumably that hasn't changed much. If you want to do any large-scale edits of the UI you need to spin up a fork.

Lately on the podcast I only hear about Fizzy and one other unannounced SAAS that they're putting dev energy behind, nothing about other ONCE products.

I suspect that without a critical mass of usage driving word of mouth the long tail of sales was basically nil, and long-term even fairly small products weren't looking to recoup dev costs any time soon.