I’m imagining a scenario where you’re working on a feature that changes the DB state (e.x. introduces a new DB migration that changes some columns) and the bug is on an unrelated part of the code from your feature. In this hypothetical, going back to the state of the upstream branch would make your local environment non functional, and the bug is on an unrelated part of the code. Fairly specific scenario but hey, you can worktree for that. It’s not particularly thorough, though.

Or a gastroenterologist instead of a neurosurgeon 🤔

OP, I dunno if you’ve seen it yet but you’re featured on their testimonials list!

Shit like this just contributes to this overall messy feeling I have on Windows. For many reasons I can’t get off the OS completely, but man every time I use Linux (for servers/my personal laptop/etc.) it just feels so clean in comparison.

Yeah I remember the first time I tried a 1080p 15" display. Even that I had to look at really hard, can’t imagine a 4k version that actually uses 4k resolution for regular computing.

But then you’d be sacrificing all that comes with React. Unless you mean having the page rendered by another framework and having React components loaded later, but I’d think that would be less maintainable than if the whole thing was just in React.

There’s versions of VSCode you can run as a web app, including support for the terminal. You just need to roll your own build/run stuff.

That’s pretty cool, although personally I’m not a fan of the things this solves. Comments after statements offer no benefit over simply commenting on a line before or after, except maybe keeping the line count the same. And defining your method like:

func methodName( int x

I prefer to write as:

func methodName(
    int x

Seems like the project could use a VSCode version, too.