Mikelius

Not an opinion, I have an actual situation with my eyes where they twitch uncontrollably when presented with bright lights for a long period of time. I have tried minimum screen brightness, lowered contrast/colors, auto brightness based on the environment, various software solutions to removing blue light 24/7 from the screen - none of it worked. Went permanently dark theme on everything, magically eyes haven’t twitched in years.

Light theme vs dark theme is not just a preference, it’s an actual accessibility need for some of us.

I totally thought because of how long the equals looked, it was multiple equals characters, not just >>= lol. That’s what got me confused. Don’t think these are things I’d personally use but each to their own preferences right xD

What is that weird >>=== symbol? Looks like a cross breed between C and JavaScript here.

I hate short variable names in general too, but am okay with them for iterators where i and j represent only indices, and when x/y/z represent coordinates (like a for loop going over x coordinates). In most cases I actually prefer this since it keeps me from having to think about whether I’m looking at an integer iterator or object/dictionary iterator loop, as long as the loop remains short. When it gets to be ridiculous in size, even i and j are annoying. Any other short names are a no go for me though. And my god, the abbreviations… Those are the worst.

Sorta kinda wondering (conspiracy thought, totally no evidence, just a random thing that came to my mind) if this is either an attack on AI or attempt to compromise those who use AI to write their code. Or both.

This post may have crashed Voyager twice… Once when scrolling by it, again when trying to reply. I don’t know why I can reply now.

Edit: lol I know why. My app auto updated at the same time I clicked reply. Perfect timing. Scrolling crash still unexplained though.

Use -F so you can keep getting those live reports even after the forest you’re watching vanishes