> OS X may be stable but it has a short shelf life. You might find your hardware unsupported in 3 or 4 years
I don't know if that might be true of some iOS mobile devices or where that FUD comes from, but my six year old Mac from 2008 is going strong and I just installed an OS update. My employer wanted to replace it, but it's a quad core with16GB of RAM - more than sufficient for today's software. Bureaucracy said the budget had to be spent on computer equipment, so we upgraded one of the four drives to an SSD. The old RAID was fast enough, but I guess the SSD will save a few minutes per week. Later we used the budget to add a Macbook Pro. It will probably make sense to upgrade my desktop in 2015 or 2016, when it's seven or eight years old.
That's the perspective of a guy who isn't even paying for the upgrade. It's free to me, but if I can run the latest OS and multiple IDEs and browsers open on four monitors with no noticeable lag, why would I replace it?
> First got into it... because Linux was totally stable
If stable is your top priority, Fedora is approximately the worst possible choice. Fedora is essentially Red Hat Beta. If you want stable, the devel / beta branch is not for you. You'll probably be much happier with Red Hat or its twin, CentOS.
Also, you mentioned that you did an "upgrade" to Debian Unstable. You didn't mention any _reason_ for doing that. If stability is a top priority for you, don't upgrade just because you can, don't fix it if it aint broke.
Mac OSX may indeed be a good choice for you also. It is certified Unix and if you use the commondand line in Linux you'll find that day-to-day tasks are the same on a Mac. System internals are different of course, but bash, sed, awk, grep, and vim work just like they do on Linux.
The total cost of driving, including wear and tear on car, is about 54 cents per mile, or $2.70 for a five mile trip. A taxi charges $15. There's a lot of money to be made with a 555% markup.
> please stop making up numbers and posting them all over this story
Since I said "billions" and you replied with a link to where someone posted $73 billion, I can only guess that English isn't your native language and you didn't actually mean to say what you said. I suppose the alternative is that you're so completely closed to the facts that in order to maintain your faith in Comedy Central as your policy adviser you've convinced yourself that $73 billion isn't "billions". That would be sad.
FYI, citing something someone posted on Wiki is like us8ng someone's Slashdot post as your source. The authoritative source for energy data is EIA.
> We have myriad energy solutions now... and in fact most are at parity with the cost of nuclear power (if you're honest about it, and include government R&D and subsidies in the cost).
You sure you want to include the billions in taxpayer subsidies it takes to get 1% of our energy from solar? I don't think Comedy Central instructed you to point out that solar-electric is 4.8X times as expensive during the daytime, and far more costly at night.
> If I'm wrong, please do show me this mass D gerrymandering that's going on.... Or did go on.
Section 2 of the Voting Rights Act _requires_ that districts be gerrymandered such that demographic groups which are a _minority_ of the population make up a _majority_ of the voters in those districts. When states fail to gerrymander for democrats ^H^H^H^H^H^H^H^H^H^H black people, the federal government intervenes and forces gerrymandered districts. This is not new.
This cache and especially native command queuing (ncq), the drive ALREADY has to pay attention to the sequence in which operations are carried out. A read requested first, then a write, might already be done in reverse order, requiring a check that the sector read isn't the same one written.
I don't see any reason reading and writing two sectors at a time makes any fundamental difference.
Somewhat off topic, but while we're talking about drives:
We put millions of transistors on a chip. Millions of photodetectors (pixels) in your phone's camera, a million pixels on it's display. Yet our hard drives have ONE sensor that swings back and forth on a mechanical arm?!?! Why the heck isn't the read/write head a strip, with a few thousand "pixels", so it can read any sector as the platter spins beneath it, without swinging the heads back and forth? That would eliminate seek time.
If needed, you could move the strip back and forth a thousandth of an inch to align a head with one of it's four tracks. That'd be a lot quicker that moving the head a full inch as they do now.
So presumably there is some good reason that can't be done. Still, an additional arm exactly like the existing one, but on the opposite side of the platter, would cut rotational latency in half and increase throughout up to 100%. Seems like an easy win.
Although I tend to agree with the general consensus that RFID or even QR codes would be a simpler way to identify (not authenticate) people, there is one important nuance being missed in all the criticism of biometric.
In the most common use cases for biometrics, you're attempting to distinguish this one person vs the other 5 billion people in the world. That's hard. This particular use case is much simpler - we're judt asking it to distinguish betweenthe 50 or so people who work in this clean room. In other words, we know it's one of these 50 people, which of them is it? That's a much easier question, so high accuracy should be easy to achieve with the right settings.
Indeed, this approach is interesting to me because I had to get out of RC planes due to the cost of crashing, especially while I was first learning to fly. Anything that allows one to recover from a crash with just a few dollars and a few minutes is a win.
This approach reminds me of a popular design that is also inexpensive, but this new design has two advantages. First, it positions the motor and prop in the center, where it is protected from damage. Second, they mount the electrical components on a subassembly board, allowing the entire assembly to be moved to a new body as one unit, thereby saving time.
> You'll be hard pressed to find a drive that isn't guaranteed for 5 years of writes at the maximum throughput the drive can handle.
Hah! I wish. The most popular line of SSDs is the Samsung 840 series. In commercial usage, the 840 Pro is warranted for 73 TB written. That's 3 DAYS at maximum throughput.
The 850 series is warranted for twice as much - 150 TB, or one week at maximum throughput.
That near-instant access also allows other uses. For example, when a small business client's web site is defaced or simply broken, I can run rsync --dry-run and tell them exactly which files have changed - in minutes, while they're still on the phone. I can restore the damaged files just as quickly.
Tape has it's place, but online offsite backups, done right, have some very significant advantages too.
> Would you buy those 15k's new today? What usage pattern would favor 15k's vs ssd's?
Anything that keeps the drive fairly busy writing. Our particular application is backups. Our backup servers write pretty much constantly. SSDs might last a couple of years, they might not.
DVRs for security cameras are another example application that writes pretty much constantly, so again HDDs are a better fit.
On the other hand, SSDs are a much better fit for most laptops, where you want fast boot and physical durability. Each is the right tool for certain applications.
I believe quotes require that exact phrase, in order. Traditionally, that is useful for multiple-word phrases. Since Google will by default include synonyms, quotes (exact phrase) can also be useful to avoid synonyms with even a single word quoted.
The plus sign appears to still require a specific word, as it always has. This is most useful when you want to search for what appears to be an unimportant word like "the" or you have many search terms and some terms are most important.
That idea kind of wrong, too. For maintenance tasks, more than once I've sat down and fixed code without ever having seen the language before, sometimes without bothering to check which language it is. A decent programmer isn't going to have to much trouble maintaining any reasonable language. For example, a fence post error is a fence post error in any language, and the fix is always the same - use the value one less.
> China didn't receive any fucking foreign aid from nobody
They actually received billions in foreign aid, cash from the US and subsidized loans from Japan. Aid to China has dropped dramatically over the last 30 years, but USAID is still sending taxpayer money to China to subsidize their green energy industry. At the same time, the US is suing China for illegal subsidies to their solar industry, which violate trade agreements.
So the current standard operating procedure in the US is:
Make a trade deal woth China agreeing to no subsidies to companies engaged in international trade. Borrow money from China. Give that money back to China, on the condition that they use it to subsidize green energy companies. Sue them for subsidizing the green energy companies.
That's what I've always done, grown each business slowly, organically. I've since learned that there are two types of companies that work well - tiny ones that basically provide the owner with a job, and larger ones run by a management team.
What I did for far too long was deal with payroll, unemployment taxes, health insurance, sick leave, etc for two employees. That was a mistake. I should have chosen to either stick with just me and a part time helper, or make the jump to six or eight employees. That jump requires a leap of faith, some investment and a marketing campaign. Not making that leap meant that the business was dependent on one or two long -term employees who occasionally get sick, leave the company, etc.
Be tiny for a while until you figure out what you're doing. That may mean doing your business and a day job for a little while until the business provides you with a full-time income. Once it pays you $60,000 / year, then decide to either stay at that level or increase revenue by 500% quickly. Especially after the changes in the last six years, being an employer takes a lot of time and effort. Make it worthwhile. Do a POC by working it by yourself first, though.
Even if you're going to pick a common word, it is another mistake to pick a word that has a commonly understood meaning specific to that industry. If the had picked any random word, such as Donkey, they could defend a trademark for Donkey programming or Donkey software. Can't quite claim a trademark for assembly programming - assembly programming has been around for decades.
I could do that. Of course I already have both Firefox and Chrome installed anyway, but there is no "install a separate browser for one plugin".
In this particular case, either way is probably fine. For security I tend to think in terms of principles, though. Which is a better principle a) Open a hole, and put a bandaid over the hole b) Don't open a hole
Slashdot Mirror
> OS X may be stable but it has a short shelf life. You might find your hardware unsupported in 3 or 4 years
I don't know if that might be true of some iOS mobile devices or where that FUD comes from, but my six year old Mac from 2008 is going strong and I just installed an OS update. My employer wanted to replace it, but it's a quad core with16GB of RAM - more than sufficient for today's software. Bureaucracy said the budget had to be spent on computer equipment, so we upgraded one of the four drives to an SSD. The old RAID was fast enough, but I guess the SSD will save a few minutes per week. Later we used the budget to add a Macbook Pro. It will probably make sense to upgrade my desktop in 2015 or 2016, when it's seven or eight years old.
That's the perspective of a guy who isn't even paying for the upgrade. It's free to me, but if I can run the latest OS and multiple IDEs and browsers open on four monitors with no noticeable lag, why would I replace it?
> First got into it ... because Linux was totally stable
If stable is your top priority, Fedora is approximately the worst possible choice. Fedora is essentially Red Hat Beta. If you want stable, the devel / beta branch is not for you. You'll probably be much happier with Red Hat or its twin, CentOS.
Also, you mentioned that you did an "upgrade" to Debian Unstable. You didn't mention any _reason_ for doing that. If stability is a top priority for you, don't upgrade just because you can, don't fix it if it aint broke.
Mac OSX may indeed be a good choice for you also. It is certified Unix and if you use the commondand line in Linux you'll find that day-to-day tasks are the same on a Mac. System internals are different of course, but bash, sed, awk, grep, and vim work just like they do on Linux.
The total cost of driving, including wear and tear on car, is about 54 cents per mile, or $2.70 for a five mile trip. A taxi charges $15. There's a lot of money to be made with a 555% markup.
> please stop making up numbers and posting them all over this story
Since I said "billions" and you replied with a link to where someone posted $73 billion, I can only guess that English isn't your native language and you didn't actually mean to say what you said. I suppose the alternative is that you're so completely closed to the facts that in order to maintain your faith in Comedy Central as your policy adviser you've convinced yourself that $73 billion isn't "billions". That would be sad.
FYI, citing something someone posted on Wiki is like us8ng someone's Slashdot post as your source. The authoritative source for energy data is EIA.
> We have myriad energy solutions now... and in fact most are at parity with the cost of nuclear power (if you're honest about it, and include government R&D and subsidies in the cost).
You sure you want to include the billions in taxpayer subsidies it takes to get 1% of our energy from solar? I don't think Comedy Central instructed you to point out that solar-electric is 4.8X times as expensive during the daytime, and far more costly at night.
> If I'm wrong, please do show me this mass D gerrymandering that's going on.... Or did go on.
Section 2 of the Voting Rights Act _requires_ that districts be gerrymandered such that demographic groups which are a _minority_ of the population make up a _majority_ of the voters in those districts. When states fail to gerrymander for democrats ^H^H^H^H^H^H^H^H^H^H black people, the federal government intervenes and forces gerrymandered districts. This is not new.
This cache and especially native command queuing (ncq), the drive ALREADY has to pay attention to the sequence in which operations are carried out. A read requested first, then a write, might already be done in reverse order, requiring a check that the sector read isn't the same one written.
I don't see any reason reading and writing two sectors at a time makes any fundamental difference.
Somewhat off topic, but while we're talking about drives:
We put millions of transistors on a chip. Millions of photodetectors (pixels) in your phone's camera, a million pixels on it's display. Yet our hard drives have ONE sensor that swings back and forth on a mechanical arm?!?! Why the heck isn't the read/write head a strip, with a few thousand "pixels", so it can read any sector as the platter spins beneath it, without swinging the heads back and forth? That would eliminate seek time.
If needed, you could move the strip back and forth a thousandth of an inch to align a head with one of it's four tracks. That'd be a lot quicker that moving the head a full inch as they do now.
So presumably there is some good reason that can't be done. Still, an additional arm exactly like the existing one, but on the opposite side of the platter, would cut rotational latency in half and increase throughout up to 100%. Seems like an easy win.
Although I tend to agree with the general consensus that RFID or even QR codes would be a simpler way to identify (not authenticate) people, there is one important nuance being missed in all the criticism of biometric.
In the most common use cases for biometrics, you're attempting to distinguish this one person vs the other 5 billion people in the world. That's hard. This particular use case is much simpler - we're judt asking it to distinguish betweenthe 50 or so people who work in this clean room. In other words, we know it's one of these 50 people, which of them is it? That's a much easier question, so high accuracy should be easy to achieve with the right settings.
Indeed, this approach is interesting to me because I had to get out of RC planes due to the cost of crashing, especially while I was first learning to fly. Anything that allows one to recover from a crash with just a few dollars and a few minutes is a win.
This approach reminds me of a popular design that is also inexpensive, but this new design has two advantages. First, it positions the motor and prop in the center, where it is protected from damage. Second, they mount the electrical components on a subassembly board, allowing the entire assembly to be moved to a new body as one unit, thereby saving time.
> You'll be hard pressed to find a drive that isn't guaranteed for 5 years of writes at the maximum throughput the drive can handle.
Hah! I wish. The most popular line of SSDs is the Samsung 840 series. In commercial usage, the 840 Pro is warranted for 73 TB written. That's 3 DAYS at maximum throughput.
The 850 series is warranted for twice as much - 150 TB, or one week at maximum throughput.
That near-instant access also allows other uses. For example, when a small business client's web site is defaced or simply broken, I can run rsync --dry-run and tell them exactly which files have changed - in minutes, while they're still on the phone. I can restore the damaged files just as quickly.
Tape has it's place, but online offsite backups, done right, have some very significant advantages too.
> Would you buy those 15k's new today? What usage pattern would favor 15k's vs ssd's?
Anything that keeps the drive fairly busy writing. Our particular application is backups. Our backup servers write pretty much constantly. SSDs might last a couple of years, they might not.
DVRs for security cameras are another example application that writes pretty much constantly, so again HDDs are a better fit.
On the other hand, SSDs are a much better fit for most laptops, where you want fast boot and physical durability. Each is the right tool for certain applications.
I believe quotes require that exact phrase, in order. Traditionally, that is useful for multiple-word phrases. Since Google will by default include synonyms, quotes (exact phrase) can also be useful to avoid synonyms with even a single word quoted.
The plus sign appears to still require a specific word, as it always has. This is most useful when you want to search for what appears to be an unimportant word like "the" or you have many search terms and some terms are most important.
That usage is mentioned in the documentation:
https://support.google.com/web...
However, testing out a few queries, it seems to still work the same as it has for 20 years - requiring a term.
That idea kind of wrong, too. For maintenance tasks, more than once I've sat down and fixed code without ever having seen the language before, sometimes without bothering to check which language it is. A decent programmer isn't going to have to much trouble maintaining any reasonable language. For example, a fence post error is a fence post error in any language, and the fix is always the same - use the value one less.
Use a plus sign in front of the yerm you want to require. For example, search for "iteration +R"
> looks absolutely gorgeous, but it's inefficient and not remotely fit for purpose.
Exactly the criteria for winning a design award. You might enjoy The Design of Everyday Things, a great book.
Eh, you can just SAY you'll do something good in a few to get your nobel peace prize. Worked for Obama.
> China didn't receive any fucking foreign aid from nobody
They actually received billions in foreign aid, cash from the US and subsidized loans from Japan. Aid to China has dropped dramatically over the last 30 years, but USAID is still sending taxpayer money to China to subsidize their green energy industry. At the same time, the US is suing China for illegal subsidies to their solar industry, which violate trade agreements.
So the current standard operating procedure in the US is:
Make a trade deal woth China agreeing to no subsidies to companies engaged in international trade.
Borrow money from China.
Give that money back to China, on the condition that they use it to subsidize green energy companies.
Sue them for subsidizing the green energy companies.
That's what I've always done, grown each business slowly, organically. I've since learned that there are two types of companies that work well - tiny ones that basically provide the owner with a job, and larger ones run by a management team.
What I did for far too long was deal with payroll, unemployment taxes, health insurance, sick leave, etc for two employees. That was a mistake. I should have chosen to either stick with just me and a part time helper, or make the jump to six or eight employees. That jump requires a leap of faith, some investment and a marketing campaign. Not making that leap meant that the business was dependent on one or two long -term employees who occasionally get sick, leave the company, etc.
Be tiny for a while until you figure out what you're doing. That may mean doing your business and a day job for a little while until the business provides you with a full-time income. Once it pays you $60,000 / year, then decide to either stay at that level or increase revenue by 500% quickly. Especially after the changes in the last six years, being an employer takes a lot of time and effort. Make it worthwhile. Do a POC by working it by yourself first, though.
onLoad=(yourscrewed)
No script tag there.
How about if I enter scrscriptipt? When you remove "script" from the middle, you end up with - script.
Removing stuff will pretty much never work. You have to htmlencode the output.
> searching the whole site, I was unable to find a single example of a successful "assembly." Not good after "a year of operation."
I saw two of four projects were turning a profit, which would mean paying dividends to contributors.
Even if you're going to pick a common word, it is another mistake to pick a word that has a commonly understood meaning specific to that industry. If the had picked any random word, such as Donkey, they could defend a trademark for Donkey programming or Donkey software. Can't quite claim a trademark for assembly programming - assembly programming has been around for decades.
I could do that. Of course I already have both Firefox and Chrome installed anyway, but there is no "install a separate browser for one plugin".
In this particular case, either way is probably fine. For security I tend to think in terms of principles, though. Which is a better principle
a) Open a hole, and put a bandaid over the hole
b) Don't open a hole
Hint - Windows does a lot of choice a).