ddddddddq
> Is it real-time?
> The term "real-time" is often misused or misunderstood. We'll define it as "a provable guarantee of meeting an execution deadline when scheduling a task". In this sense, no, it is not a real-time system. If you have hard deadlines like controlling the robotic arm in an assembly line, this is not the OS for you. On the other hand, if by real time you mean "snappy performance", that we've got in spades. Our interrupt overhead is next to nothing, and there is so little background activity going on that our response time might often rival that of a real-time system.
So... not an RTOS.
Yeah, but isn't it in the private roads' owners benefit to reduce congestion, so they create HOV lanes? And what if they want to promote certain kinds of cars like electric and hybrid and therefore allow them to drive in the HOV lanes? Shouldn't they be allowed to?
Edit: Not that I necessarily agree, but this seems like a flaw in the analogy.
It seems like a giant flaw in this model is that once the service goes away for any reason your device is completely useless. You don't have the 'driver' any more and the device won't connect to a RE'd or alternate free 'driver'.
So fundamentally their complaint is: "My investment carried a risk"
Even if your page doesn't have sensitive information on it, an insecurely loaded page provides an attacker the avenue to inject potentially malicious code. This will be the case until the entire web is HTTPS-enabled.
Yes, yes, DANE, but it's not ubiquitous or even all that widely accepted.
