__d
Joined 12 years ago
Joined 12 years ago
C++ is perhaps the worst case, but C and Python also suffer badly. Java, C#, and Swift perhaps too.
Once a language reaches broad adoption, it should be frozen. If you want to make changes, then feel free to call it something else. The only good reason for standards committees is to resolve ambiguities in the initial specification.
It’s a misapplication of skills and interests. Language people want to add new stuff, fix old stuff, and make their language universally applicable. Putting them in charge of the spec is bound to end in a C++ style disaster.
Unix used to have a glob command, rather than building it into the shells (and the C library). I think it was 7th edition that added it directly to Bourne shell.
If you want job training, get certifications.
To this day there are people who still use Wordstar, for instance.
I contend that it chose to invade because its leader wants to integrate Ukraine into the Russian Federation, and offered this as evidence of that desire. I think that contradicts your statement as to the true rationale for the invasion.
https://en.wikisource.org/wiki/On_the_Historical_Unity_of_Ru...
The US is choosing to leverage its position without much concern for those consequences right now. The rest of the world is busy routing around that, and the leverage is slowly reducing.
It will take time: the US was a key member of the world economy. But there’s frequent new reminders of why it’s necessary.
There’s a lot of things the rest of the world has no or bad backups for.
People used it to write business applications. Like Microsoft Access, or Visual Basic.
It started as a competitor to dBase II/III called FoxBase, and then Microsoft bought it.
There was an opportunity to build out graphical management tools, but NIS+ kinda got in the way, and the politics of commercial Unix in general didn't help.