If a 16 years old girl sends nude photo her 16 year old boyfriend in Germany, it's fine. If she does the same in US, he's pedophile. This is what RMS was talking about.
But you have to get to that future first! If you lose your customers because you can't deliver something on time due to complexity of your 'scaling-proof' system or because you can't accommodate changes requested by clients because they would compromise your architecture, scaling will be last of your worries.
(I'm not not very familiar with Postgres, but this is common among RDBMSs).
What changed is size and/or statistics. Also, if the Query Optimizer supports something like parameter sniffing, that happened.
Unacceptable? Not really. Annoying? Very much so.
>programming, where a rate of say 100 lines per day is a major achievement
Wait, what? 100 lines per day is an achievement?
I'm honestly curious in what branch of SW development this happens. I'd assume something that requires formal proof of every piece of code ever written?
What I was trying to say was that even if the captain instantly tried to reverse the course, ship has already started to move and due to size its momentum is enormous.
Do you really extrapolate that women are 'far behind' from the fact there are few female ship captains? What about coal miners or steel workers or construction crews then?
Which is as it should be. Backward compatibility and 'stability' (maybe familiarity/recognizability would be better words) are far more important than random changes/experiments that are the core features of Linux desktops.
Business-oriented means "we do realize that the money don't magically materialize out of thin air and that anything that keeps customers happy/helps attract more is significantly more important than any code purism nonsense."
But I fully agree with the rest of your comment, the more decades I spend programming, the more I realize that the answer to pretty much any question related to SW development should start with "It depends. ..."
No, great leader must recognize his weaknesses and hire people to compensate for them. If you think leaders/owners of big companies are not dictators, I have a bridge to sell to you.
Now I see the problem. You never experienced what the internet was like when it wasn't as ad-infested as it is now. It might be hard to comprehend, but people who were passionated about something and wanted to make a website about that paid for it out of their own pockets without focusing mainly on 'monetization', 'ad revenue', 'SEO' and similar garbage.
Unbelievable, isn't it?
If it's just 'random set of bits', how Google plans to use it? For it to be useful, they must have a way to decompose it to back to those categories mentioned in grandparent post, otherwise how are they going to sell it to those advertisment parasites, I mean companies?
Just from top of my head some of the programming languages I used professionaly in past 30 years - C,C++,C#,F#,Pascal,x86 assembler,D,Java,Javascript.
And I still stand behind what I said before - Go is trying to be as different as possible, for no good reason.
Time to post my favorite downvote farming comment!
What is "far right"? Is there "near right"? "middle-reach right"? 'Far right' is just a BS title used to 'adjust' the perception of people that anyone not left wing is crazy extremist nutjob.
Every time I see any Go code, it looks like the language was designed with primary goal being as different from everything else as possible. If there is X ways something is done (and you could then relate to that knowledge), you can be sure Go uses something different.