So what is the <title> then again exactly?

Because my takeaway from the article is this: C++ piled loads and loads and them some loads of stuff onto a slim, easy, comprehensible language, is now a gigantic pile of complexity. that has precious little to do with its roots any more...and every attempt to solve its problems includes piling on more complexity.

So, how is that a problem of C?

C is not responsible for C++, simple as that.

There is no reference to it on the internet, and I'm fairly sure no bit survives. Which is sad when I think I worked 6 months on it, but someone paid me to do it, so that's nice.

I once implemented in a dead chat-app a "typing notification" by sending both the `isTyping` flag, along with the length of the unsent message. On the clients side it was displayed as a blurred lorem-ipsum of the correct length.

It was the nicest form of instant conversation I've ever had. Watching the blurred text become a message was lovely and every conversation felt snapper rather than anxiety-inducing as you start at the "x is typing" message, instead you just watch the sentance grow, then materialise.

It appears this provides a way to truly distinguish who should be protected from SARS-Cov-2 infection and who shouldn’t, given a cheap test can be manufactured.

The problem then is, that we and the individuals affected know which group they are belonging to. This makes a very alienable experience. Imagine being one of these people, virtually every other person is radioactive to you.

What would be the societal and political implications of this? Lockdowns only for people who have this marker? I can imagine people wouldn’t want to make this test as it makes them turn paranoid, could we force people to make this test?

One thing I understand as a "backend engineer" (which my front-end/web engineer colleagues usually hold in high regard): my code does exactly what I tell it to do, good logic and bad logic.

You can have the best and cleanest JS that targets FF, and have it fall over one million ways in other browsers (I'm looking at you, Safari). There is a level of respect that is lost, so far as the expertise of understanding the lowest common denominator across browsers, and actually getting that denominator to do something useful.

Front-end is, at the end of the day, much harder than backend. I understand why us backend people get praise: algorithms, distributed systems, coherency, performance, yada yada yada. Imagine coding against a system that doesn't behave consistently. No thanks.