My parish priest told me he uses AI to edit newsletter posts. He didn't say he used it to write. And he mentioned using Magesterium.ai, which is a chatbot trained on a pretty conservative Catholic corpus (eg, it knows almost nothing about the Catholic Worker movement).
One thing I appreciate in our diocese is that the priests are encouraged to deliver their homilies without a written script. I think that is very wise, as it forces them to preach from instinct and heart, not from a script, either AI or human written.
I've been using Vim only about a year, and just finished drafting an academic-trade crossover book with extensive endnotes in it. I've tried Pencil and Goyo, but ended up finding that a pretty tiny vimrc file was all I needed. No plugins.
I launch with `vim -O [2-3 working files]` and am good to go. Learning vim itself is hard enough, and rewarding enough, that plugins feel extreme, especially for prose writing.
For me, too late, because my workflow is already full of little pandoc scripts that do document conversion wherever I need it!
But I wonder if the killer app might be a browser plugin, not a website. Highlight text on any webpage, convert it to whatever. Saves the copy-paste, and hopefully stays on the local machine.
I'm not sure I agree. It takes getting used to, and the default designs tend to feel old-fashioned, giving a false impression that it won't do what you need. The settings feel like you're almost in a config file. Except for on old computers, Gnome or Cosmic are safer starting points.
I guess I assume "BS" means "UX flourishes that most end users are used to," and I'm not sure minimizing it immediately is the best approach to bring people into the ecosystem.
I've tried Cosmic recently and it's glitches galore right now (on nvidia at least). I think safest point is KDE. The most familiar paradigm, mature wayland support with mixed refresh rate displays, HDR and other modern features that XFCE can't do.
Yeah, I think it might be a driver thing (or driver interaction with XFCE code).
After ~10 years of using XFCE, I recently for the first time encountered flickering, after an NVidia driver update. I disabled compositing and it went away. Still happy, but clearly something broke there. Pretty sure someone's trying to fix it, somewhere.
> the default designs tend to feel old-fashioned, giving a false impression that it won't do what you need
Who is actually getting this impression? What thing that they "need" is in doubt?
> I guess I assume "BS" means "UX flourishes that most end users are used to,"
You assume incorrectly. Every OS and DE finds some way to be obnoxious, even when you've learned the tricks and keyboard shortcuts. XFCE just seems to have the least of them. It's predictable. I think a new user will be able to navigate it immediately. I don't know about KDE, but I sure couldn't say the same about Gnome 3.
> The settings feel like you're almost in a config file.
What on earth?
No, the config has dialogues and intuitive controls. There is a settings-editor you can go into if you need to, with a bit more of a regedit kinda feel, but I haven't looked in there in years.
> Gnome or Cosmic are safer starting points.
In Gnome, can I move the UI elements to locations I want them in? Or are we still in a situation where it's opinionated and you have to seek plugins to get an experience that you actually want?
> In Gnome, can I move the UI elements to locations I want them in?
No.
> Or are we still in a situation where it's opinionated and you have to seek plugins to get an experience that you actually want?
Yes, 100%.
COSMIC feels like GNOME but done right to me. It's not as pretty but while it looks and works pretty much the same by default, you can choose what goes where.
For older machines I'd recommend Mate. It's a fork of old Gnome 2, so it got a lot more polish back on the day, even though some of it bit rotted away.
It's still a very nice desktop and you can combine it with Compiz if you want to have some fun.
"Too late now, I suppose, but the only file extension I would endorse is “.markdown” [...]
(I personally use “.text” for my own files, and have BBEdit set to use Markdown syntax coloring for that extension, which is why I never saw a need to endorse an official extension.)"
It is my assumption that Gruber chose ‘.text’ over ‘.txt’ for several reasons. To give it a little difference when searching for files. To be more legible to non-computer people. And finally, while Classic MacOS did not use file extensions, the Resource Fork type code for text files was ‘TEXT’
Also a little extra distinction: “.txt” is a relic of 8.3 DOS filename conventions. He was not bound by these. If you’ve got the space, of course you’ll go with “.text” over “.txt” because text is the input, HTML is the output, Markdown is the tool for converting one into the other, per the first line of the introduction:
> Markdown is a text-to-HTML conversion tool for web writers.
Ergo they’re not Markdown documents, they’re text files that can be converted into HTML using Markdown.
One thing I appreciate in our diocese is that the priests are encouraged to deliver their homilies without a written script. I think that is very wise, as it forces them to preach from instinct and heart, not from a script, either AI or human written.
reply