Dokuwiki user here. Your cons are true, but compared to the cons of other ones, they are all solvable. The concern with a plug-in being required to do something is silly. It’s open source and the plugin system is limitless. If it’s ugly, make a theme. I’ve never had a problem with article titles being mutilated, but then again, I treat the file name (e.g. the url of the page) separate from the root header as you’re supposed to.

Considering your comment about search being awful in another wiki, it’s pretty good in Dokuwiki.

Considering how much you care about plain text, you should probably discount the con about file names as I’m pretty sure that’s part of why Dokuwiki does what it does. It’s an actual text file sitting in a directory that matches the path.

For what it’s worth, I admire Obsidian. If it’s a personal project with no intent to share, that’s what I’d use. For business or public hosting, I’d use (and do use, at my company) Dokuwiki.

Another fun thing from this show is the magic system, which limits the caster’s ability based on what they can imagine. Programming feels exactly like that to me. I mean, a lot of human ability is limited by that, but most stuff is also limited by physical constraints long before imagination. With programming, we more often hit the limit of our imagination, or time feasibility, before any other constraint.

Working with non programmers, it’s always wild to field their unimaginative solutions, and refreshing when someone actually had a good idea.

Working with less experienced programmers, it’s fun to help them through problems. So often they hit a wall they can’t imagine walking through, take some concession and build around the wall. You can appreciate the work, and then show them the simple solution to walk through the wall. If they have talent, they grow quick.

Working with a much more experienced programmer, or in a domain you don’t have much experience with, helps keep you humble because there’s no way you’re going to learn everything.

Anyway, back to writing my spells.

Going to try to convert two 2-post racks into a 4-post rack today. Dreading the mess though.

Obviously absolute speculation on my part, but if they were truly doing what I suggested intentionally, part of the plan would need to be plausible deniability to avoid anti-monopoly issues, and also public sentiment nightmare. Killing your favorite shop out of incompetence doesn’t win good will, but you will still go there. Doing it out of malicious intent could have people in other states joining a boycott.

I’m in management, participated in the acquisition process of the company I’m at being acquired. At least at the 150mm/year revenue level there’s no one doing the shit I’m suggesting, no one is so competent. Cash on hand is bad , acquisition is an obvious way to deal with that. You’re spot on about skills though, 95% of management at every level is totally incompetent at the work required to actually do management shit. All the competent people leave as soon as they can because the work just got way harder and the money doesn’t follow.

Perhaps they realized it would be cheaper to stop the growth of a superior product. Especially when that superior product would likely require more types of costs that would eat corporate level profit. More higher paid employees that can’t be mechanized.

Status quo is incredibly profitable, assuming nothing threatens it. That’s why big business does everything they can to increase the barrier of entry, and happily overpays to buy out successful competitors, with the leadership of the competitors having enforceable noncompetes for the model.

Regardless of what the remote access test says about it being available, I had to manually port forward to fix this same issue.