I would hope that it actually helps by discouraging anyone from using the NDK that doesn't absolutely have to. Hardware banging is a pretty bad idea in this day and age. It isn't always avoidable, but it should be avoided any time it can be.
No, it doesn't. You are going to be hard pressed to find anyone on Slashdot that is going to honestly claim that someone complementing American Idol is "evil". A few people might joke about it, but no one is seriosly going to claim that it is evil.
On the other hand, huge international corporations secretly tracking their customers is quite literally Hollywod movie villain evil.
This is why it is a always a bad idea to be a spelling/grammar Nazi. You always end up being a hypocrite. The parent poster's comment was criticizing content of your post, which was worthy of criticism.
You don't even seem to understand the difference between illegal and evil. Here is a hint. They are not synonymous.
I don't think that is the end game. I think it is to have the entire population believe that they are and always will be helpless children. Consider that the age of legal adulthood has skyrocketed in recent history. Consider things like the drinking age. The current push to raise the driving age. The fact that a woman who graduates high school and gets a job at 18, gets married to her the man she has been dating for years, and gets pregnant at 19 is counted in the "Teen Pregnancy" statistics. Now people will claim "She is a teen. She is nineTEEN." That may be true, but if you are going to count adults in the "Teen Pregnancy" statistics, the statistic is pointless. The fact is that "Teen" is used as a term for post pubecent "kids". So, they are counting adults as childhood pregnancies. Most people now consider 18, 19, 20 year olds as "kids".
keeping a job as an administrator makes you competent
No, it doesn't. And that doesn't just apply to Admins. People in all fields, INCLUDING administration sit in jobs that they are not and never become competent in. You don't don't help your case making absurd claims.
And this is my point. It's not a matter of mtbf, it's a matter of gigabytes:IOPS ratios. Having 2 TB on one spindle is like having a 500,000 square foot warehouse with one loading dock. You just can't get to your stuff. We spread your data across sixty drives because 7500 IOPS is way more than 100 IOPS. We'll backup your data in an hour instead of fourteen. When a drive fails the rebuild time won't be twenty hours.
You explain to me how you pull data off of an enterprise drive you don't have faster and more reliably than you pull it off of a consumer drive. Go ahead. I am listening.
I understand that 7500 IOPS is better than 100 IOPS. I understand that 1 hour backups are better than 14 hour backups. I understand rebuilding a drive in less than twenty hours is better than taking twenty hours. YOU seem to not understand that 7500 IOPS is better than 0 IOPS. 14 hour backups are better than no backup at all. A twenty hour drive rebuild is better than just telling the company lawyer that we no longer have the documentation showing that we gave that crane operator training telling him that taking LSD while lifting 3 ton containers is dangerous.
Having a 500,000 square foot warehouse with one loading dock is dramatically better than just dumping all of your product out on the street.
When an admin is doing their job, enterprise equipment is better, and well planned networks are better. When they are not, people are forced to fend for themselves. At the place I currently work, we have had to backup data to a consumer drive and code the backup functionality into the application. Is that idea? Of course not. Are we reinventing the wheel? Yes. Would we rather the administrator back up the data with a IOP, long MTBF, quickly backed up and restored solution that we don't need to worry about? Of course we would. Unfortunately, the administrator that has kept his job for the last 10 years has claimed the entire time that 3 days worth of backups is sufficient, and if a drive fails at the end of the day before a long weekend, then the fact that decades worth data being lost is a flaw with the software. That is a best case scenario, as even the three days of backups frequently isn't done.
So, you tell me? Is an administrator that has kept his job for 10 years and thinks that 3 days worth of backups is sufficient for data that must be kept for decades is competent?
That is debatable. MS may not actually file the paperwork to sue for lame patents, but that is because they don't need to. They use poor patents, or even patents that don't really exist to harm other companies and entities all the time. It may not fit the exact definition of 'Patent Troll', but it is awful close.
Because anyone that points out flaws in the Mac OS is a "Mac Hater"? Riiiighhht. It does not make sense as a secondary method. It is bad UI and conceptually it's a way to say "This is garbage. I don't want it anymore".
I can say that I have seen exactly the opposite about admins vs. developers. Although, I can agree that consultants tend to be the worst. This makes sense though, as they know that they will not have to be around later to maintain the mess they create, and they have no sense of ownership. They also tend to work as a silo within the company. As long as they deliver their piece, they tend not to care if the rest of the system works or not.
Rationalize all you want, but the WAY that you provide service for the company is by providing it to the employees. The disconnect that admins have from that fact is why people go around them. I don't disagree that many developers don't get it. That is why I quoted a 10% competency rate. That includes Admins as well. You are fooling yourself if you think getting a job as an administrator automatically makes someone competent. It doesn't I understand that the enterprise hard drive might have a better mtbf than a consumer drive, but I can tell you that the cheapest crappiest consumer drive is still more a more reliable backup device than the absolute best enterprise drive that you don't have. At my current client's site, they administrators have decided that 3 days of backups are all you need because "enterprise" drives are too expensive. On 3 different occasions the rogue backups that are being done on a consumer level drive have made the difference in passing the ISO audit or not.
You are also taking an extreme example. MOST admins are not managing 15000 seat facilities. Some are, and they certainly do need different skills, but most are much much smaller than that.
I would have put an eject button right under the drive, as that would have give the option of removing the disk even if the computer was turned off. Just about anything would be better than having it go to the same target as the trashcan though. Your explination of other ways to do it doesn't change the fact that using the same target drop point as the trashcan for eject is poor UI.
That is a rational at best. It is comments like that that get Mac users accused of being fanboys. Dropping a disk in the trash to eject is simply bad UI design. Having other ways to accomplish an eject doesn't change that.
I worked in a software store way back when, and I regularly would have Mac owners come in and ask me how to eject a disk. They would ask multiple times if I really meant that the disk should be put in the trash, and if it that would delete there files. It was a bad UI choice then, and having the icon change while dragging is a bad UI choice now. You shouldn't have to start dragging the disk around to find out where it goes.
You were quite clear that you would base priority on how much trouble a user was to you and not on business need. That makes you an incompetent administrator. As a developer, I don't care how annoying I might find a users, I wouldn't 'prioritize' code based on how much I like a user. It is simply not legitimate to delay supplying a user with resource they need as punishment, even if you do find something else to keep you busy in an attempt rationalize your bad behavior.
That would be the intuitive action that should happen. I get that in 1984, that kind of crappy UI MIGHT have been understandable, but that understanding changed from mistake to incompetence 2 decades ago.
A) Pointing out that admins who don't respect there users are incompent doesn't mean my feeling are hurt. Your comment IS a restatement of your incompetence though.
B) It does NOT mean "little users" (which would be pejorative and a sign of admin incompetence anyway). It is wannabe nerd speak for Loser. http://en.wikipedia.org/wiki/Luser
C) I am a developer and have been an administrator. It isn't that the words are "strange" to me because I am an outsider. It is that I am fully aware of their meaning, and what your level of competence is if you are the type to refer to your users that way.
D) I never said that "support" requires ego stroking, but being a good Administrator and a professional DOES mean treating the people you serve with respect. It doesn't take a "trained psychological professional" to understand simple civility and etiquette.
A) We are talking about Windows. That mean consumer as well as enterprise.
B) A good many of consumers don't know anything about the support cycles on particular programs.
C) We are talking about MS abandoning a platform that they were still selling 2 years ago. The length of warranty on the OEM machines is irrelevant.
D) The support time line you are referring to is for bug fixes to the OS, not the abandonment of offering software on that platform.
E) The machines bought in 2009 were not 'pieces of shit'. They were perfectly fine for the tasks they were designed for.
Obviously, you look at your environments and assume that everyone needs a fast machine and it gets replaced every couple years. You then assume that is the only market, or the only one that counts. Maybe if you stepped out of your hole every once in a while, you would find out that being aware of the world around you isn't synonymous with stupid.
You MAY be complying with Federal regulations, but if the user has to install his own equipment to do his job well, then you are NOT doing your job. IT's job is to serve the users. Period. Without users, there is no IT. As much as security is great, it is often used as an excuse for IT to do a poor job. 'Enterprise' is often another excuse. Our department has had to resort to doing backups on a consumer USB drive that the department head requisitioned without an explination for it's use. Why do we do this? Because the admin side of IT has decided 3 days worth of backups is all they can afford the 'enterprise' disk space for, and consumer level drives wouldn't be reliable enough. So, instead of a 1% chance of not having the data when an audit comes around, we have a 90% chance because they just don't do backups.
Slashdot Mirror
I would hope that it actually helps by discouraging anyone from using the NDK that doesn't absolutely have to. Hardware banging is a pretty bad idea in this day and age. It isn't always avoidable, but it should be avoided any time it can be.
No, it doesn't. You are going to be hard pressed to find anyone on Slashdot that is going to honestly claim that someone complementing American Idol is "evil". A few people might joke about it, but no one is seriosly going to claim that it is evil.
On the other hand, huge international corporations secretly tracking their customers is quite literally Hollywod movie villain evil.
disapprove off
This is why it is a always a bad idea to be a spelling/grammar Nazi. You always end up being a hypocrite. The parent poster's comment was criticizing content of your post, which was worthy of criticism.
You don't even seem to understand the difference between illegal and evil. Here is a hint. They are not synonymous.
I don't think that is the end game. I think it is to have the entire population believe that they are and always will be helpless children. Consider that the age of legal adulthood has skyrocketed in recent history. Consider things like the drinking age. The current push to raise the driving age. The fact that a woman who graduates high school and gets a job at 18, gets married to her the man she has been dating for years, and gets pregnant at 19 is counted in the "Teen Pregnancy" statistics. Now people will claim "She is a teen. She is nineTEEN." That may be true, but if you are going to count adults in the "Teen Pregnancy" statistics, the statistic is pointless. The fact is that "Teen" is used as a term for post pubecent "kids". So, they are counting adults as childhood pregnancies. Most people now consider 18, 19, 20 year olds as "kids".
Do you realize that every one of your response is an agreement that you are an incompetent admin, right?
So, change the subject if that makes you feel better. It is probably for the best, as you have made your competence level perfectly clear.
keeping a job as an administrator makes you competent
No, it doesn't. And that doesn't just apply to Admins. People in all fields, INCLUDING administration sit in jobs that they are not and never become competent in. You don't don't help your case making absurd claims.
And this is my point. It's not a matter of mtbf, it's a matter of gigabytes:IOPS ratios. Having 2 TB on one spindle is like having a 500,000 square foot warehouse with one loading dock. You just can't get to your stuff. We spread your data across sixty drives because 7500 IOPS is way more than 100 IOPS. We'll backup your data in an hour instead of fourteen. When a drive fails the rebuild time won't be twenty hours.
You explain to me how you pull data off of an enterprise drive you don't have faster and more reliably than you pull it off of a consumer drive. Go ahead. I am listening.
I understand that 7500 IOPS is better than 100 IOPS. I understand that 1 hour backups are better than 14 hour backups. I understand rebuilding a drive in less than twenty hours is better than taking twenty hours. YOU seem to not understand that 7500 IOPS is better than 0 IOPS. 14 hour backups are better than no backup at all. A twenty hour drive rebuild is better than just telling the company lawyer that we no longer have the documentation showing that we gave that crane operator training telling him that taking LSD while lifting 3 ton containers is dangerous.
Having a 500,000 square foot warehouse with one loading dock is dramatically better than just dumping all of your product out on the street.
When an admin is doing their job, enterprise equipment is better, and well planned networks are better. When they are not, people are forced to fend for themselves. At the place I currently work, we have had to backup data to a consumer drive and code the backup functionality into the application. Is that idea? Of course not. Are we reinventing the wheel? Yes. Would we rather the administrator back up the data with a IOP, long MTBF, quickly backed up and restored solution that we don't need to worry about? Of course we would. Unfortunately, the administrator that has kept his job for the last 10 years has claimed the entire time that 3 days worth of backups is sufficient, and if a drive fails at the end of the day before a long weekend, then the fact that decades worth data being lost is a flaw with the software. That is a best case scenario, as even the three days of backups frequently isn't done.
So, you tell me? Is an administrator that has kept his job for 10 years and thinks that 3 days worth of backups is sufficient for data that must be kept for decades is competent?
That is debatable. MS may not actually file the paperwork to sue for lame patents, but that is because they don't need to. They use poor patents, or even patents that don't really exist to harm other companies and entities all the time. It may not fit the exact definition of 'Patent Troll', but it is awful close.
Because anyone that points out flaws in the Mac OS is a "Mac Hater"? Riiiighhht. It does not make sense as a secondary method. It is bad UI and conceptually it's a way to say "This is garbage. I don't want it anymore".
I can say that I have seen exactly the opposite about admins vs. developers. Although, I can agree that consultants tend to be the worst. This makes sense though, as they know that they will not have to be around later to maintain the mess they create, and they have no sense of ownership. They also tend to work as a silo within the company. As long as they deliver their piece, they tend not to care if the rest of the system works or not.
Rationalize all you want, but the WAY that you provide service for the company is by providing it to the employees. The disconnect that admins have from that fact is why people go around them. I don't disagree that many developers don't get it. That is why I quoted a 10% competency rate. That includes Admins as well. You are fooling yourself if you think getting a job as an administrator automatically makes someone competent. It doesn't I understand that the enterprise hard drive might have a better mtbf than a consumer drive, but I can tell you that the cheapest crappiest consumer drive is still more a more reliable backup device than the absolute best enterprise drive that you don't have. At my current client's site, they administrators have decided that 3 days of backups are all you need because "enterprise" drives are too expensive. On 3 different occasions the rogue backups that are being done on a consumer level drive have made the difference in passing the ISO audit or not. You are also taking an extreme example. MOST admins are not managing 15000 seat facilities. Some are, and they certainly do need different skills, but most are much much smaller than that.
HFCS is High Fructose Corn Syrup.
I would have put an eject button right under the drive, as that would have give the option of removing the disk even if the computer was turned off. Just about anything would be better than having it go to the same target as the trashcan though. Your explination of other ways to do it doesn't change the fact that using the same target drop point as the trashcan for eject is poor UI.
That is a rational at best. It is comments like that that get Mac users accused of being fanboys. Dropping a disk in the trash to eject is simply bad UI design. Having other ways to accomplish an eject doesn't change that.
I worked in a software store way back when, and I regularly would have Mac owners come in and ask me how to eject a disk. They would ask multiple times if I really meant that the disk should be put in the trash, and if it that would delete there files. It was a bad UI choice then, and having the icon change while dragging is a bad UI choice now. You shouldn't have to start dragging the disk around to find out where it goes.
It is still the same target. Having the icon change is an obvious attempt to try to legitimize a poor UI.
You were quite clear that you would base priority on how much trouble a user was to you and not on business need. That makes you an incompetent administrator. As a developer, I don't care how annoying I might find a users, I wouldn't 'prioritize' code based on how much I like a user. It is simply not legitimate to delay supplying a user with resource they need as punishment, even if you do find something else to keep you busy in an attempt rationalize your bad behavior.
That would be the intuitive action that should happen. I get that in 1984, that kind of crappy UI MIGHT have been understandable, but that understanding changed from mistake to incompetence 2 decades ago.
it doesn't quit the application.
Except when it does close the application. Which there is no rhyme or reason in determining which applications that will be.
A) Pointing out that admins who don't respect there users are incompent doesn't mean my feeling are hurt. Your comment IS a restatement of your incompetence though.
B) It does NOT mean "little users" (which would be pejorative and a sign of admin incompetence anyway). It is wannabe nerd speak for Loser. http://en.wikipedia.org/wiki/Luser
C) I am a developer and have been an administrator. It isn't that the words are "strange" to me because I am an outsider. It is that I am fully aware of their meaning, and what your level of competence is if you are the type to refer to your users that way.
D) I never said that "support" requires ego stroking, but being a good Administrator and a professional DOES mean treating the people you serve with respect. It doesn't take a "trained psychological professional" to understand simple civility and etiquette.
A) We are talking about Windows. That mean consumer as well as enterprise.
B) A good many of consumers don't know anything about the support cycles on particular programs.
C) We are talking about MS abandoning a platform that they were still selling 2 years ago. The length of warranty on the OEM machines is irrelevant.
D) The support time line you are referring to is for bug fixes to the OS, not the abandonment of offering software on that platform.
E) The machines bought in 2009 were not 'pieces of shit'. They were perfectly fine for the tasks they were designed for.
Obviously, you look at your environments and assume that everyone needs a fast machine and it gets replaced every couple years. You then assume that is the only market, or the only one that counts. Maybe if you stepped out of your hole every once in a while, you would find out that being aware of the world around you isn't synonymous with stupid.
No kidding. I'm still trying to figure out how MS missed the obviously intuitive UI element of using the trash can for eject.
That is AT BEST fear mongering. A hard drive crash in a failure. A network dropping is a failure. These do not lead to multi-million dollar lawsuits.
Any Sysadmin that would refer to their users as 'Lusers' is incompetent. Users are the only reason for Sysadmins to exist.
You MAY be complying with Federal regulations, but if the user has to install his own equipment to do his job well, then you are NOT doing your job. IT's job is to serve the users. Period. Without users, there is no IT. As much as security is great, it is often used as an excuse for IT to do a poor job. 'Enterprise' is often another excuse. Our department has had to resort to doing backups on a consumer USB drive that the department head requisitioned without an explination for it's use. Why do we do this? Because the admin side of IT has decided 3 days worth of backups is all they can afford the 'enterprise' disk space for, and consumer level drives wouldn't be reliable enough. So, instead of a 1% chance of not having the data when an audit comes around, we have a 90% chance because they just don't do backups.
Of course it does, but unfortunately, his organization is the norm, not the exception.