FizzyOrange

Actually chars() is pretty simple - it's just UTF-8 decoding which is elegant and simple.

The complexity is all around unicode, not UTF-8.

Interesting. But can't you do basically the same thing with @nonnull annotations? I remember using something like that a decade ago when I last wrote Java.

IMO automated changelogs like these are not especially useful. Better than no changelog I guess, but nowhere near as good as a proper changelog. But proper changelogs take actual effort.

IDEs tend to work out of the box while the likes of vim or emacs need configuration and have an initially steep learning curve.

Not in my experience. It's very easy to design systems that break IDE support. People love adding all sorts of ad hoc build scripts that mean you can't just press F5 or whatever. It takes discipline and caring about IDEs to not do that.

And while people might love tweaking Emacs and Vim, it isn't required.

There's definitely an element of snobbery, and also of being lazy about tooling. Do you think once you become a talented dev you lose all human vices?

Some of the smartest people in the world believe in an imaginary dad who lives in the sky and grants imperceptible wishes. Everyone is human.

I completely agree. Also almost all of the fancy editing you can do with Vim can be done just with multiple cursors, and it's less annoying because you do it incrementally (rather than typing a long sequence of commands and then seeing the result), and you much less to memorise.

Yeah but one is using Tk and the other doesn't look any better than git log --graph. I think the point of this is that it looks okish and is in the terminal.

Doesn't look like it.

I agree. C2 continuity does matter for aesthetics sometimes, but not for a button.

Even KISS. Sometimes things just have to be complex. Of course you should aim for simplicity where possible, but I've seen people fight against better and more capable options just because they weren't as simple and thus violated the KISS "rule".

One example is creating an interface for every goddamn class I make because of “loose coupling” when in reality none of these classes are ever going to have an alternative implementation.

Sounds like you've learned the answer!

Virtual all programming principles like that should never be applied blindly in all situations. You basically need to develop taste through experience... and caring about code quality (lots of people have experience but don't give a shit what they're excreting).

Stuff like DRY and SOLID are guidelines not rules.

Thanks for highlighting your username - made me notice that you post a lot of nonsense here so I can easily block it!