Can't pandoc do it?

Are you suggesting PhD candidates have AI write their theses? Or just writing LaTeX commands while the students write the core text? Because if it's the latter, LaTeX usually isn't the bottleneck.

No, I am not suggesting PhD candidates have AI write their theses. The original poster implied that they typed latex code for their thesis out by hand, to which I responded that it seemed silly to do so, silly in a similar way that taking a horse drawn carriage would be vs using a car.

So, do they write their formulas like S a b f(x)dx in their hand-written source text, but then get the LLM to convert that to \int_{a}^{b}f(x)dx? Invent their own "markup" to indicate S a b is the integral from a to b? They might as well learn \int and just use that.

I write LaTeX by hand all the time whenever I need to put any math in my notes, and depending on your use-case or field, you learn the LaTeX for that which you use often and it's faster than trying to use most tools.

Anyone who wants to communicate cross-OS and doesn't want to use a whole separate application for it, when it should be a basic capability of the phone?

SMS and MMS are still a thing and I don't know anyone not having at least one of the three apps, add Threema to the mix for the nerds and that's it.

Firefox with uBlock Origin. Nothing else comes close.

That might be a good fit considering who's in charge today.

What makes Crush fun?

It has a CLI component and a very flashy TUI application. The TUI has lots of effort put in to layouts, color, and really pushing the boundaries of what a TUI can be. It looks a bit “hacker in a 2000s movie” except with pink instead of green as the dominant color.

Totally not for everybody though. I can see why some people would hate it.

You should be able to use the normal git gutter as long as your repository is colocated.

I've been using it in relatively the same way for a while now. The only meaningful changes were native support for `tug` and `absorb`, neither of which significantly changed my workflow.

eh, there have been a good amount of breaking changes. `-d`/`--destination` → `-o`/`--onto` (the former isn't yet deprecated though); deprecated `--allow-new` on push (or, forcibly making it the default for `--bookmark`); deprecated `jj bookmark track foo@bar` (and `jj bookmark track foo` having a really-weird system (I personally just call it broken, even though the behavior is intentional) of sometimes tracking the bookmark on all remotes; really I'd call jj's entire system of bookmark tracking/pulling/pushing quite incomplete outside of the trivial cases); various changed revset functions over time that break configs; and a really-annoying thing of `jj git fetch` sometimes abandoning ascendants of `@` leaving you in a confusing state (if not one with conflicts), with the solution being a future `jj git sync`.

It's certainly very usable despite all that, and the changes are simple enough to adapt to, but it's a pretty new thing.

I think for a real neophyte jj will be fine especially when used with the git backend.

Someone who "knows enough to be dangerous" may be better served by sticking with the git happy-path.

Of course, if working with others you should use what they do until you're confident that you can switch without impacting them.

Typst is amazing, but if you want HTML output, it's not quite there yet.

You don't need to subscribe to the NYT to play the games. There's a separate subscription.