doritosfan84

Healthcare is a hellscape and the companies that run it in the us have no incentive to improve the experience for beneficiaries right now.

I was on Obsidian for a while, moved away to try Supernotes and other competitors, and now I'm in the process of moving back to Obsidian.

Has everything you want I think with plugins to do a ton more while still essentially being just Markdown.

My use cases are trying to find the one test that failed out of my suite and finding a specific log print when my app is running. Yes, there are other ways to do both of these. Having scrollback search in the terminal is a very convenient option though.

I think most people that want this feature want to be able to search through terminal output, not the commands they've previously used.

A Republican promoted and implemented No Child Left Behind though? Maybe I’m misunderstanding your point.

I don't see the correlation. Jujutsu has workspaces as the match to git's worktrees too because their worktrees are a different thing from what I'm talking about. Switching worktrees and making commits is way more work than just making commits.

IME, the benefit is ease of branching paths. For example, if I'm working on a feature I can do something like this:

- Put tests in one commit - Tell Claude to come up with several approaches where I'm not exactly sure what the best might be - Put approach 1 into a commit, 2 into a separate one, etc. These approach commits all live side by side instead of stacked on top of each other. - At any point I can create a new commit that is the combination of approach 1 along with the tests and iterate from there - When doing that, I can absorb any changes made into the appropriate commit.

Possibilities kinda open up from there. Maybe intead of fully separate approaches, you just want to break the change into parallel pieces (e.g. you're not sure all of your changes will be needed as requirements change). Then I can create a "super" commit that's the combination of all the other commits even though they're not stacked. That means I can conditionally choose which commits I want to include into my "super" commit too.

A very depressing fumble. I was very high on Arc and to see what they've done has completely turned me off the company. Hopefully their telemetry was really showing them the right things but from the Arc subreddit and other commentary there seems to be a lot of unhappy people.

Ah I love that megamerge example. Thanks.

Thanks. This is a really good one. It outlines an operation that would resonate well with most developers and clearly demonstrates how much simpler, easier, and faster this is in jujutsu vs git. I think most devs just wouldn't even bother to do it in git, they'd leave the test out of order and call it a day.

I’ve been trying unsuccessfully to convert my team to jujutsu. I feel like what would be great is a page that really shows some common but complicated operations in git and how much easier they are in jujutsu. Something like the elevator pitch here but expanded on without the depth of Steve’s tutorial.

Maybe what I need to do is do a demo so people can see and ask questions.

We're seeing logins fail and trying to use the google meet and google drive APIs fail.

The permissions this asks for feel kinda insane to me. Why does a kanban board need to see the code or my deploy keys among other things?