> In a fair market this should kick the door down for AMD.
What's the betting intel are pushing M$ to enable the KPTI patch for all chips regardless of mfr to try and shore up relative losses in performance?
23 posts • joined 6 May 2014
> Umm I don't think you get enough leakage from microwaves to affect your WiFi. They are after all very carefully shielded against radiating.
My old microwave used to knock out the wifi without fail. You've got to remember that 1000W microwave only has to leak 0.1% of it's energy to equal your 1W wifi access point.
Looks like you're getting downvoted despite your point being valid AndrueC.
One thing I would say is that it probably isn't always true for something as complex as core kernel/driver code, which is always going to be pretty hairy in places. Applications code on the other hand, there's no excuses.
I have self cancelling indicators on my motorbike (Honda Crosstourer) and they're the work of satan. Really bad idea - they self cancel way too early on larger roundabouts, just like car indicators often do.... except it's much much easier to not notice it's happened on a bike (can't hear them, and you can't really be looking down at the dash to check while negotiating a big junction). I don't know how you implement them on a motorbike reliably. You very infrequently use much steering angle at all, and you can be steering the 'wrong' way (https://en.wikipedia.org/wiki/Countersteering) or if you're going really slow, the 'right' way.
> where's the problem?
the problem is, NTP doesn't work like that. It proactively notifies the client of an upcoming leap second, and the client should attempt to deal with it by inserting or deleting an extra second, not by just discovering the clock is wrong by a second at some point afterward.
Biting the hand that feeds IT © 1998–2018