TheCee

Original poster is right by all accounts, of course. Now, let's come up with exotic significant indentations.

function xyz(a, b):
|   var x = 2

|   if true:
|   |   do_something()
|   else:
|   |   do_something_else()

|   anyway()

Pro: Your editor no longer needs to implement indentation hints.

Con: Looks obstructive if not highlighted like an indentation hint.

Your turn.

That reminds me of those times when back on reddit some dev showed up to present their new GUI library. Bragging about how they were better than Qt devs etc. (even though they didn't implement the hard parts, like working text fields or tables)

After some time a bunch of people had enough and started bullying those guys into submission about accessibility. After some time, every of those toolkits had support or at least plans for supporting screenreaders. Eventually, AccessKit became a thing.

Good times.

Of course, I might be overestimating how easy it is to get better braille oriented editors

A braille display traditionally is a personal, almost handfitted (estimated by price) device controlled by its screen reader software. Not the editor. This has some unfortunate implications:

• There is no (standardized) API to control your braille device directly. You could hand your screenreader filtered data, but that would be read as well. At best, you might be able to script your screen reader software to a varying degree of success. However:
  • Every aspect about this is extremely abysmal in every possible way, so it will likely require you to fork over some biiiiig amount of cash to one of the vendors to provide a brittle plugin. In particular if we are talking about JAWS. Think of extremely unstandardized COBOL dev with less stability and more price gauging involved.
  • As far as free readers are involved, only the proprietary and licensing aspect go away. Still, developing extensions is terrible in many ways. For example, for ORCA, I was able to find out that you can extend it somehow. Alledgedly. NVDA on the other hand has better documentation. That is to say, it has documentation. Now, you might recall that NVDA is written mostly in Python, and its devs rightly don't even pretend that one could develop stable software in Python, so APIs might change. However, I wasn't able to find a Filter function specific to braille output. That's likely because
• From my superficial experience, developers of screen readers think of braille displays mostly as an alternative to speech. It even took them quite a while to be smart about not displaying redundant, long lines of text.

So yes, you might be overestimating how easy that is, compared to telling some diva asswipe chucklefuck to use that formatter or work at McDolans.

Thanks!

Don't usual astronauts have to learn all about celestial mechanics and whatnot? Sounds like the master class to mental gymnastics.

Eh, I'd give it a spin.

"What you got there, Sandy? Ah, another cow-bone that didn't make it on the ark and got encrusted. Hold on.. UMM UMM UMM UMM UMM, there you go, original shape."

Instant-game: Trying to one-up this.

• Has also a background in biology and is an evolution denier.

Looks like a couple of used, dusty sponges, weird sponge clothes to me. I'm more worried about: Everything else.

whichadose

From what I can see it is a slightly more detailed take on dependencies, loose coupling etc. Seems like it is formal and a bit weird, though. And a few part seem... extrapolated. So, no wonder it never caught on.

Possibly. Hard to tell how much time that would have bought.

And the logical conclusion of this is there is a non-zero chance you get to enjoy the opportunity, no, the priviledge to maintain that 100k loc codebase written in someones personal PHP dialect. Lucky you.