I feel strangely offended that here in Czechia there are actually no ads on BBC podcasts …

vim-fugitive

If you say that you can work only with JJ and never use git, you are delusional. For one, where is that JJ forge (i.e., the equivalent of Sourcehut)?

GitHub, or sourcehut, or whatever you prefer.

Maybe you feel that jj git fetch and jj git push are using "git" but it means you avoid the git cli in favour of the IMO better designed jj cli.

I could respond to this uselessly pedantic comment, but then nobody wins.

I didn’t mean to be pedantic. My experience with Jujutsu was as bad as with Mercurial (and hg-git, I believe?) … after couple of hours working with my repo (https://git.sr.ht/~mcepl/m2crypto), looking at it with git, I got incomprehensible mess of destroyed multiple unmergeable heads (especially for Mercurial), and completely destroyed other branches, where I was not planning to work (Jujutsu). The only resolution in both case was export my work to plain patches, rm -r the checkout, clone again with git and forget anything about those other VCSes.

So, I claim that Jujutsu actually doesn’t work well with git repositories (and forges) very well, and I would like to see a native one.

It works fine for my use case, all my Github repos are in the state I'd expect, and I sometimes use git in my local repos as well, and that works fine. Hell, sometimes I use jj to fix a mess I made in git.

The only issue is being in detached HEAD all the time, but in practice it's not a big problem for me.

I am very confused as to what happened to you here, that’s not usual.

Most of jj’s stuff is purely local. I woke on GitHub with jj just fine, the only thing people notice is that my autogenerated branch named are a bit odd.

You cannot give millions of USD to potential authors if you are tiny webserver-running small business. That’s what the article was all about.

yes, I haven’t managed for a week, but I tried to Jujutsu and gave up. It is too complicated for no visible gain. Plus, there is no infrastructure supporting it (in the end, you store the stuff in the crippled git repositories). `git commit --amend` and `git rebase --update-refs` together with few scripts (e.g., https://git.sr.ht/~mcepl/git-fixup) does the same, and I am still with true git.

Git infrastructure works just fine with jj...

And there's nothing crippled about thr git repos.

Try jjui for a great TUI experience on top of jj.

Yeah, we are just paying customers, who cares about us, right?

I don’t think it is that simple. Itanium was for years supported for example by RHEL (including GCC working of course, if anybody cared enough they could invest into optimising that), it is not like the whole fiasco happened in one moment. No, Itanium was genuinely a bad design, which never got fixed, because it apparently couldn’t be.

Well, yes, the market didn't care all that much for various reasons. (There were reasons beyond technology.) RHEL/GCC supported but, while I wasn't there at the time, I'm not sure how much focus there was. Other companies were hedging their bets on Itanium at the time--e.g. Project Monterey. Aside from Sun, most of the majors were placing Itanium bets to some degree if only to hedge other projects.

Even HP dropped it eventually. And the former CEO of Intel (who was CTO during much of the time Itanium was active) said in a trade press interview that he wished they had just done a more enterprisey Xeon--which happened eventually anyway.

> Copyright terms have been radically extended in this country largely to keep pace with Europe, where the standard has long been that copyrights last for the life of the author plus 50 years. But the European idea, “It’s based on natural law as opposed to positive law,” Lateef Mtima, a copyright scholar at Howard University Law School, said. “Their whole thought process is coming out of France and Hugo and those guys that like, you know, ‘My work is my enfant,’” he said, “and the state has absolutely no right to do anything with it—kind of a Lockean point of view.” As the world has flattened, copyright laws have converged, lest one country be at a disadvantage by freeing its intellectual products for exploitation by the others. And so the American idea of using copyright primarily as a vehicle, per the constitution, “to promote the Progress of Science and useful Arts,” not to protect authors, has eroded to the point where today we’ve locked up nearly every book published after 1923.

This is disingenuous: the article doesn’t mention that the biggest proponent of the prolonging of the copyright terms were Americans (e.g., Walt Disney Corp and Jack Valenti, see “Mickey Mouse Protection Act” for more) not Europeans.

The author specifically mentions, and benchmarks against, ripgrep in the linked content.

ripgrep is brilliant and I use it a lot but it has no knowledge of the languages it works with so I don't use it for searching anything more than names of functions or stuff.

If you really need to search for code constructs that can span multiple lines (but not always do) then Treesitter-aware tools like ast-grep and gritql are superior.

Ripgrep lacks the “& replace” bit.

Nah.

   $ rg 'sear' -r 'repl' file.txt

That only replaces in the output. ambr seems to actually modify the file contents, like `sed -i`. ripgrep never modifies the contents of files.

Right, can use --passthru and > or sponge to write it to disk.

Edit: Oh, it's you. Thanks for a brilliant tool, I use it every workday and have been for years.

Thanks!