What would be the point of putting a Pre on the Verizon network? The whole reason people wanted to put their iPhones on T-Mobile is that they could get it so much cheaper.
But with Sprint being cheaper than Verizon, and Sprint phones being able to roam on Verizon's towers, why would anybody want to move their Pre to Verizon? That'd be paying extra for absolutely no reason.
I'm pretty sure that your taxes aren't keeping drinkypoo out of MN, either.
My taxes didn't buy the lakes, but they certainly help keep them clean. The revenue for the Minnesota State Lotteries all go to the DNR here. And my taxes did pay for the hundreds of miles of bike trails, and hunters and fishers taxes paid for the clean lakes, rivers, parks, and rest of the land.
Of course they do. All I'm saying, is that I have clean lakes (although admittedly, many fewer of them), parks, bike trails, etc. But my tax rate is over 2% lower than yours is.
Think about how nice it would be to have 2% of your income back. Betcha you could buy something really nice with that every year, no?
I lived in Minnesota for 20 years. There are definitely things that I miss, like my friends, and the people, and the weather (yes, the weather), and the lakes; but the high taxes, and the supposed benefits they confer, I do not miss at all.
back in the late 90s i knew a lot of techs that when talking to non-techs would call the computer "the CPU".. i chewed their ass every time for it.
Yeah, I've heard that too. For some reason, it doesn't bother me as much.
Maybe it's because a computer does processing, and so does a CPU. Maybe it's because the acronym almost looks like it could be an abbreviation for ComPUter. Maybe it's because a CPU is part and parcel with a computer (you wouldn't have much of a computer with no CPU, but plenty of computers lack hard drives).
It is a shame when people who should know better use incorrect terms. A PC tech isn't really doing his job if he doesn't educate the end user a bit.
In cree the word for monitor I have found is teevee. The word for computer is hard drive. Who am I to say they are wrong? I just have to make it's still working for them when I am 500 miles away back home.
If you would read the article, you'd notice that his point isn't that different things are called by different words in different languages.
You'd also see that his point wasn't that nontechnical users don't always know the proper names for computer components.
His point is that there is a significant contingent of people who make the specific error of referring to a computer by the name "hard drive". He wonders where huge populations of computer users were taught this specific piece of incorrect terminology.
Personally, I'm a bit curious about that, as well. Why would so many people people refer to a computer as a "hard drive", as opposed to any other component or term. Where are people being taught this?
Well how about this. You, as an IT knowing guy, tell your friend, the retard, that his hard drive is broken. Instead of buying a new hard drive, he buys a new PC, on your recommendation. Language is language and it's important that we are all synced.
What good is it to sync up language, when the guy still has no idea what you are talking about?
This reminds me of a time, a long long time ago, when I went into my college campus's computer store. I told the friendly sales associate that I wanted to look at their hard disks. He handed me a box of 3.5 inch floppies.
However, they've now said that, since this hasn't worked so well in practice, the next version of PostgreSQL WILL include direct, built-in support for basic replication, as well as making sure that heavyweight, third-party replication solutions are still supported.
Well, wake me when it's there. MySQL still gets bashed for its historical lack of transactions, so if Postgres wants credit for something, it can at least implement it. Last I checked, it was supposed to be in 8.4, then it wasn't, then it was supposed to be in 8.5, and if memory serves, it's slipping again.
Either way, I don't think these replication issues are a good enough reason to use MySQL instead. Worst case scenario, there ARE good replication options for PostgreSQL.
So which one of those solutions is:
Easy to configure (as in, no harder than MySQL replication).
Scales linearly (Slony-I scales quadratically, which is why you can't get beyond a few nodes)
Can add a slave node without downtime
Can handle, gracefully, a failure of the master node
Can do master-master replication
Can do statement-based replication and also log-based replication (to support autogenerated keys, rand(), etc.)
MySQL replication supports all of the above, and has for years now. Postgres has some serious catching up to do in this area.
I imagine the intent is for database administrators to issue that command during scheduled maintenance windows. I agree that an "auto vacuum" feature would be preferable for many people. Is "auto vacuum" the major advantage of MySQL over Postgres, then?
Before auto-vacuum, I'd say it was a big advantage. Anything that can cause you to lose all of your data is a big deal, and it used to be that if you didn't vacuum your postgres tables, you'd lose all of your data eventually. MySQL has no such vacuum requirement.
Nowadays, with auto-vacuum, I'd say that's no longer an advantage. And all of the distros that I've worked with have auto-vacuum enabled by default.
Say you need clustering or replication. Then, you would need MySQL because Postgres does not have a serious solution for you.
Slony-I is a dreadful hack that misuses triggers. It's easy to break, difficult to administer, and doesn't scale past a few nodes.
There is no postgres clustering solution that can add a node to the cluster without blocking all reads and writes as the added node syncs up. Sorry, that is not a real solution.
Postgres has definitely realized their error in forcing replication and clustering into third party apps, and they're going to include replication "real soon now" (although it's already slipped versions at least once).
But, sorry. You can't really use Postgres is a high-availability architecture because of the lack of decent replication and cluster support.
It depends on the person. I live alone, and most recipes I find make a whole lot of food that's quite likely won't be able to eat before it goes bad.
Cooking economically for one is difficult, I'll give you that. You put in all that time and expense, only to throw food away.
This can be partially mitigated with a freezer. I can tell you that in my household, we usually make double the food that we'll need, with the intent of freezing half. With dishes that will freeze well, anyhow. We also bring leftovers into work/school for lunches.
A friend of mine insists it's cheaper to eat out. You see, he doesn't consider his time to prepare meals "free." I don't quite get that, but hey, that's not my problem.
I've never bought into the whole "Well, I make $xx/hr, so I won't yyy" argument. Would your friend have been working during the time he otherwise would have been cooking? Is he even paid hourly?
Even if he actually could trade his cooking time for revenue-producing time, would he want to? I tell you what, my billing rate is pretty high, so if I made that argument for every possible activity, all I'd ever do is work. After all, chances are I can find someone who can do just about any given task for cheaper than my time is worth.
By way of example: My billing rate is roughly 10x the billing rate of my babysitter's. Does that mean I should always work and never see my kids?
Seriously? You've never heard of saturated fat and its effect on cholesterol?
Yes, I've heard of these things. But I would rather eat saturated fat than garbage with zero nutritional value.
The Mac & Cheese recipe we use has many vegetables in it (it's Italian Mac & Cheese), so the saturated fat is less of an issue. Generally, you don't want more than 10% of your caloric intake to come from saturated fat, and if you were to analyze our recipe combined with side dishes, you'd probably find it weighs in pretty close to 10% saturated fat.
People who eat Kraft eat it for convenience, and aren't going to be serving it with sides, and may very well eat it multiple times per week. Kraft Mac & Cheese provides roughly zero nutritional value.
Also, have you seen the serving size of Kraft? I can eat a whole damn box, and I am not a large person.
Umm. Those things are more or less available in every state. Well, minus the 13,000 lakes part (and I'm pretty sure your tax dollars didn't buy you those 13,000 lakes).
While I generally agree with you, what home grown mac n cheese recipe do you have that is healthier? All of the recipes we have are very high in fat.
I've never understood this aversion to fat. Humans are evolved to digest fat. If you want to make your mac'n'cheese healthier, don't eat all the reprocessed crap that's in Kraft.
Let us also not forget that many families are either single parent or have two working parents and thus there is a lack of time to prepare all of this delicious nutritious food. At my house we've been trying 20 minute recipes but in general they do end up costing more than just going out to eat.
My household is dual-income, and we have plenty of time to prepare delicious, nutritious food. It's all about time management. Chop veggies the night before. Get a crock pot. It's not that hard.
I'm not sure how your home-cooked food costs more than going out to eat. You must be eating strictly off the dollar menu, or you must buy some seriously expensive ingredients.
One thing you are forgetting is that people that are cheap and would buy prepackaged food or eat at McDonalds will buy cheap ingredients for making food from scratch and you'll be back at square one when it comes to health concerns.
There are plenty of cheap, healthy ingredients. Lentils, chick peas, carrots, peanuts, etc. on the veggie side. And with a crock pot, you can buy cheaper cuts of meat--you cook it all day, so it comes out great.
I think the bigger problem is they don't teach home economics in school anymore. The byproduct of all this political correctness is that nobody knows how to run a household and put healthy food on the table.
If a peace officer puts handcuffs on you, you're under arrest, period.
Nope. You are merely detained.
I didn't read about the arraignment. That's what matters, because the arrestee either was accused of a crime or has it in writing that the police arrested him without any cause, which is assault.
If he was arrested, the officers would have informed him of the charge, and he would have been arraigned on those charges.
Actually, the standard for police to detain someone is "reasonable suspicion" and the standard to arrest someone is "probable cause".
It sounds like the blogger was detained and not arrested, so the officer would have had to have had "reasonable suspicion" based on "specific and articulable facts". The specific and articulable fact would be him recording the inner-workings of the ATM, and activities of the ATM personnel.
So the cops detained him, determined that there was not "probable cause" to arrest him, and let him go.
So what, exactly, is the problem here?
Also, realize that you only have one side of the story. I doubt the blogger posted anything that would make him look like anything other than an innocent, but the cops may have a different side of the story.
Either way, I can't figure out why people believe the cops acted improperly.
The US is roughly the size of Australia, so as you can imagine, you can't really generalize about where the good jobs are, or where people live, etc. It really depends on the locality.
Most high-paying jobs tend to be in the city proper in any given metro area, but that is not necessarily always true. Take New York, for example. There are a ton of good jobs in the city, but you can find good jobs in the commuter suburbs, too (e.g. Stamford, CT has a lot of financial firms (UBS, Swiss Re, etc.)).
Or take Washington DC, for example. Lots of great jobs in DC, but you have Amazon.com, AOL, and a few huge NOCs in Dulles, Virginia (where?).
So I don't think you can really generalize about how it is here. There are definitely rich people in the city centers (who can afford to send their kids to private schools). There are rich people in the suburbs, too. And there are poor people in both places.
Out in the middle of nowhere, however, you'll mostly find poor people.
IANAL, but I Am A Landlord, so I deal with federal and state anti-discrimination laws.
Forbidding the use of an information source because that source might contain information that a hiring manager might use to practice illegal discrimination, in my opinion, is taking too defensive a stance.
By the bank's logic, why not forbid resumes? I mean, what if the applicant stated that he or she served on the board of a religious charity?
And why not forbid interviews, while we're at it? I mean, what if a candidate shows up in some sort of religious dress?
Bottom line: Either the information source is valuable, or it is not. If it is, use it. But you still need to educate your hiring managers what criteria are legal and illegal to use. If your managers can't handle the task, then maybe you have a different HR problem on your hands.
So what do the people running the cloud do at Christmas if most of the people they're supporting need 10 times the load?
The cloud provider is going to have a heterogeneous set of customers.
Perhaps your e-commerce company needs to scale up for Christmas, while my monthly payment processor needs to scale up on the first day of every month, and some other customer has to scale up on Mondays to deal with processing that queued up over the weekend, and some other customer scales up at night for nightly processing, and some other customer needs to scale up during business hours, and...
In other words, demand gets smoothed out a bit for the cloud provider by having a diversity of different customers with a diversity of different requirements.
Slashdot Mirror
What would be the point of putting a Pre on the Verizon network? The whole reason people wanted to put their iPhones on T-Mobile is that they could get it so much cheaper.
But with Sprint being cheaper than Verizon, and Sprint phones being able to roam on Verizon's towers, why would anybody want to move their Pre to Verizon? That'd be paying extra for absolutely no reason.
I'm pretty sure that your taxes aren't keeping drinkypoo out of MN, either.
My taxes didn't buy the lakes, but they certainly help keep them clean. The revenue for the Minnesota State Lotteries all go to the DNR here. And my taxes did pay for the hundreds of miles of bike trails, and hunters and fishers taxes paid for the clean lakes, rivers, parks, and rest of the land.
Of course they do. All I'm saying, is that I have clean lakes (although admittedly, many fewer of them), parks, bike trails, etc. But my tax rate is over 2% lower than yours is.
Think about how nice it would be to have 2% of your income back. Betcha you could buy something really nice with that every year, no?
I lived in Minnesota for 20 years. There are definitely things that I miss, like my friends, and the people, and the weather (yes, the weather), and the lakes; but the high taxes, and the supposed benefits they confer, I do not miss at all.
back in the late 90s i knew a lot of techs that when talking to non-techs would call the computer "the CPU".. i chewed their ass every time for it.
Yeah, I've heard that too. For some reason, it doesn't bother me as much.
Maybe it's because a computer does processing, and so does a CPU. Maybe it's because the acronym almost looks like it could be an abbreviation for ComPUter. Maybe it's because a CPU is part and parcel with a computer (you wouldn't have much of a computer with no CPU, but plenty of computers lack hard drives).
It is a shame when people who should know better use incorrect terms. A PC tech isn't really doing his job if he doesn't educate the end user a bit.
In cree the word for monitor I have found is teevee. The word for computer is hard drive. Who am I to say they are wrong? I just have to make it's still working for them when I am 500 miles away back home.
If you would read the article, you'd notice that his point isn't that different things are called by different words in different languages.
You'd also see that his point wasn't that nontechnical users don't always know the proper names for computer components.
His point is that there is a significant contingent of people who make the specific error of referring to a computer by the name "hard drive". He wonders where huge populations of computer users were taught this specific piece of incorrect terminology.
Personally, I'm a bit curious about that, as well. Why would so many people people refer to a computer as a "hard drive", as opposed to any other component or term. Where are people being taught this?
Well how about this. You, as an IT knowing guy, tell your friend, the retard, that his hard drive is broken. Instead of buying a new hard drive, he buys a new PC, on your recommendation. Language is language and it's important that we are all synced.
What good is it to sync up language, when the guy still has no idea what you are talking about?
This reminds me of a time, a long long time ago, when I went into my college campus's computer store. I told the friendly sales associate that I wanted to look at their hard disks. He handed me a box of 3.5 inch floppies.
Wow.
However, they've now said that, since this hasn't worked so well in practice, the next version of PostgreSQL WILL include direct, built-in support for basic replication, as well as making sure that heavyweight, third-party replication solutions are still supported.
Well, wake me when it's there. MySQL still gets bashed for its historical lack of transactions, so if Postgres wants credit for something, it can at least implement it. Last I checked, it was supposed to be in 8.4, then it wasn't, then it was supposed to be in 8.5, and if memory serves, it's slipping again.
Either way, I don't think these replication issues are a good enough reason to use MySQL instead. Worst case scenario, there ARE good replication options for PostgreSQL.
So which one of those solutions is:
MySQL replication supports all of the above, and has for years now. Postgres has some serious catching up to do in this area.
I imagine the intent is for database administrators to issue that command during scheduled maintenance windows. I agree that an "auto vacuum" feature would be preferable for many people. Is "auto vacuum" the major advantage of MySQL over Postgres, then?
Before auto-vacuum, I'd say it was a big advantage. Anything that can cause you to lose all of your data is a big deal, and it used to be that if you didn't vacuum your postgres tables, you'd lose all of your data eventually. MySQL has no such vacuum requirement.
Nowadays, with auto-vacuum, I'd say that's no longer an advantage. And all of the distros that I've worked with have auto-vacuum enabled by default.
Does it scale better? Does it have better security? Is it easier to manage in some way?
Yes.
PostgreSQL has no serious replication or clustering solution. MySQL does.
If you need high availability, then you need something other than Postgres.
Say you need clustering or replication. Then, you would need MySQL because Postgres does not have a serious solution for you.
Slony-I is a dreadful hack that misuses triggers. It's easy to break, difficult to administer, and doesn't scale past a few nodes.
There is no postgres clustering solution that can add a node to the cluster without blocking all reads and writes as the added node syncs up. Sorry, that is not a real solution.
Postgres has definitely realized their error in forcing replication and clustering into third party apps, and they're going to include replication "real soon now" (although it's already slipped versions at least once).
But, sorry. You can't really use Postgres is a high-availability architecture because of the lack of decent replication and cluster support.
Slony-I is a dreadful hack that misuses triggers, and doesn't scale past a few nodes.
I'm sorry, but Slony-I is not a serious replication solution.
It depends on the person. I live alone, and most recipes I find make a whole lot of food that's quite likely won't be able to eat before it goes bad.
Cooking economically for one is difficult, I'll give you that. You put in all that time and expense, only to throw food away.
This can be partially mitigated with a freezer. I can tell you that in my household, we usually make double the food that we'll need, with the intent of freezing half. With dishes that will freeze well, anyhow. We also bring leftovers into work/school for lunches.
A friend of mine insists it's cheaper to eat out. You see, he doesn't consider his time to prepare meals "free." I don't quite get that, but hey, that's not my problem.
I've never bought into the whole "Well, I make $xx/hr, so I won't yyy" argument. Would your friend have been working during the time he otherwise would have been cooking? Is he even paid hourly?
Even if he actually could trade his cooking time for revenue-producing time, would he want to? I tell you what, my billing rate is pretty high, so if I made that argument for every possible activity, all I'd ever do is work. After all, chances are I can find someone who can do just about any given task for cheaper than my time is worth.
By way of example: My billing rate is roughly 10x the billing rate of my babysitter's. Does that mean I should always work and never see my kids?
Seriously? You've never heard of saturated fat and its effect on cholesterol?
Yes, I've heard of these things. But I would rather eat saturated fat than garbage with zero nutritional value.
The Mac & Cheese recipe we use has many vegetables in it (it's Italian Mac & Cheese), so the saturated fat is less of an issue. Generally, you don't want more than 10% of your caloric intake to come from saturated fat, and if you were to analyze our recipe combined with side dishes, you'd probably find it weighs in pretty close to 10% saturated fat.
People who eat Kraft eat it for convenience, and aren't going to be serving it with sides, and may very well eat it multiple times per week. Kraft Mac & Cheese provides roughly zero nutritional value.
Also, have you seen the serving size of Kraft? I can eat a whole damn box, and I am not a large person.
Homemade mac & cheese is definitely healthier.
Umm. Those things are more or less available in every state. Well, minus the 13,000 lakes part (and I'm pretty sure your tax dollars didn't buy you those 13,000 lakes).
Anything else?
Surely that's not the comparison.
What's your issue with his comparison. He compares carrots with Doritos, or snack food with snack food.
While I generally agree with you, what home grown mac n cheese recipe do you have that is healthier? All of the recipes we have are very high in fat.
I've never understood this aversion to fat. Humans are evolved to digest fat. If you want to make your mac'n'cheese healthier, don't eat all the reprocessed crap that's in Kraft.
Let us also not forget that many families are either single parent or have two working parents and thus there is a lack of time to prepare all of this delicious nutritious food. At my house we've been trying 20 minute recipes but in general they do end up costing more than just going out to eat.
My household is dual-income, and we have plenty of time to prepare delicious, nutritious food. It's all about time management. Chop veggies the night before. Get a crock pot. It's not that hard.
I'm not sure how your home-cooked food costs more than going out to eat. You must be eating strictly off the dollar menu, or you must buy some seriously expensive ingredients.
One thing you are forgetting is that people that are cheap and would buy prepackaged food or eat at McDonalds will buy cheap ingredients for making food from scratch and you'll be back at square one when it comes to health concerns.
There are plenty of cheap, healthy ingredients. Lentils, chick peas, carrots, peanuts, etc. on the veggie side. And with a crock pot, you can buy cheaper cuts of meat--you cook it all day, so it comes out great.
I think the bigger problem is they don't teach home economics in school anymore. The byproduct of all this political correctness is that nobody knows how to run a household and put healthy food on the table.
Minnesotans still pays more per person and I'd bet we get a lot more from our money than you do.
Such as?
"I invoke my right to counsel."
If a peace officer puts handcuffs on you, you're under arrest, period.
Nope. You are merely detained.
I didn't read about the arraignment. That's what matters, because the arrestee either was accused of a crime or has it in writing that the police arrested him without any cause, which is assault.
If he was arrested, the officers would have informed him of the charge, and he would have been arraigned on those charges.
He wasn't even arrested. I seriously doubt the DA will file any charges.
Actually, the standard for police to detain someone is "reasonable suspicion" and the standard to arrest someone is "probable cause".
It sounds like the blogger was detained and not arrested, so the officer would have had to have had "reasonable suspicion" based on "specific and articulable facts". The specific and articulable fact would be him recording the inner-workings of the ATM, and activities of the ATM personnel.
So the cops detained him, determined that there was not "probable cause" to arrest him, and let him go.
So what, exactly, is the problem here?
Also, realize that you only have one side of the story. I doubt the blogger posted anything that would make him look like anything other than an innocent, but the cops may have a different side of the story.
Either way, I can't figure out why people believe the cops acted improperly.
The US is roughly the size of Australia, so as you can imagine, you can't really generalize about where the good jobs are, or where people live, etc. It really depends on the locality.
Most high-paying jobs tend to be in the city proper in any given metro area, but that is not necessarily always true. Take New York, for example. There are a ton of good jobs in the city, but you can find good jobs in the commuter suburbs, too (e.g. Stamford, CT has a lot of financial firms (UBS, Swiss Re, etc.)).
Or take Washington DC, for example. Lots of great jobs in DC, but you have Amazon.com, AOL, and a few huge NOCs in Dulles, Virginia (where?).
So I don't think you can really generalize about how it is here. There are definitely rich people in the city centers (who can afford to send their kids to private schools). There are rich people in the suburbs, too. And there are poor people in both places.
Out in the middle of nowhere, however, you'll mostly find poor people.
IANAL, but I Am A Landlord, so I deal with federal and state anti-discrimination laws.
Forbidding the use of an information source because that source might contain information that a hiring manager might use to practice illegal discrimination, in my opinion, is taking too defensive a stance.
By the bank's logic, why not forbid resumes? I mean, what if the applicant stated that he or she served on the board of a religious charity?
And why not forbid interviews, while we're at it? I mean, what if a candidate shows up in some sort of religious dress?
Bottom line: Either the information source is valuable, or it is not. If it is, use it. But you still need to educate your hiring managers what criteria are legal and illegal to use. If your managers can't handle the task, then maybe you have a different HR problem on your hands.
I once was given a job offer and then they rescinded it because I did not have a high school diploma. Were they wrong? You decide.
How old were you at the time?
I wouldn't be quick to hire some greenbean who couldn't be bothered to finish high school, either.
There are plenty of ports that allow merchant ships with small arms, provided the proper declarations are filed, and the guns are properly locked up.
So what do the people running the cloud do at Christmas if most of the people they're supporting need 10 times the load?
The cloud provider is going to have a heterogeneous set of customers.
Perhaps your e-commerce company needs to scale up for Christmas, while my monthly payment processor needs to scale up on the first day of every month, and some other customer has to scale up on Mondays to deal with processing that queued up over the weekend, and some other customer scales up at night for nightly processing, and some other customer needs to scale up during business hours, and...
In other words, demand gets smoothed out a bit for the cloud provider by having a diversity of different customers with a diversity of different requirements.