Oh no... I remember nightmare bain-breaker UIs from the 90s; they were normal then. I'd forgotten they were still around in workplaces. Great line BTW, "More clicks than a school for dolphin telegraph operators." I'm thankful I've only had to use one bad desktop GUI in the last 15 years, but on Android, EveryCircuit is pretty bad. The back button does insanely inconsistent things. There's no way to search your own circuits so finding a circuit can require literally an hour of scrolling. Of course, the actual chance of finding it is low. There are other faults. In the last few months, they've been making silly changes under the banner of "improving the UI" without even touching the serious faults.
Java allows all of unicode too, now? I remember the Go team touting this feature as a good thing when Go was launched. This reminds me of when I tried to use the last stable release of SP-Forth. Most of the comments were in Russian. Some of the defined words were in Cyrillic characters.
The files were in two different character encodings, neither of which were UTF-8. The last stable release was old; I should have updated, but it was easier to just fall back to Gforth.
Oh! Speaking of GNU complexity and bloat:
Gforth! It's bad. It was already bad in the mid-00s. Parts of SP-Forth were more readable
despite the Russian comments! I may be exaggerating; I no longer have a SP-Forth install to check, but I do recall feeling happier with SP-Forth. Anyway, Pforth is 100 times more readable than Gforth. And don't get me started on Gforth's rapid, recent namespace bloat -- this despite its own author saying its compiler's whole design is no longer a good idea and a fresh start would be good. But I think the namespace bloat is probably related to increased development of
net2o, and that is interesting. (I still need to decide on namespace management techniques for my Forth.)