I don't think we pile it so high, though I have never worked in whichever civil service branch handles snow so it is only based on life-experience.
I have never seen a pile so high, we have many smaller piles scattered throughout our cities: every parking lot has one, the parking lane of most roads becomes places for snow piles, just outside of town you can see fields of small piles. The snow that is actually removed from the roads, I assume they spread that out into smaller piles as well.
Those pictures of loaders on top of huge piles of snow seems particularly dangerous.
I was wondering if anyone had information about this.
It looks like it ties to Microsoft HealthVault. That is not available in Canada. It appears (from the outside) that MS sold the "rights" to HealthVault to Telus, whom did absolute nothing with it. Does anyone know, is that the right read of the situation? Can MS ever offer HealthVault to Canada or will we have to hope that Telus will?
Also, to the people below. As far as I can see, even a service to forward the hardware from the US to Canada, this probably will not work. If you register your live account in Canada (which you probably would, so you can put a CC on it) then you will not be able to active HealthVault on your live account - it will send you to a Telus page.
What if this wasn't classified as a corner case? As you said - most MSOs are running either an old Moto or old SA as their standard box. Because headends are either Moto or SA there are actually very few unique STBs in the field. And of those, they are all versions of the same OS that either Moto or SA have been using for a long time.
If MS just threw a bunch of resources at common SA and Moto boxes to enumerate and add special code to handle these cases... could it work? Would it be a better experience? Is it worth it?
This looks to be shaping up well. Might I suggest a new word for "Favorites" though. Maybe it is silly but it seems odd to me to Favorite gore pictures et. al. "Important" or "Impactful" or something else might be a better word when the content could be that of loss and suffering.
I think they are implying you only pop() when you are doing the replacement (Trim). The rest of the time you Sink and Swim depending on how the LRU was done. IE: every time you get() an item you set the access time to now() and then call sink/swim to fix the ordering. This would give logn time to get and set.
(not hugely familiar with Java so this stuff might be wrong)
The implementation presented has some bad timing issues (List.Contains is a linear search). I think List.Remove is also a linear search. As well this implementation doesn't seem to do Point (1).
The OP is talking about a list with at most five items in it. Linear search is not an issue. Using a dict may even be slower than just searching a 5 element array linearly...
Reminds me of Stable Matching[1] but the groups aren't the same size. I guess if we can relax the "opposite sex" requirement then we reduce the problem to a Stable Roommates Problem[2] ;)
Political musing aside I think it may be disingenuous to compare modern collision-free Ethernet vs shared-medium solutions.
Modern Ethernet over twisted-pair connect directly to a switch, a quite intelligent piece of technology. During this transfer you will not get a collision because it is your wire. When all the various clients packets converge at the switch the software there will sort and buffer the traffic in a hopefully 'fair' way and then send all that traffic out a collision-free link. Repeat. (Note: old Ethernet did at one time transmit on a shared medium but most people thing of Ethernet as our modern twisted-pair-switch-n-router architecture).
ATM and other channel access methods[1] are solutions dealing with a different problem. A shared medium can quite easily become overwhelmed even if everyone is playing fair. If the link just has too many clients the network collapses. One might liken this to the "hotel wifi" or "stadium wifi" problem.
While I think more open wifi is good, the technical challenges are not trivial. Many hotels and stadiums are moving to WLAN Controller architectures coupled with highly directional APs. Just a bit ago we saw an article on how the Super Bowl will be RF Spectrum policed this time around - just to try and keep the shared medium working. There would be many policy questions around deploy, management, policing, etc. and many technical questions about channel access, network health, buffering, etc.
I am not a doctor. The body is quite good at keeping high ox levels. If your ox level is too low cell damage can occur, organ damage, etc. If your ox level gets way to low your die.
Lower than normal ox levels can help diagnose that something is "wrong" with your body (or your environment) - lung damage, heart issues, etc. It can't tell you what is wrong, just something is up.
I wouldn't use the headrest personally. In an accident the magnets will detach and the ipad will become incredibly dangerous to the passengers in the car.
The easy way to look at loose things in your car is would this hurt if it hit me from a 10 story building. However, as this is behind the seat it's probably going to mostly have forward momentum in a crash which means it's far less likely to detach and be tossed around that violently in a crash.
I suspect on average it's about as bad as holding it in your hands.
I have never seen a pile so high, we have many smaller piles scattered throughout our cities: every parking lot has one, the parking lane of most roads becomes places for snow piles, just outside of town you can see fields of small piles. The snow that is actually removed from the roads, I assume they spread that out into smaller piles as well.
Those pictures of loaders on top of huge piles of snow seems particularly dangerous.