Point 2 pretty much means you just want a simple abstraction on top of assembly, and for that you need simple and stupid code with a minimalistic language. It's the only good point that you've made as to why you couldn't use C++ to match your requirements.
Linus is referring to Monotone, a distributed versioning system a bit similar to Git that was written in C++. It uses the STL extensively, and it was slow because the STL is built on a paradigm where copies can easily happen without you being able to easily keep track of them.
Since C++11, work has been done to alleviate those problems with move semantics and in-place insertion.
C++ is a pragmatic language, not an idealistic one. It has everything yes, it's a strength not a weakness. All the tools are at your disposal, and you're still free to build your own style with them.
The rant from Linus is famous and old. I don't understand why people are still discovering it today and why they feel the need to discuss it. Linus doesn't like C++ as a systems programming language. He doesn't want any in his project. He never claimed that C++ was bad for everything, he just thinks it's bad for what he does (some people agree, some don't).
And he pretty much hates most other programming languages much more than he hates C++. He thinks that Java is horrible for everything for example.
'premiere' instead of 'premier' is not a typo, it is clear that the OP thought this was the correct word and spelling. In my case though, words/worlds is indeed a typo, of the kind that I often make, in part because of muscle memory. I tend to write a word for another when multiple consonants are tied together and I don't proofread correctly. Arguably my post still made sense so I could have let it go instead of pointing it out, but I did notice the irony of my mistake at the time.
I also doubt you've seen that error in a slashdot summary a couple of days ago.
I like how you're confusing the northern hemisphere with North America. Maybe you should actually look at data before making such bold generalizations.
The color of the pixels is white and gold. The white is blue-ish of course, but the people who see the dress as white and gold can clearly see that. People who see it as white and gold see the real colors of the pixels. People who see it as blue and black have their brain doing color compensation automatically.
I'd say the normal people are the one who see it white and gold...
There are plenty of companies that do high-end videoconference equipment (they often call it telepresence), Lifesize isn't the only actor in this area. The leader is Tandberg/Cisco, Polycom is a cheaper alternative.
You need to change your company name. Something similar happened to my company. It got created in Europe at the same time as some other company with the same name in the US. We got the trademark in Europe, they got it in the US. We each got about half of the domain names, but they were better at the Internet game and got more visibility. A lot of people were confusing us for that company, including our clients. We had no choice but to change the name, and when we did it really helped with the business.
The icons don't like that different than usual, I see no problems with it. They're a bit too bright for my liking, I find it a bit aggressive, but that's the style these days apparently.
What is really problematic in the screenshot though, is the "This PC" text. It's barely readable. There are two shades of blue next to each other that are almost the same, and in one the text is white and in the other it's black. It's incoherent. They need to fix their color scheme and take accessibility into account.
The optimal code depends of each micro-architecture, and there are plenty of different x86 ones deployed everywhere, so you need to know a little bit of each. Transferring that expertise to ARM or POWER isn't that difficult either. They're more different, but the same principles still apply.
Most of the time though, optimizations are entirely portable. Using the cache well for example, can be done in a way that is independent on the cache and cache line size in certain scenarios, and in others you can use a portable function to fetch the size.
Actually, people who have high levels of knowledge usually expect anyone working in science to know a lot as well, as they're aware of the vast diversity of things and their own lack of knowledge in many areas. People who think they know more than others usually only have a superficial understanding of things.
My job is to optimize some other people's code. You'd be impressed how many people have no idea how to program to use caches effectively. People than know pipelines how to make the most of the pipeline are even rarer.
Slashdot Mirror
Point 2 pretty much means you just want a simple abstraction on top of assembly, and for that you need simple and stupid code with a minimalistic language.
It's the only good point that you've made as to why you couldn't use C++ to match your requirements.
Linus is referring to Monotone, a distributed versioning system a bit similar to Git that was written in C++.
It uses the STL extensively, and it was slow because the STL is built on a paradigm where copies can easily happen without you being able to easily keep track of them.
Since C++11, work has been done to alleviate those problems with move semantics and in-place insertion.
C++ is not about object-oriented programming. It's a multi-paradigm language, and OOP is one that tends to be shunned by its users.
C++ is a pragmatic language, not an idealistic one.
It has everything yes, it's a strength not a weakness. All the tools are at your disposal, and you're still free to build your own style with them.
C can cast away constness too.
C++ added special constructs for this to make it more explicit you were doing something evil.
C++ is a language for experts, but so is C.
There are two bad ways to code in C++: the C way and the Java way.
You're talking of inheritance, that's something you use in the Java way.
The rant from Linus is famous and old. I don't understand why people are still discovering it today and why they feel the need to discuss it.
Linus doesn't like C++ as a systems programming language. He doesn't want any in his project. He never claimed that C++ was bad for everything, he just thinks it's bad for what he does (some people agree, some don't).
And he pretty much hates most other programming languages much more than he hates C++. He thinks that Java is horrible for everything for example.
'premiere' instead of 'premier' is not a typo, it is clear that the OP thought this was the correct word and spelling.
In my case though, words/worlds is indeed a typo, of the kind that I often make, in part because of muscle memory. I tend to write a word for another when multiple consonants are tied together and I don't proofread correctly.
Arguably my post still made sense so I could have let it go instead of pointing it out, but I did notice the irony of my mistake at the time.
I also doubt you've seen that error in a slashdot summary a couple of days ago.
Unfortunately, for that kind of decision political and economical factors are more important than technical ones.
People typically don't wash coats and typically wear them every day and all the time when they're outside (in winter that is).
At the scale of big cities, 20 miles is not that far away.
London for example is 25 miles wide.
I like how you're confusing the northern hemisphere with North America.
Maybe you should actually look at data before making such bold generalizations.
If your employees believe they're working for the other company, clearly it is impacting you!
The color of the pixels is white and gold. The white is blue-ish of course, but the people who see the dress as white and gold can clearly see that.
People who see it as white and gold see the real colors of the pixels. People who see it as blue and black have their brain doing color compensation automatically.
I'd say the normal people are the one who see it white and gold...
There are plenty of companies that do high-end videoconference equipment (they often call it telepresence), Lifesize isn't the only actor in this area.
The leader is Tandberg/Cisco, Polycom is a cheaper alternative.
You need to change your company name.
Something similar happened to my company. It got created in Europe at the same time as some other company with the same name in the US. We got the trademark in Europe, they got it in the US. We each got about half of the domain names, but they were better at the Internet game and got more visibility. A lot of people were confusing us for that company, including our clients. We had no choice but to change the name, and when we did it really helped with the business.
I don't understand why you'd need to buy an adapter at all.
Just put the disk in another computer. All desktop motherboards still have IDE.
The icons don't like that different than usual, I see no problems with it. They're a bit too bright for my liking, I find it a bit aggressive, but that's the style these days apparently.
What is really problematic in the screenshot though, is the "This PC" text. It's barely readable. There are two shades of blue next to each other that are almost the same, and in one the text is white and in the other it's black. It's incoherent.
They need to fix their color scheme and take accessibility into account.
Looks like it could be worth it to implement some advanced auto-aim technology.
A Parrot drone cannot stay in the air for 24 consecutive hours.
The optimal code depends of each micro-architecture, and there are plenty of different x86 ones deployed everywhere, so you need to know a little bit of each.
Transferring that expertise to ARM or POWER isn't that difficult either. They're more different, but the same principles still apply.
Most of the time though, optimizations are entirely portable. Using the cache well for example, can be done in a way that is independent on the cache and cache line size in certain scenarios, and in others you can use a portable function to fetch the size.
Actually, people who have high levels of knowledge usually expect anyone working in science to know a lot as well, as they're aware of the vast diversity of things and their own lack of knowledge in many areas.
People who think they know more than others usually only have a superficial understanding of things.
My job is to optimize some other people's code.
You'd be impressed how many people have no idea how to program to use caches effectively.
People than know pipelines how to make the most of the pipeline are even rarer.
words not worlds, sorry.