WTF? We're talking about bulk here; the normal 95% of people in a profession, not the nobel prize winners. I've literally no idea how you managed even think that "rockstar" was the key issue here in any way, shape or form.
You're not trying very hard to find any counter-evidence, are you? The fact that other STEM fields are experiencing increasing balance, and our is increasingly unbalanced doesn't register for you? The many personal anecdotes are not in your site?
Worse, you don't see the increasing evidence that men and women are much, much more alike than non-alike? That both sides are fully capable of essentially all tasks that the other can do?
In ever so many fields, over the last hundred years, men have declared that only men can do job A, B, or C; it's been clearly proven wrong in basically all cases. Is our field so very different? History would say no: we are like cooking (once a male prerogative), telephone operator, surgeon, and CEO.
Damn straight. IBM had a network, and Burroughs had a network, and ICL had a network,
Except IBM. They have about four incompatible network schemes
Yes: they would have been one of "n" winners, each with incompatible content. You'd be in the situation (like the old phone companies) where a person on network "a" couldn't contact a person on network "b". That would be substantially less valuable than the fully interoperable internet we have today.
You're rather cherry-picking your data. Solyndra made a big bet: that the raw cost of the silicon in solar power would be important, and that a remarkably cool manufacturing technique to use a lot less would have a ton of value. As it turns out, that's not how the industry went: silicon costs dropped faster than anticipated, and the manufacturing costs of the Solyndra didn't.
We weren't "picking winners and losers" here: we enabled a big bet. Big bets don't always work.
And the internet was absolutely funded for years by the public purse to develop all of the major technologies and to make the same set of "big bets" about the valuable and non-valuable aspects of internet communication. Private people only became interested because of that investment.
And part of the investment was the "picking a winner". The key to the internet is that it worked across multiple vendors. If we hadn't have done that, there would be an ATT network, an IBM network, a Unisys network, and so on. The government chose a winner (cross platform) and a loser (per-company networks).
Yes, but that not how IP networks work. When the server sends you a packet, it needs to pick exactly one IP address as the destination. Because your WiFi and Cell are on different networks, they give you different IP addresses. So the server has to pick either your WiFi or your cell IP address. Once that packet is sent, it's not going to ever get to you via the "other" network.
That's why the multipath needs special support. Among other things, lots of web sites which are on multiple load-balanced servers need to affinitize your session to a single server. Those load balancers are currently (AFAICT) knowledgeable about Multipath.
My prediction: apps will have to opt-in to get this feature, but beyond setting a flag when they set up the connection, nothing more is needed.
New protocols? A low-level protocol like like a PGM or ICMP? No, the RT sockets don't let you do that (among other things, there's hardly any value: even if you made a new low--level protocol, you'd have trouble getting internet-scale adoption (heck, even useful things like PGM have trouble, and we're never getting another ICMP again).
RT Sockets are a wrapper over WinSock (aka, Windows version of BSD sockets), but with some stuff cut out and object-orient-ified.
Links: documentation is at http://msdn.microsoft.com/en-us/library/windows/apps/windows.networking.sockets.aspx/
and there's a talk: http://channel9.msdn.com/Events/Build/BUILD2011/PLAT-580T/
(cough). Actually, we rebuilt the RT Socket API from top to bottom, and part of that work involves changing all the names.
What you get with the change is APIs that actually work together: it's a smaller set of objects and radically fewer data structures and the result is something more powerful.
For example, to pull a byte-swapped integer out of a RT Socket, all you do it slap a "DataReader" onto the socket's stream, and read ints until the cows come home. In BSD, it's definitely more awkward: recv returns a void* which in practice is commonly a big char buffer which you pull data out of. But when it comes time to swab your bytes with htonl, you need to convert a pointer-to-char to a u_long. But a u_long needs to be u_long-aligned, so you can't just do some casting; you have to pull the data out and memcpy it into a u_long.
Or, to see a real advance; given a socket, you can, just by "hopping" from socket to hostname to IP information to network adapter, and from there you can get to the network information itself.
You can also directly get some useful socket statistics like your bandwidth usage and the round trip time data.
And (Ok, last point): we have sockets, and we have WebSockets (which follow the normal WebSocket protocol standards). And they have the same basic set of functions, meaning that your socket code and your websocket code are easily swappable!
Hmmm -- a quick bing search for "aviation grade connector" shows lots and lots of connectors. There are even magazine articles about them.
I'm an old fart who went to a good private school way back in the 80's. And our professors complained about our lack of work ethic, our ability to do assignments, and our writing ability.
IMHO, what's really happening is that your skills are getting better as you age, and you're automatically up-leveling what "average" is. Back when your were in college, other kids were about as good as you. But now you have years of experience and you're way better. Only you still compare yourself to the kids, and of course they do worse.
The long term tests on college performance show that we aren't in any way getting worse academically.
You asked, I answer. Yes, there are right companies to get the money, and yes, robbing Peter to pay Paul often is quite valuable.
For example, "we will collect taxes to pay to build a wall around our city", or "we will collect taxes to pay for a sewer", or "we will collect taxes to pay for lighthouses in remote areas that our ships pass near".
In those cases, the result is: fewer homes being flattened by invaders, substantially less stench, and rather many fewer dead sailors and lost cargoes.
In more modern times: it was government funding to a private company that created the Internet.
That's odd -- everywhere I look, I see government intervention done well. The road outside my door? Government. FedEx charges 20x what the government does for a letter (and delvers to fewer places). Even the Internet was a created by the government very thoughtfully creating a computer network.
In this case, our government has seen that batteries are important (which should be a "duh" -- a big chunk of the cost of, e.g., Tesla is the batteries), that advanced chemistry and processes will win, and that we really ought to fight to keep that here.
Ick -- WSAAsynGetHostByName? In this day and age, you have a window handle lying around?
I'm the Program Manager for WinSock at Microsoft. Have you looked at GetAddrInfoEx? In Windows 8/Server 2012, the DNS team added some Async features into it. Even better, it will properly handle IPv6 AND international domain names.
And if you're doing the new "Runtime" programming for Windows 8, we done our best to make sure that most network programs never have to deal with IP addresses at all -- that means that new new RT apps should be IPv6 ready out of the box.
(We also do the dual-stack thing with our sockets, so listener sockets just specify a port (or service) to listen on, and we automatically listen to both IPv6 and IPv4. We updates