TRIM is pointless as you need a consistent output/throughput in the worst case scenario Also, in most cases, your workload will be optimized against the hardware so you won't be doing any such small writes/updates where TRIM becomes useful (stripe size on an FS that requires frequent updates is already 4k or larger).
Most people simply do not know whether or not IOPS are important but they generally are. Given that spinning drives peak out at ~100IOPS, SSD's are generally a better investment (also in power and space requirements) than multiple drives (or drive arrays). You also don't try to run any system without at least having RAID1 and regular snapshots/backups, that way, your SSD's can fail every month, you just ship them back to manufacturer.
SSD's are never a waste of money IMHO unless they are literally unused. They can always be used for something, heck I have paid for the very first Intel 32GB SLC SSD's. Still being re-used in a small backup server systems.
I've also had HDD's failing in first 3 months of use, many more than SSD's. SLC SSD or RAM SSD's are necessary though to maintain throughput on modern systems. No way spinning rust is keeping up with a pair of SSD's, heck even USB Flash drives perform better as a boot drive than HDD's. HDD's only make sense if you need really large amounts of storage for cheap and even then you're still inserting SSD's and RAM as caches and accelerators.
The cost is there, it is just shifted to the local cities and villages. The cost comes in damage from potholes and road damages which the locality is liable for. Also, there is a cost of more wear and tear on locals' vehicles including first responder vehicles.
There is a law against modifying the software you own (at least in the US and the EU), it's called the DMCA and it's European derivatives. The only exception the DMCA allows is for 'interoperability' where no other programs do the same things. With the availability of open source solutions, it's just not worth fixing old crap when you can just fix open source systems without legal issues.
You seem to have failed basic physics and chemistry.
As I said: Oil is not flammable, it's combustible, big difference. No oxygen means no flame, regardless of the fuel Datacenters remove the oxygen in case of fire, the fire suppression system uses an inert gas to displace oxygen.
You do not need permits to handle oils in these situations. You are not 'storing' oil.
With most residential providers you have contractually agreed not to run a mail server. Also, you won't have a fixed IP so a receiving mail server is kind of useless. Use a commercial account/provider and you will most likely be able to obtain a fixed IP outside of the blacklisting that comes with residential IP's.
The same goes for drug dealers in the US. Local drug dealers earn money that's stratospheric by local standards which is very profitable until you get caught.
What will happen is this will simply create a submarket for 'real' horn poachers that establish their 'confirmed kill', perhaps via video. Horns will still be harvested (until they run out of rhino's) but it will be harder to catch the real with all the fakes around and everyone will be claiming theirs is fake to get away from prosecution.
It's going to become a situation like you see in the heist movies where everyone is wearing the same hat/suit as the actual thief, but the thief is the only one with the original product but gets away due to the overwhelming amount of fakes.
I think he meant native multithreading and sorry to say, it ain't coming. JS was designed to be a single threaded, event driven language. It will never be multithreaded as it would break events and that is a problem with all event based languages/programs. You're stuck with the speed of a single core, fine for general purpose processors where you just throw more power at the problem (110W/CPU for modern systems) but really bad on low frequency/power multicore systems.
Most likely they assumed, as most companies these days erroneously do, that their entire internal network is 'secure' and thus does not need encryption. Besides these dedicated devices, most corporate networks don't protect much against visiting and malware infested laptops. Even if they are aware of the chance of someone bringing a virus from home, they rather turn to device 'access controls' and trusting the device to self-report over securing the internal systems.
As long as the oil remains contained within the unit, there is not a problem. Most oils aren't immediately flammable either. By the time most oils have the time and temperature to catch a flame, the sprinkler systems should have activated.
Sparks in oil? You could soak the thing in diesel fuel or even gasoline, as long as it is fully submerged and contained there is not enough oxygen to ignite it and sparks do not develop in an oil based substance (again, you need oxygen to get a flame).
I agree it shouldn't be hazardous but "toxic" does not always mean it's a hazard. There are berries that are toxic to humans yet totally fine in nature. Also, there are other containment methods and cleansing procedures similar to how underground gas station tanks operate.
Non-flammable, non-toxic and cheap aren't really necessary for these things. Nobody is going to light a flame, drink it and the cost is usually offset by the savings.
But that is the case with any security project. You cannot keep the stupid from doing stupid things and they're the weakest link. Only by removing THEM do you remove the threats to any security system.
If your private keys are compromised, would you keep using them? Some in this world think it would be acceptable simply because the cost of replacement ($25-150 for a new certificate). Eventually the PHB's take over a perfectly working project and cause it to be declared insecure.
My experience is these newfangled API's perform poorly across the board.
For example, LocalStorage was great, it's fast, it's easy but is hamstrung by it's limits. IndexedDB is another beast entirely with severe performance and implementation issues and total non-resemblance of what an actual database interface should be.
I find Firefox to be slow and bloated. Using 500MB of RAM for 2-3 tabs is ridiculous. Perhaps the plugins are the reason but Safari + AdBlock + Click2Plugin is very, very responsive.
Sites breaking is that site's issue, not a Safari issue and avoiding the site or fixing the site is usually the correct response. You can probably replicate the same issue on Chrome and other WebKit browsers.
I like Safari's developer functions, Mozilla even copied them (poorly). For instance Safari allows you to see what actually happens on any site you just visited. Mozilla changes the way 304's and similar caches work in dev mode causing issues to disappear in dev mode.
This is Slashdot, not CNN. I am a geek/nerd with 2 decades worth of experience in computer programming and currently working close with people in the field of evolutionary biology. If anything, I'm excited that a computer sees what the religious right doesn't.
Perhaps they meant that the data is available but it's origin isn't. So you can safely publish your customer data for analysis because (in theory) the data source is anonymized.
Some Engima messages have thus far been undecrypted. Enigma was an awesome encryption tool and in theory (especially at the time) unhackable. The issue came in, as most/all encryption systems are vulnerable to the famous PEBKAC. A device was stolen/recovered by the allies allowing for the discovery of it's mechanism which was based around a one-time-pad rotating ciphers every so often (it would be similar to getting your hands on the source code of the algorithm of more modern encryptions and the rotating key was a frequently changing 'private key'). Later on, code books were stolen/recovered as well which were not/improperly destructed (similar to getting your hands on the set of private keys). Substantiating those compromises were the fact that some officers used the same key over and over opening the door to linguistic analysis. Later on, versions of Enigma machines had rotators removed in order to cut costs.
The problems wasn't with the tool but with the PHB's in charge (much like current encryption systems).
It's impressive that it can even recognize and classify things as such. Great apes and humans share about 99% of our DNA, any 'alien' entity would classify us amongst the apes.
The fact that black people are black and thus have a closer resemblance to the generally 'darker' great apes is not racist because an algorithm that is not programmed to have biases cannot be racist. It's just peoples interpretation of the facts that makes things 'racist'. Superficially, black people and apes look mathematically more alike than white people and apes. If the thing was trained on albino apes (which do exist), white people would be considered apes AND NOBODY WOULD THINK IT WAS RACIST.
Depends, they could easily have made 6000 Perl one-liners.
Lines of code is really a bad metric. If you have 6000 lines written by a team of bad programmer (which is typical for startups) vs 6,000,000 by a set of really good programmers makes a huge difference.
But how many US pilots have been in an actual dogfight since, say WWII. Most wars these days are no longer in the air, no large nations are fighting each other and ISIS doesn't have the capacity to fly an F16-like aircraft. Even during the Cold War, the most action was recon missions in enemy airspace which went largely unnoticed.
Sure, the F35 is a boondoggle but are these jets really necessary? The F16 seems to be holding up fine and the Russians, the only non-allied force with similar capabilities is flying mostly rust that is older than the F16 program.
There is very little you can do with it. The stuff is carcinogenic, dangerous and mostly plastic. In some states it's illegal to just dump them in the general waste.
Slashdot Mirror
TRIM is pointless as you need a consistent output/throughput in the worst case scenario Also, in most cases, your workload will be optimized against the hardware so you won't be doing any such small writes/updates where TRIM becomes useful (stripe size on an FS that requires frequent updates is already 4k or larger).
Most people simply do not know whether or not IOPS are important but they generally are. Given that spinning drives peak out at ~100IOPS, SSD's are generally a better investment (also in power and space requirements) than multiple drives (or drive arrays). You also don't try to run any system without at least having RAID1 and regular snapshots/backups, that way, your SSD's can fail every month, you just ship them back to manufacturer.
SSD's are never a waste of money IMHO unless they are literally unused. They can always be used for something, heck I have paid for the very first Intel 32GB SLC SSD's. Still being re-used in a small backup server systems.
I've also had HDD's failing in first 3 months of use, many more than SSD's. SLC SSD or RAM SSD's are necessary though to maintain throughput on modern systems. No way spinning rust is keeping up with a pair of SSD's, heck even USB Flash drives perform better as a boot drive than HDD's. HDD's only make sense if you need really large amounts of storage for cheap and even then you're still inserting SSD's and RAM as caches and accelerators.
The cost is there, it is just shifted to the local cities and villages. The cost comes in damage from potholes and road damages which the locality is liable for. Also, there is a cost of more wear and tear on locals' vehicles including first responder vehicles.
There is a law against modifying the software you own (at least in the US and the EU), it's called the DMCA and it's European derivatives. The only exception the DMCA allows is for 'interoperability' where no other programs do the same things. With the availability of open source solutions, it's just not worth fixing old crap when you can just fix open source systems without legal issues.
You seem to have failed basic physics and chemistry.
As I said:
Oil is not flammable, it's combustible, big difference.
No oxygen means no flame, regardless of the fuel
Datacenters remove the oxygen in case of fire, the fire suppression system uses an inert gas to displace oxygen.
You do not need permits to handle oils in these situations. You are not 'storing' oil.
With most residential providers you have contractually agreed not to run a mail server. Also, you won't have a fixed IP so a receiving mail server is kind of useless. Use a commercial account/provider and you will most likely be able to obtain a fixed IP outside of the blacklisting that comes with residential IP's.
The same goes for drug dealers in the US. Local drug dealers earn money that's stratospheric by local standards which is very profitable until you get caught.
What will happen is this will simply create a submarket for 'real' horn poachers that establish their 'confirmed kill', perhaps via video. Horns will still be harvested (until they run out of rhino's) but it will be harder to catch the real with all the fakes around and everyone will be claiming theirs is fake to get away from prosecution.
It's going to become a situation like you see in the heist movies where everyone is wearing the same hat/suit as the actual thief, but the thief is the only one with the original product but gets away due to the overwhelming amount of fakes.
I think he meant native multithreading and sorry to say, it ain't coming. JS was designed to be a single threaded, event driven language. It will never be multithreaded as it would break events and that is a problem with all event based languages/programs. You're stuck with the speed of a single core, fine for general purpose processors where you just throw more power at the problem (110W/CPU for modern systems) but really bad on low frequency/power multicore systems.
Water sprinklers in datacenters? You really have no idea about data centers do you?
Most likely they assumed, as most companies these days erroneously do, that their entire internal network is 'secure' and thus does not need encryption. Besides these dedicated devices, most corporate networks don't protect much against visiting and malware infested laptops. Even if they are aware of the chance of someone bringing a virus from home, they rather turn to device 'access controls' and trusting the device to self-report over securing the internal systems.
Crunch bitcoins for the locals?
As long as the oil remains contained within the unit, there is not a problem. Most oils aren't immediately flammable either. By the time most oils have the time and temperature to catch a flame, the sprinkler systems should have activated.
Sparks in oil? You could soak the thing in diesel fuel or even gasoline, as long as it is fully submerged and contained there is not enough oxygen to ignite it and sparks do not develop in an oil based substance (again, you need oxygen to get a flame).
I agree it shouldn't be hazardous but "toxic" does not always mean it's a hazard. There are berries that are toxic to humans yet totally fine in nature. Also, there are other containment methods and cleansing procedures similar to how underground gas station tanks operate.
Non-flammable, non-toxic and cheap aren't really necessary for these things. Nobody is going to light a flame, drink it and the cost is usually offset by the savings.
But that is the case with any security project. You cannot keep the stupid from doing stupid things and they're the weakest link. Only by removing THEM do you remove the threats to any security system.
If your private keys are compromised, would you keep using them? Some in this world think it would be acceptable simply because the cost of replacement ($25-150 for a new certificate). Eventually the PHB's take over a perfectly working project and cause it to be declared insecure.
My experience is these newfangled API's perform poorly across the board.
For example, LocalStorage was great, it's fast, it's easy but is hamstrung by it's limits. IndexedDB is another beast entirely with severe performance and implementation issues and total non-resemblance of what an actual database interface should be.
I find Firefox to be slow and bloated. Using 500MB of RAM for 2-3 tabs is ridiculous. Perhaps the plugins are the reason but Safari + AdBlock + Click2Plugin is very, very responsive.
Sites breaking is that site's issue, not a Safari issue and avoiding the site or fixing the site is usually the correct response. You can probably replicate the same issue on Chrome and other WebKit browsers.
I like Safari's developer functions, Mozilla even copied them (poorly). For instance Safari allows you to see what actually happens on any site you just visited. Mozilla changes the way 304's and similar caches work in dev mode causing issues to disappear in dev mode.
This is Slashdot, not CNN. I am a geek/nerd with 2 decades worth of experience in computer programming and currently working close with people in the field of evolutionary biology. If anything, I'm excited that a computer sees what the religious right doesn't.
Perhaps they meant that the data is available but it's origin isn't. So you can safely publish your customer data for analysis because (in theory) the data source is anonymized.
Homomorphic encryption is a pipe dream thus far.
Some Engima messages have thus far been undecrypted. Enigma was an awesome encryption tool and in theory (especially at the time) unhackable. The issue came in, as most/all encryption systems are vulnerable to the famous PEBKAC. A device was stolen/recovered by the allies allowing for the discovery of it's mechanism which was based around a one-time-pad rotating ciphers every so often (it would be similar to getting your hands on the source code of the algorithm of more modern encryptions and the rotating key was a frequently changing 'private key'). Later on, code books were stolen/recovered as well which were not/improperly destructed (similar to getting your hands on the set of private keys). Substantiating those compromises were the fact that some officers used the same key over and over opening the door to linguistic analysis. Later on, versions of Enigma machines had rotators removed in order to cut costs.
The problems wasn't with the tool but with the PHB's in charge (much like current encryption systems).
It's impressive that it can even recognize and classify things as such. Great apes and humans share about 99% of our DNA, any 'alien' entity would classify us amongst the apes.
The fact that black people are black and thus have a closer resemblance to the generally 'darker' great apes is not racist because an algorithm that is not programmed to have biases cannot be racist. It's just peoples interpretation of the facts that makes things 'racist'. Superficially, black people and apes look mathematically more alike than white people and apes. If the thing was trained on albino apes (which do exist), white people would be considered apes AND NOBODY WOULD THINK IT WAS RACIST.
Depends, they could easily have made 6000 Perl one-liners.
Lines of code is really a bad metric. If you have 6000 lines written by a team of bad programmer (which is typical for startups) vs 6,000,000 by a set of really good programmers makes a huge difference.
But how many US pilots have been in an actual dogfight since, say WWII. Most wars these days are no longer in the air, no large nations are fighting each other and ISIS doesn't have the capacity to fly an F16-like aircraft. Even during the Cold War, the most action was recon missions in enemy airspace which went largely unnoticed.
Sure, the F35 is a boondoggle but are these jets really necessary? The F16 seems to be holding up fine and the Russians, the only non-allied force with similar capabilities is flying mostly rust that is older than the F16 program.
There is very little you can do with it. The stuff is carcinogenic, dangerous and mostly plastic. In some states it's illegal to just dump them in the general waste.
In the US, you need not register a name for it to be trademarked necessarily. You just have to have it used.