Do you know what subset of C NASA limits itself to? Or hw architecture? The rigour of their testing? Should all C developers follow the same restrictions as NASA?
Hardware (according to Wikipedia) is a BAE Systems RAD750 radiation-hardened single board computer based on a ruggedized PowerPC G3 microprocessor (PowerPC 750). The computer contains 128 megabytes of volatile DRAM, and runs at 133 MHz.
Personally I firmly believe that "all C developers" do not need to follow these regulations. It might even be counter-productive to slow down the development process for some clients. For safety-critical systems, these rules make sense. For little startups, they don't.
Developers are smart enough to learn these rules, so HR shouldn't ask for "5 years MISRA experience". It's really a choice of business model, time to market, and risk management. If you're a big company looking to cut costs, be careful about outsourcing firmware development to a little startup who might not follow these rules so strictly. I won't follow these rules for the stuff I throw together in my free time and put on Github, but I will be careful before committing code to master for medical device firmware.
More job opportunities for the highly educated, absolutely. But I think you'd be suprised at just how corrupt and oligarchic the US is perceived internationally. No other western first world country comes close.
I'm a motorcyclist and do this regularly and legally on Sydney's narrow streets. It is quite safe. For leg powered cyclists riding with a reasonable degree of care it is certainly safer than the regular flow of moving traffic.
If the second person knew of the existence of the first, he could buy the glass of water and sell it to the first, pocketing any difference. Their perceived values should be similar.
No, the perceived value wouldn't be similar. If the first person is about to die of dehydration and only the water can save him, he very likely would be willing to pay more / sacrifice more to get the water. The second person will match the price only up to a point. If he had to cut his finger off to pay for the water, he wouldn't do it. But the first person might, to save his life. They value the water differently.
No, there should be an equilibrium market price in dollars thst they both pay if they are participants in a shared market. That doesn't mean the value to each is the same.
Of course, the fact that they have access to that shared market also changes the value to each of them from that in the original hypothetical.
I think we have a difference in vocabulary. I would say value and equilibrium market price refer to the same thing, but you are saying it is the particular use it has to the individual which is of course not quantifiable. Assuming the person who's had no water has access to a functioning market they will only pay market price. Arguing about them perceiving it to have a higher value seems like a pointless philosophical argument.
I think he's talking about how mismanagement of Sydney's growth has resulted in awful traffic and sky high housing market. But I'm probably being optimistic.
It works, but "works fine" is a long stretch. Takes a long time to connect, particularly after suspend, sometimes several minutes or longer. This is true of both windows and Linux.
You could also consider the Precision 5510 [1] if a Quadro GPU works for you. Essentially an XPS 15 but it includes Intel wifi. Recently got one from work and I've been pretty happy with it.
Is fsck something you'd avoid because of its name, or is the single letter change enough to make it safe?
[1] https://github.com/nvbn/thefuck