wols

It does and you can safely ignore us.
Just two pendants nitpicking people's spelling on the internet.

!corsicanguppy appeared to imply your spelling of "till" to be incorrect and that the "correct" spelling is "'til". I pointed them to a dictionary describing the word with the spelling you used and the meaning you intended.
Both comments are inconsequential to your point, and to anything, really.!<

till

Ditto on the no text part. That is an accessibility failure that's way too widespread.
Sometimes I'm afraid to even push a button: does this delete my thing, or does it do some other irreversible change? Will I be able to tell what it did? Maybe it does something completely different, or maybe I'm lucky and it does in fact perform the action I'm looking for and which in my mind is a no-brainer to include?

And it's infected interpersonal communication too - people peppering their messages with emojis, even professional communications. It not only looks goofy, but is either redundant (when people just add the emoji together with the word it's meant to represent - such a bizarre practice) or, worse, ambiguous when the pictogram replaces the word and the recipient(s) can't make out what it depicts.
The most fun is when it's a mix - the message contains some emojis with accompanying translation, some without.

I don't share the hate for flat design.
It's cleaner than the others, simpler and less distracting. Easier on the eyes, too. It takes itself seriously and does so successfully imo (nice try, aero). It feels professional in a way all the previous eras don't - they seem almost child-like by comparison.

Modern design cultivates recognizable interactions by following conventions and common design language instead of goofy icons and high contrast colors. To me, modern software interfaces look like tools; the further you go back in time, the more they look like toys.

Old designs can be charming if executed well and in the right context. But I'm glad most things don't look like they did 30 years ago.

I'm guessing many people associate older designs with the era they belonged to and the internet culture at the time. Perhaps rosy memories of younger days. Contrasting that with the overbearing corporate atmosphere of today and a general sense of a lack of authenticity in digital spaces everywhere, it's not unreasonable to see flat design as sterile and soulless. But to me it just looks sleek and efficient.
I used to spend hours trying to customize UIs to my liking, nowadays pretty much everything just looks good out of the box.

The one major gripe I have is with the tendency of modern designs to hide interactions behind deeply nested menu hopping. That one feels like an over-correction from the excessively cluttered menus of the past.
That and the fact that there's way too many "settings" sections and you can never figure out which one has the thing you're looking for.

P S. The picture did flat design dirty by putting it on white background - we're living in the era of dark mode!

That's fair enough, thanks for elaborating!

What do you hate about it?
I'm generally just uninterested in genres I don't enjoy, save for movies that instill and spread hate and intolerance or try to pass off falsehoods as fact.

That number is like 20 years old.

Today it's around 60 billion.

This works as a general guideline, but sometimes you aren't able to write the code in a way that truly self-documents.
If you come back to a function after a month and need half an hour to understand it, you should probably add some comments explaining what was done and why it was done that way (in addition to considering if you should perhaps rewrite it entirely).
If your code is going to be used by third parties, you almost always need more documentation than the raw code.

Yes documentation can become obsolete. So constrain its use to cases where it actually adds clarity and commit to keeping it up to date with the evolving code.

The point is that you're not fixing the problem, you're just masking it (and one could even argue enabling it).

The same way adding another 4 lane highway doesn't fix traffic long term (increasing highway throughput leads to more people leads to more cars leads to congestion all over again) simply adding more RAM is only a temporary solution.

Developers use the excuse of people having access to more RAM as justification to produce more and more bloated software. In 5 years you'll likely struggle even with 32GiB, because everything uses more.
That's not sustainable, and it's not necessary.

As always, the dose makes the poison.
A common scenario is people picking the wrong species and then not just eating a small bite, but cooking an entire meal and eating that.

A small bite may not kill you, but just one mushroom (50g) can be enough to do it.

There are some toxic mfs out there and they can be mistaken for edible lookalikes by inexperienced foragers.

Many of the programming languages that are regularly the butt of everyone's jokes don't just allow you to use them badly, they make it easy to do so, sometimes easier than using them well.
This is not a good thing. A good language should

• be well suited to the task at hand
• be easy to use correctly
• be hard to use incorrectly

The reality is that the average software developer barely knows best practices, much less how to apply them effectively.
This fact, combined with languages that make it easy to shoot yourself in the foot leads to lots of bad code in the wild.

There's something almost dreamlike to this picture.

He looks weightless yet somehow at the same time really heavy.

Trapped in a nightmare of man's creation, he's a prisoner in this absurd dimension, forever cursed to run but getting nowhere, inert and lost, desperate but powerless, unable to satiate his urgent need for freedom.

Truly a testament to the state of this society.