How do we know the false positives for this "Mythos" thingamabob? Since they didn't release it, and we cannot reproduce it, are we to simply believe their word on this? What if the author of the featured article simply made a claim about that? We also simply believe their word? To me these AI tech companies are not any more trustworthy than a random blog author, maybe even less so, due to all the shady stuff they are pulling and especially since they have not released. Show or it didn't happen.

What's the difference between "snapshots" and git commits? In my mind a git commit is already a snapshot of the repo and the changes one staged. In what way can you move around more freely than what one can do with magit, deciding for files, hunks, or even single lines of code, whether or not they get staged and committed?

You're right that git commits are snapshots.

jj is very non-modal, that is, it doesn't tend to have a lot of state that commands rely on. As an example of what I mean, because jj does not have a staging area, everything is already committed, which makes it very easy to say, move to a different commit: you don't need to stash your working copy, as jj has already stashed it for you. Similarly, due to the auto-rebase behavior, you can be working in one part of the tree, realize something somewhere else should be moved, and go rebase that without even moving to it at all!

As a small example: say I'm working on something, and I find a typo. I want to send that typo in as a PR, but I don't want to do it as part of my work. I can do that with:

1. make the change in my current working copy (@)

2. jj split -o trunk (selecting the typo contents to split off the typo fix into a new change on top of (hence -o) trunk)

3. jj log (go check out what the change id of that change is

4. jj git push -c <change id I found in 3>

No need to even move my own HEAD (in git terms), just knock it out inline in a few steps while I'm working.

Now, as for magit, I don't use it, and I know that those that do love it and it does make some of this stuff easier. But not everyone can use magit. And there are "magit, but jj" projects as well, but I can't speak to them or which is best at the moment.

Technically, nothing. But psychologically git commits represent a unit of completed work, whereas with AI agents what's needed is a kind of agent-wise undo history such that you can revert back to the state of the repo 1 minute ago before Claude did an oopsie all over your repo.

You can definitely use git as a backend for building such a system, but some extra tooling is necessary.

Just create a new branch before you implement new features and if the agent messes up don't merge the branch.

That way you get the best of both worlds. The buggy code is still there in case it's needed but it's not in the main branch

Most of the time when I'm using Claude my working tree is already dirty because I'm mid-task. I usually try to do a throwaway commit before every interaction with Claude, but it's easy to forget, or to leave the "accept edits" mode on accidentally and my working tree gets corrupted. Also having to commit takes you out of flow because you suddenly have to deal with any new gitignores, which requires at least a glance at untracked files to make sure you're not committing anything you shouldn't be. I want to be able to undo the state of my working tree to the moment before a particular interaction with Claude, just like how I can undo a file.

jj offers "jj undo" which will undo changes to your repo, and the "oplog", which is sort of like the reflog, but on steroids. It's one of the nicest things about it.

> You can definitely use git as a backend for building such a system, but some extra tooling is necessary

Is it? There’s the stash for storing patches, the index for storing good hunks, branching for trying out different experiments. You can even use worktree if you want separate working directory especially when there will be changes in the untracked files.

Git has a lot of tooling for dealing with changes, directly or at the meta layer.

git checkout @{1.minute.ago}

I think the GP is relating to MS services and accounts as utilities that should not be possible to be taken away easily, not about Wireguard.

Even if they somehow were so expensive, that it would no longer scale to their size, that is still not our problem and if anything, a sign that either they need to improve their systems, or simply cannot be as big as they are. Shit happens, scale down, I won't cry for them.

I have a feeling, that the resolve to do something about it is waning in the EU, because of the plans to soften up the GDPR.

About the work being more enjoyable when seeing it as a craft: I think it only is more enjoyable, if you can somehow bring part of your craftsmanship into it, and are not overly limited by other people or the sprint or management or any of the other many factors that ruin the fun, like time available, terrible inherited codebase that would take weeks or months to fix, and so on.

Well, sure, there are aspects of the work that can suck the joy out of it, but that's part of it. :) Even in personal projects I can create a codebase that's difficult to work with, or depend on third party code and tools that I don't particularly enjoy. The tricky task is navigating in and around these hurdles, knowing how and when to address them, and ultimately, simply accepting them. If your expectation is constant enjoyment, you'll be disappointed not just at work, but at life in general.

That said, I struggle with this as well, so I'm speaking more aspirationally than from a place of wisdom. :)

As a first step they could give back some of their illegal settlements. Then over time give back more, until they are back in UN recognized borders. That would be a start. They could also start to persecute violent mobs that chased people out of their own homes and the people in the military covering them. They could also release unjustifiably imprisoned people.

You know, things that basic human decency would demand of them.

And yet that laptop stand is not even the slightest bit slanted, one of the crucial details. I could simply take a book and put the laptop on top of that, to get the same ergonomic features. I am aware that ergonomic use is not the main point, but it would certainly not have hurt to consider that angle at least a little bit.

That would have destroyed the brutalist cred.

Use a random cement brick instead of a book, then.

No, gotta use concrete.

Why would this matter? If you were typing on it, that would be helpful, but this is for a laptop that sits on the side, while the user types on a separate (and likely much better) keyboard.

Haha, consider that angle. (I'll show myself out.)

I found your comment funny and I only realized this pun when I read my own comment after posting it. I hope you keep your humor, despite being downvoted. You are probably downvoted, because people think it doesn't add much to the topic, and not because it isn't funny. (I hope so, at least.)

That's a heartwarming response, thank you!

I am guessing these companies were not big enough to make enough of a fuss and have a good legal team? Google likes making money, and if there is the slightest reason to not have to pay someone, then they are gonna make use of that reason. Might even make it onto someone's KPI list of "prevented fraud".

Would be good to not depend on the US that much any longer, since they have proven to be such an unreliable "partner". Even in a non-Trump future one cannot rely upon some future election not resulting in some similar disaster. Better to pull out, before some hothead gets weird ideas about that gold.

Maybe the fact that US soldiers and military bases exist inside Germany's borders is slightly more important than where the gold is. First regain your sovereignty, I'd say.

Nothing wrong with going for the low hanging fruit first.

Yes, close Ramstein and close Landstuhl, which were used for every US war in the Middle East in the last 30 years.

The USA is threatening to pull out of NATO anyway, so those might go away.

I am guessing that these bases are one of the last things to go. Would be a major diplomatic incident. But then again Trump creates those for breakfast, so who knows when we finally have had enough.