I would hardly credit Apple for that, given that they are pretty much non-existent in the sub-$300 market. I would have to give the credit to Google with Android and Chromebooks. Though really, it's just that hardware got cheap enough and still good enough that a computer that cheap is actually viable. Which means, of course, that Microsoft is very active in the sub-$300 market now. Apple? Not so much.
The default in Windows now when it BSOD's is to reboot. Of course, if it just boots up into another BSOD, that's how you get the reboot loops. If it's more of the random fluke BSOD, you just come back and see your computer restarted (oh, must have been Windows Update...again....). That's how people claim that they've not seen a BSOD in years. You can turn that nonsense off if you want, though I wouldn't trust Windows 10 to not ignore it and do whatever it wants regardless of the setting.
My state has a similar, but more reasonable law, that you can't leave your car running unattended with the keys in the ignition. So the solution is one of those remote starters that lets the car run without the keys in it, and here that is legal.
Even if the keys are in it, you don't actually have to have your ass in the driver's seat, so long as the car is not unattended. So if you're scraping the ice off or are otherwise nearby you're not breaking the law even if there's no one actually in the car.
Keep in mind that your dollar store alkalines will likely not last nearly as long as a decent set of alkalines. Generally the dollars per run time ratio still favors the cheap batteries if don't mind having to swap them out more often, but you're getting what you paid for.
And if you're going to be lazy and not check up on the batteries in the flashlights in your emergency kit, I'd recommend getting Lithium batteries (not Lithium-ion, these are not rechargeable). They are more expensive, but they have a longer shelf-life, and won't leak like alkaline batteries. They'll also last longer if you need to use them.
I've found the longer the paper takes to read generally means the less worthwhile the paper is. I've read some papers in fields I'm familiar with, and when I get done I still don't know WTF they're talking about. So I start breaking it down, slashing through all the jargon and word soup, working through the math myself, and finally when I understand what they're actually saying.... I realize they really don't have much. A bunch of dense language, big words, and technical terms thrown about with some fancy-looking charts and it all looks very impressive, but in reality what they've done is pretty minor and not that novel. They know it too, and know it's not good for a multi-page paper, hence a massive amount of filler - most of which is just reiterating basic things that everyone already knows once you've managed to hack through it.
On the other side, go pick up one of the famous, ground-breaking papers in the field that everyone knows about and cites. In comparison, you'll find those papers easy to read - they are clearly written, using simple language, and easy to follow and understand (maybe longer to digest though). There's really no reason to have to dress it all up, as the science stands on its own.
Well that explains some of the old, obsolete, inefficient systems I've seen still chugging along. "It's too much trouble to replace it" they say. I'm no expect on HVAC, but it didn't look all that difficult to replace it. Little did I know the difficulty wasn't actually doing the work...
One way it happens is when you have to split your time between more than one project. Of course, each project expects your attendance at their set of meetings. So working on two projects, you now have 2 sets of meetings. Two projects is still manageable, but any more than that and you're spending a significant amount of time in meetings and overhead.
Well in that situation perhaps dropping the tazer and drawing the gun would be justified.
I mean, you're a cop, there's going to be some element of danger in the job. Don't like it? Don't be a cop. You don't get to just start blowing people away in any situation where the risk to you is non-zero, no matter how small it is.
Besides, a 9mm or a.40 S&W is not even guaranteed to take down a real tough guy charging at you while pumped up on adrenaline and meth without multiple rounds. So does that mean the cops should all carry military-style fully automatic rifles and shoot at anything that moves? You have to draw the line somewhere.
I would argue it's felony murder. Even if he didn't intend for someone to get hurt, nevertheless someone died as a direct result of the crime he committed.
I laughed when I saw the picture of the 747 business jet on the linked site because that's just plain absurd. Then I did a search, and yes, they've sold one (and no, it's not Air Force One in case you are wondering).
The easy, but inefficient way to defeat it would be have a few low priority threads that just spin to keep the CPU at 100%. Since the CPU will be pegged at all times now, the malware will no longer be able to affect the power usage of the computer.
I don't understand this either. I used to donate blood to the Red Cross, and to thank me they spammed my phone endlessly. 1-2 times a day, everyday, and almost always within a few hour window when, of course, I was at work. They would never leave a message either. After a while, I set up an old PC with a modem that could do caller ID. Whenever it saw one of their numbers, it would pick up the line, then immediately hang up. They still didn't get the message. It only ended when I dumped that landline and went to a cell phone with a different number. And I haven't donated blood to them since.
Electricity isn't free, but neither are high-end processors. If you bought a new one, it might pay for itself by the time it too is 10 years old. Less so if the computer is turned off or in sleep mode when you aren't using it.
You can't even use the first number as the generation, as the really high end chips in some generations increment the first number for some reason. For example 38XX and 39XX i7 chips are Sandy Bridge (2nd generation), the 48XX and 49XX i7 chips are Ivy Bridge (3rd generation). Why? Ask Intel, I have no idea.
Given that they are using a chunk of code from ESET which more than likely is not going to be open source, my guess is that this is another one of those binary blobs that Google links in when they build Chrome so chances are you won't find it in the Chromium source.
With that said, some of those binary blobs are freely available so you can find builds of Chromium that have things like Widevine (Chrome's included DRM) baked in, so it could depend on who's build of Chromium you grab.
I've also been running into more and more websites that apparently don't test compatibility with anything other than Chrome, and Chrome is actually somewhat quirky so it can really show. It seems that Chrome really is the new IE6.
The Nissan Frontier is only small relative to the size of other new trucks on the market - historically it would be considered mid-sized. It has grown significantly larger now than it was 15 years ago, when it was more the size of small trucks like the Ford Ranger, Mazda B-Series, Chevy S10, all of which have been discontinued. And of course back in the 70's - 80's you had even smaller compact trucks, like the Ford Courier, Chevy LUV, Dodge Rampage, Subaru Brat, or the VW Rabbit Pickup - none of which have a modern equivalent you can buy (in the US).
It's a bit of a shame that trucks like that are so difficult to sell under the current rules. I wouldn't mind a truck, but the mid-sized trucks now are almost the size of the full-sized trucks from 30 years ago, and full-sized trucks are just gigantic now.
I thought about it, and realized that really the only credible threat to my machines would be something in the browser written in Javascript. All the major browsers have modified their Javascript implementations to basically make that vector impossible, to which I said "good enough".
And that's just the desktops. As the servers go, I couldn't think of any way, assuming everything nothing is broken, that someone could run their own code on the server as to exploit Spectre or Meltdown. Sure, maybe they could use some other exploit to load and run arbitrary code on my servers, but if they could do that then I'd have already lost.
The other obvious solution would be to buy a laptop where the hard drive (or SSD) can easily be removed. My older Thinkpad it's one screw and the HDD + caddy slides right out. So buy a second drive and another caddy, and it would take less than a minute to swap the drives. Bonus of doing that is that your second OS would use your main CPU and all the available ram instead of being something weak like a Raspberry PI stuck inside your laptop.
Though as someone else suggested below, just buy a big drive, partition it, and encrypt the partitions. Set it up so the OS's don't know the key for the other OS's partition, and there's no way for either one to read or contaminate the other - though I suppose a malicious program could still nuke the other encrypted partition if it wanted to.
Zipper merging in practice is a disaster. People in the backup don't leave enough space between them and the car in front of them to do the "zipper" at the merge point. Which means that at the merge point, they need to slow down to create the space for the other car to merge, which inevitably turns into the zipper merge into a "stop and take your turn" merge. And of course, once everyone has to stop, the cars just pile up the merge point and that's how you end up with miles-long backups of stop-and-go traffic that take forever to clear.
This is actually what TFA is about. It may seem to make sense to use multiple routes, just like in the zipper merge, to use multiple lanes. But if you create a choke point where those two routes come back together, you could end up slowing down traffic on both routes more than if everyone just stayed on the main route.
AMD had the best CPU back then, and it was cheaper too. The problem is to actually use the Athlon you were stuck with garbage like the VIA's KT133 chipset. It's no wonder the OEM's fled in terror to boring but safe choices like Intel's 440BX chipset.
Slashdot Mirror
I would hardly credit Apple for that, given that they are pretty much non-existent in the sub-$300 market. I would have to give the credit to Google with Android and Chromebooks. Though really, it's just that hardware got cheap enough and still good enough that a computer that cheap is actually viable. Which means, of course, that Microsoft is very active in the sub-$300 market now. Apple? Not so much.
The default in Windows now when it BSOD's is to reboot. Of course, if it just boots up into another BSOD, that's how you get the reboot loops. If it's more of the random fluke BSOD, you just come back and see your computer restarted (oh, must have been Windows Update...again....). That's how people claim that they've not seen a BSOD in years. You can turn that nonsense off if you want, though I wouldn't trust Windows 10 to not ignore it and do whatever it wants regardless of the setting.
My state has a similar, but more reasonable law, that you can't leave your car running unattended with the keys in the ignition. So the solution is one of those remote starters that lets the car run without the keys in it, and here that is legal.
Even if the keys are in it, you don't actually have to have your ass in the driver's seat, so long as the car is not unattended. So if you're scraping the ice off or are otherwise nearby you're not breaking the law even if there's no one actually in the car.
Keep in mind that your dollar store alkalines will likely not last nearly as long as a decent set of alkalines. Generally the dollars per run time ratio still favors the cheap batteries if don't mind having to swap them out more often, but you're getting what you paid for.
And if you're going to be lazy and not check up on the batteries in the flashlights in your emergency kit, I'd recommend getting Lithium batteries (not Lithium-ion, these are not rechargeable). They are more expensive, but they have a longer shelf-life, and won't leak like alkaline batteries. They'll also last longer if you need to use them.
I've found the longer the paper takes to read generally means the less worthwhile the paper is. I've read some papers in fields I'm familiar with, and when I get done I still don't know WTF they're talking about. So I start breaking it down, slashing through all the jargon and word soup, working through the math myself, and finally when I understand what they're actually saying.... I realize they really don't have much. A bunch of dense language, big words, and technical terms thrown about with some fancy-looking charts and it all looks very impressive, but in reality what they've done is pretty minor and not that novel. They know it too, and know it's not good for a multi-page paper, hence a massive amount of filler - most of which is just reiterating basic things that everyone already knows once you've managed to hack through it.
On the other side, go pick up one of the famous, ground-breaking papers in the field that everyone knows about and cites. In comparison, you'll find those papers easy to read - they are clearly written, using simple language, and easy to follow and understand (maybe longer to digest though). There's really no reason to have to dress it all up, as the science stands on its own.
Well that explains some of the old, obsolete, inefficient systems I've seen still chugging along. "It's too much trouble to replace it" they say. I'm no expect on HVAC, but it didn't look all that difficult to replace it. Little did I know the difficulty wasn't actually doing the work...
One way it happens is when you have to split your time between more than one project. Of course, each project expects your attendance at their set of meetings. So working on two projects, you now have 2 sets of meetings. Two projects is still manageable, but any more than that and you're spending a significant amount of time in meetings and overhead.
Well in that situation perhaps dropping the tazer and drawing the gun would be justified.
I mean, you're a cop, there's going to be some element of danger in the job. Don't like it? Don't be a cop. You don't get to just start blowing people away in any situation where the risk to you is non-zero, no matter how small it is.
Besides, a 9mm or a .40 S&W is not even guaranteed to take down a real tough guy charging at you while pumped up on adrenaline and meth without multiple rounds. So does that mean the cops should all carry military-style fully automatic rifles and shoot at anything that moves? You have to draw the line somewhere.
I would argue it's felony murder. Even if he didn't intend for someone to get hurt, nevertheless someone died as a direct result of the crime he committed.
I laughed when I saw the picture of the 747 business jet on the linked site because that's just plain absurd. Then I did a search, and yes, they've sold one (and no, it's not Air Force One in case you are wondering).
Go big or go home, I guess.
Of course he would. That's why the best thing he could do is just shut up and not say anything until the NTSB finishes their investigation.
The easy, but inefficient way to defeat it would be have a few low priority threads that just spin to keep the CPU at 100%. Since the CPU will be pegged at all times now, the malware will no longer be able to affect the power usage of the computer.
I don't understand this either. I used to donate blood to the Red Cross, and to thank me they spammed my phone endlessly. 1-2 times a day, everyday, and almost always within a few hour window when, of course, I was at work. They would never leave a message either. After a while, I set up an old PC with a modem that could do caller ID. Whenever it saw one of their numbers, it would pick up the line, then immediately hang up. They still didn't get the message. It only ended when I dumped that landline and went to a cell phone with a different number. And I haven't donated blood to them since.
That's true! I heard you've only managed about 50 miles on that '93 Escort since new :)
Electricity isn't free, but neither are high-end processors. If you bought a new one, it might pay for itself by the time it too is 10 years old. Less so if the computer is turned off or in sleep mode when you aren't using it.
Sunshine wasn't that great if you ask me. It did start out with a lot of promise, but it then turned into a generic monster on the loose horror movie.
You can't even use the first number as the generation, as the really high end chips in some generations increment the first number for some reason. For example 38XX and 39XX i7 chips are Sandy Bridge (2nd generation), the 48XX and 49XX i7 chips are Ivy Bridge (3rd generation). Why? Ask Intel, I have no idea.
Given that they are using a chunk of code from ESET which more than likely is not going to be open source, my guess is that this is another one of those binary blobs that Google links in when they build Chrome so chances are you won't find it in the Chromium source.
With that said, some of those binary blobs are freely available so you can find builds of Chromium that have things like Widevine (Chrome's included DRM) baked in, so it could depend on who's build of Chromium you grab.
I've also been running into more and more websites that apparently don't test compatibility with anything other than Chrome, and Chrome is actually somewhat quirky so it can really show. It seems that Chrome really is the new IE6.
The Nissan Frontier is only small relative to the size of other new trucks on the market - historically it would be considered mid-sized. It has grown significantly larger now than it was 15 years ago, when it was more the size of small trucks like the Ford Ranger, Mazda B-Series, Chevy S10, all of which have been discontinued. And of course back in the 70's - 80's you had even smaller compact trucks, like the Ford Courier, Chevy LUV, Dodge Rampage, Subaru Brat, or the VW Rabbit Pickup - none of which have a modern equivalent you can buy (in the US).
It's a bit of a shame that trucks like that are so difficult to sell under the current rules. I wouldn't mind a truck, but the mid-sized trucks now are almost the size of the full-sized trucks from 30 years ago, and full-sized trucks are just gigantic now.
I thought about it, and realized that really the only credible threat to my machines would be something in the browser written in Javascript. All the major browsers have modified their Javascript implementations to basically make that vector impossible, to which I said "good enough".
And that's just the desktops. As the servers go, I couldn't think of any way, assuming everything nothing is broken, that someone could run their own code on the server as to exploit Spectre or Meltdown. Sure, maybe they could use some other exploit to load and run arbitrary code on my servers, but if they could do that then I'd have already lost.
The other obvious solution would be to buy a laptop where the hard drive (or SSD) can easily be removed. My older Thinkpad it's one screw and the HDD + caddy slides right out. So buy a second drive and another caddy, and it would take less than a minute to swap the drives. Bonus of doing that is that your second OS would use your main CPU and all the available ram instead of being something weak like a Raspberry PI stuck inside your laptop.
Though as someone else suggested below, just buy a big drive, partition it, and encrypt the partitions. Set it up so the OS's don't know the key for the other OS's partition, and there's no way for either one to read or contaminate the other - though I suppose a malicious program could still nuke the other encrypted partition if it wanted to.
Zipper merging in practice is a disaster. People in the backup don't leave enough space between them and the car in front of them to do the "zipper" at the merge point. Which means that at the merge point, they need to slow down to create the space for the other car to merge, which inevitably turns into the zipper merge into a "stop and take your turn" merge. And of course, once everyone has to stop, the cars just pile up the merge point and that's how you end up with miles-long backups of stop-and-go traffic that take forever to clear.
This is actually what TFA is about. It may seem to make sense to use multiple routes, just like in the zipper merge, to use multiple lanes. But if you create a choke point where those two routes come back together, you could end up slowing down traffic on both routes more than if everyone just stayed on the main route.
AMD had the best CPU back then, and it was cheaper too. The problem is to actually use the Athlon you were stuck with garbage like the VIA's KT133 chipset. It's no wonder the OEM's fled in terror to boring but safe choices like Intel's 440BX chipset.