I'm sure they're roughly equivalent. Parent is probably actually asking: is there native support for managing multiple checkouts/branches for parallel work (and I would add: with lifecycle hooks for create/teardown so I can have dedicated test databases etc).
Ignoring the fashion context (to which, no comment), totally agree.
I have an Apple Watch SE that I got the battery refurbed after 5 years, 95% of my use is a quick check on my next calendar, setting timers, managing the morning alarm, and tracking medication and exercise. Oh, and constantly putting it into power save mode after I take it off the charger.
It's not a cellular model, so the other 5% is basically letting me know my phone has something to tell me. I have in the past tried to put games on it, but purely as a novelty.
My understanding is (1) yes. (2) maybe, maybe no, depends on if they're looking up people tagging you in threads? If there's signs you're scrubbing yourself out of politically controversial threads that might become problematic. (4) yes, yes, yes. (5) yes.
Oh, yeah 100% I'm putting up scripts for them, the conductor hook is "run the one script" for setup/teardown.
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.
I'm buying into this workflow more the more I use it, but the real gamechanger is (a) parallel threads in worktrees, with (b) enough lifecycle hooks to treat them similarly to spinning up a VM.
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.
I've been extremely happy with Arq https://www.arqbackup.com/ for several years as a quiet backup solution, bring your own storage. I've done a few small restores and it's been just fine, and it automatically thins your backups to constrain storage costs.
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.
Maybe I should've worded differently for clarity, the game doesn't go forever:
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.
> with most EVs, you can drive 500 miles with one 30 minute charge
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.
I see this as not just internal API/architecture/code documentation, but product documentation too. We maintain internal docs about how our product is used for our support, implementation, and sales teams to reference.
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.
The US decided (and Canada followed) that daylight time was more correct for the larger portion of the year, presumably it's easier to transition the remaining 4mo to daylight than it is to move 8mo to standard.
But also, all the opinion polling (business and individual) was like over 90% in favour of year-round daylight time, so here we are.
The difference is how they're consumed you don't sit down on Netflix and say "put some scifi on shuffle for 8h", you sit down and choose a show.
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.