Re:Back when people could actually code..
on
DOS 5 Upgrade Video
·
· Score: 1
Thanks for clearing up my overall concern with computers taking over the world! It's a relief to know that current programming skills are nowhere near as good at 20 years ago, and that, by extension, the ones 20 years from now won't be as good as yours are now.
By 2030, there shouldn't be a usable piece of software in the world! Hooray technology!
The school districts I've been around in Cincinnati are great for one thing: begging parents for stuff. A friend of mine has 4 kids in school and their school supply lists are ridiculous. For the youngest, in 1st grade, the teachers actually tell the parents what brands of crayons and glue to buy, all of which are the most expensive. Then the high school is even worse, requiring computers, software, and the like.
It's bad enough that the school can't provide some of the stuff, but the worst part is that the list includes tissues, toilet paper, paper towels, and so forth for the classrooms. I can live with parents needing to buy their children their own supplies, but if the school can't afford paper for the children to wipe their asses with, they need to reprioritize.
Maybe spend less on computers, recordable marker boards, and gymnasium floors and more on basic needs. What's hard to understand about that?
Two versions: server and workstation. That's it. No more "ultimate" or "home" or any other stripped down versions.
For Server: no client access licenses. When you buy a copy of the server software, you can have as many clients as you want. Each server version is capable of everything, including clustering, load balancing, and everything else.
For Workstation: one interface. It could be new or old, whatever, but exactly one. If it's new, we all need to learn the new version. Don't like that? Get Linux or a Mac.
Finally, both server and workstation should support a single hardware compatibility list. If your hardware isn't on the list, you can't load it; update the list monthly through Windows Update. There is Driver Signing already, but you can get around it by ignoring the warnings. Eliminate getting around the warnings.
The distinction between the traditional sites and the blogs is the level of skill of the people writing the articles. If I'm looking for a well-written piece on a new product I've never seen or some comparisons between products, I'm going to hit the trade rags. If I'm actually using the product, though, there isn't a "journalist" in the world with the skills to help me use it right.
Similarly, if I want to know how to attract the hottest young ladies, I'll ask my 20-year-old cousin. If I want real sex advice, though, I'd ask my 45-year-old uncle driving the VW love van. That old fart may be banging the same chicks he's been banging for 15 years, but he's a pro at it!
In 8 years, I have had exactly 1 server crash due to a bad patch and maybe 5 PCs. The server required me to do the Windows installation with the repair option and the PCs had to be fully reinstalled. Not the best situation, but not the end of the world either.
On the other hand, my predecessor at one company decided to "test" everything first. He would get so bogged down in other tasks that he would be way late getting the patches installed. So when Blaster hit, just after I'd taken over his position, I had every computer infected. This WAS a big problem. That was the day that I came to the realization that patching blindly is safer than not patching at all.
Here are some questions for those of you who test every patch:
1. What criteria do you use to determine if the patch is safe?
2. Do you have every possible server and PC configuration available to you to test in a non-production environment?
3. How many systems do you patch before giving the green light?
4. Which department in your company becomes the guinea pig and gets the patches first, after your initial testing says everything is okay?
5. How many days per month do you allocate to simply patching systems?
Now, if you are in a large company, I would expect that patching is at least one person's entire job and all of these questions can get answered. In a small to medium company, however, you'd be hard pressed to get the hardware, people, and time to do the patching "safely".
smithcl8's Guesstimated New iPhone Price in 2009: $500
Timster's Guesstimated Used Working iPhone Price in 2009: $300+$30+$60 = $390.
Conclusion: If you feel like revamping a 2 year old piece of hardware to save 20%, go for it, but those who would not are certainly not idiots. I can't predict the features that will be available in 2009, but I must believe that they will be worth at least $110 more than a used first generation iPhone.
This is how Apple is going to change the pricing model used in the cell phone market. Before, when you drooled over a new phone, you knew that if you waited 1-2 years, you could pick it up for next to nothing. The RAZR, for instance, was about $300 when it came out...one year later, it was $99. I've heard several of my colleagues say that they will get their iPhones in two years when they are $50.
I've explained to these colleagues that there is no way this will happen. Apple's products never become cheaper, they just release new "generations" and keep the price about the same. They fill the gap with less functional products. This method is true for their desktops (Mac Pro, iMac, Mac Mini), notebooks (MacBook Pro, Macbook) and their iPods (iPod, iPod Nano, iPod Shuffle); it only stands to reason that it will be true for iPhones, too.
And since the batteries aren't replacable in the iPhones, after two years, you won't want to get a used one. This locks their customers into the current $500-$600 units forever, as you wouldn't want to buy a used one in 1 1/2 years.
Will this work in the cell phone market? I'm not sure, but I'm certain that there will never be a "free iPhone with 2 year activation" type promotion.
On the first point, I don't know the full percentage breakdown, but between Firefox and IE, you're bound to be reaching close to 99% of Internet users. "Should support more browsers" is a philosophical comment only, and while I agree philosophically that they should, I do not see any business reason for them to do so. By supporting Firefox, they are supporting Windows, Mac, and Linux users...we should be thankful for that alone.
On the second point, if you think, even remotely, that telling IE users they can't use your web service is a good idea, you're nuts. So, yes, that is just you.
See, though I've criticized essentially everything you said, I totally agree!
Sometimes the arrogance of/.ers kills me. To think that a tool as valuable as a computer should take "knowledge and mental ability" illustrates the reason that computers are slower to be adopted.
All it comes down to is that personal computer software sucks. I don't care if it's for Linux, for the Mac, or for Windows, or if it is the operating systems themselves; for the average Joe, they all suck. Apple makes a damn good attempt at making it work out of the box, but even then it takes a little getting accustomed to.
Don't get me started about hardware replacement or upgrades that we, as IT folks, have raped people over for years. The prices charged for simple little upgrades are ridiculous. This pricing makes people think it takes a rocket scientist to do it. "If they charge $150 an hour, that must be some complicated stuff!"
I see the video game console as a much better platform for full adoption. They are, in fact, just small computers, and they work out of the box. Even children with no experience can figure out how to use them and they tend to work for a long time without breaking. No hardware parts to be replaced; if it does break, you just replace it with a new system or send it back under warranty.
Yep. Real physics class. The professor may have been an engineer for all I know. Either way, I didn't last long there. I considered myself to be too right for him.
I was a mathematics major in college. I'll never forget my only college physics class, I found one answer to have pi in it, so I left it in there. Lost 1/2 credit because I didn't take the right number of "significant digits of pi." Next day, dropped the class and picked up a biology course for my science credit.
Maybe, just maybe, all of the digits are significant.
It's called paying your dues. The best techs go through the b.s. first, get their feet wet, and then move up the ladder.
I took my first job in IT, traveling the country installing tiny computer networks of about 4 computers and a server. Pulling cable, imaging the systems, plugging them in. When I got back to the office, I was on a telephone helpdesk. Did it suck? Kinda. Did I learn a ton? Yep. Would I do it again if I was starting over? Yep. Would I do it now? Hell no.
There is a claim on MS's site that the registry hack works for Windows 2000 and that the patch for Windows XP only works on SP2. Can't I just use the same registry hack for 2000 and XP, any service pack? I don't see why not, as if I do the hack on Windows XP and then run TZEdit (downloaded for Windows 2000), my time zone shows up properly adjusted for the new rules.
Why don't I just upgrade to SP2? Well, I have an entire load of new PCs to deploy, but I'm not going to get them done by this weekend. Once they are in place, this is a complete non-issue, but for now, I need to get this working.
Both the mechanic and the dentist in your example obviously own their own shops. You, too, can make money on people's problems, if you want to take the risk of running your own business to do so.
Slashdot Mirror
What did that editor use to check the spelling and grammar in that article? That was almost as hard to read as the average Slashdot post!
This article shall incite many flaming posts.
Thanks for clearing up my overall concern with computers taking over the world! It's a relief to know that current programming skills are nowhere near as good at 20 years ago, and that, by extension, the ones 20 years from now won't be as good as yours are now.
By 2030, there shouldn't be a usable piece of software in the world! Hooray technology!
As an Ohioan, I'm getting a kick out of these replies.
Wait....wrong site.
The school districts I've been around in Cincinnati are great for one thing: begging parents for stuff. A friend of mine has 4 kids in school and their school supply lists are ridiculous. For the youngest, in 1st grade, the teachers actually tell the parents what brands of crayons and glue to buy, all of which are the most expensive. Then the high school is even worse, requiring computers, software, and the like.
It's bad enough that the school can't provide some of the stuff, but the worst part is that the list includes tissues, toilet paper, paper towels, and so forth for the classrooms. I can live with parents needing to buy their children their own supplies, but if the school can't afford paper for the children to wipe their asses with, they need to reprioritize.
Maybe spend less on computers, recordable marker boards, and gymnasium floors and more on basic needs. What's hard to understand about that?
I'm certain that you, indeed, self appreciate yourself often while thinking of the hot college aides.
Two versions: server and workstation. That's it. No more "ultimate" or "home" or any other stripped down versions.
For Server: no client access licenses. When you buy a copy of the server software, you can have as many clients as you want. Each server version is capable of everything, including clustering, load balancing, and everything else.
For Workstation: one interface. It could be new or old, whatever, but exactly one. If it's new, we all need to learn the new version. Don't like that? Get Linux or a Mac.
Finally, both server and workstation should support a single hardware compatibility list. If your hardware isn't on the list, you can't load it; update the list monthly through Windows Update. There is Driver Signing already, but you can get around it by ignoring the warnings. Eliminate getting around the warnings.
No need to continue your work....it's already been solved, too. From a link within the article: http://www.nature.com/news/2007/070716/multimedia/ 070716-13_bx1.html.
What about War?
The distinction between the traditional sites and the blogs is the level of skill of the people writing the articles. If I'm looking for a well-written piece on a new product I've never seen or some comparisons between products, I'm going to hit the trade rags. If I'm actually using the product, though, there isn't a "journalist" in the world with the skills to help me use it right.
Similarly, if I want to know how to attract the hottest young ladies, I'll ask my 20-year-old cousin. If I want real sex advice, though, I'd ask my 45-year-old uncle driving the VW love van. That old fart may be banging the same chicks he's been banging for 15 years, but he's a pro at it!
In 8 years, I have had exactly 1 server crash due to a bad patch and maybe 5 PCs. The server required me to do the Windows installation with the repair option and the PCs had to be fully reinstalled. Not the best situation, but not the end of the world either.
On the other hand, my predecessor at one company decided to "test" everything first. He would get so bogged down in other tasks that he would be way late getting the patches installed. So when Blaster hit, just after I'd taken over his position, I had every computer infected. This WAS a big problem. That was the day that I came to the realization that patching blindly is safer than not patching at all.
Here are some questions for those of you who test every patch:
1. What criteria do you use to determine if the patch is safe?
2. Do you have every possible server and PC configuration available to you to test in a non-production environment?
3. How many systems do you patch before giving the green light?
4. Which department in your company becomes the guinea pig and gets the patches first, after your initial testing says everything is okay?
5. How many days per month do you allocate to simply patching systems?
Now, if you are in a large company, I would expect that patching is at least one person's entire job and all of these questions can get answered. In a small to medium company, however, you'd be hard pressed to get the hardware, people, and time to do the patching "safely".
Thanks for both correcting me and making my point more valid.
smithcl8's Guesstimated New iPhone Price in 2009: $500
Timster's Guesstimated Used Working iPhone Price in 2009: $300+$30+$60 = $390.
Conclusion: If you feel like revamping a 2 year old piece of hardware to save 20%, go for it, but those who would not are certainly not idiots. I can't predict the features that will be available in 2009, but I must believe that they will be worth at least $110 more than a used first generation iPhone.
This is how Apple is going to change the pricing model used in the cell phone market. Before, when you drooled over a new phone, you knew that if you waited 1-2 years, you could pick it up for next to nothing. The RAZR, for instance, was about $300 when it came out...one year later, it was $99. I've heard several of my colleagues say that they will get their iPhones in two years when they are $50.
I've explained to these colleagues that there is no way this will happen. Apple's products never become cheaper, they just release new "generations" and keep the price about the same. They fill the gap with less functional products. This method is true for their desktops (Mac Pro, iMac, Mac Mini), notebooks (MacBook Pro, Macbook) and their iPods (iPod, iPod Nano, iPod Shuffle); it only stands to reason that it will be true for iPhones, too.
And since the batteries aren't replacable in the iPhones, after two years, you won't want to get a used one. This locks their customers into the current $500-$600 units forever, as you wouldn't want to buy a used one in 1 1/2 years.
Will this work in the cell phone market? I'm not sure, but I'm certain that there will never be a "free iPhone with 2 year activation" type promotion.
If there was a Nobel category for "Best Visual Image", it would be yours. Until then, you'll just have to take an Oscar.
I suppose I should go into my Armageddon bunker; there are actual Slashdotters taking up for Microsoft and bashing something Google-related.
On the first point, I don't know the full percentage breakdown, but between Firefox and IE, you're bound to be reaching close to 99% of Internet users. "Should support more browsers" is a philosophical comment only, and while I agree philosophically that they should, I do not see any business reason for them to do so. By supporting Firefox, they are supporting Windows, Mac, and Linux users...we should be thankful for that alone.
On the second point, if you think, even remotely, that telling IE users they can't use your web service is a good idea, you're nuts. So, yes, that is just you.
See, though I've criticized essentially everything you said, I totally agree!
Sometimes the arrogance of /.ers kills me. To think that a tool as valuable as a computer should take "knowledge and mental ability" illustrates the reason that computers are slower to be adopted.
All it comes down to is that personal computer software sucks. I don't care if it's for Linux, for the Mac, or for Windows, or if it is the operating systems themselves; for the average Joe, they all suck. Apple makes a damn good attempt at making it work out of the box, but even then it takes a little getting accustomed to.
Don't get me started about hardware replacement or upgrades that we, as IT folks, have raped people over for years. The prices charged for simple little upgrades are ridiculous. This pricing makes people think it takes a rocket scientist to do it. "If they charge $150 an hour, that must be some complicated stuff!"
I see the video game console as a much better platform for full adoption. They are, in fact, just small computers, and they work out of the box. Even children with no experience can figure out how to use them and they tend to work for a long time without breaking. No hardware parts to be replaced; if it does break, you just replace it with a new system or send it back under warranty.
Charles Simonyi : Rich Man of America for Make Benefit Glorious Nation of Kazakhstan.
Very Nice!
Yep. Real physics class. The professor may have been an engineer for all I know. Either way, I didn't last long there. I considered myself to be too right for him.
I was a mathematics major in college. I'll never forget my only college physics class, I found one answer to have pi in it, so I left it in there. Lost 1/2 credit because I didn't take the right number of "significant digits of pi." Next day, dropped the class and picked up a biology course for my science credit.
Maybe, just maybe, all of the digits are significant.
It's called paying your dues. The best techs go through the b.s. first, get their feet wet, and then move up the ladder.
I took my first job in IT, traveling the country installing tiny computer networks of about 4 computers and a server. Pulling cable, imaging the systems, plugging them in. When I got back to the office, I was on a telephone helpdesk. Did it suck? Kinda. Did I learn a ton? Yep. Would I do it again if I was starting over? Yep. Would I do it now? Hell no.
There is a claim on MS's site that the registry hack works for Windows 2000 and that the patch for Windows XP only works on SP2. Can't I just use the same registry hack for 2000 and XP, any service pack? I don't see why not, as if I do the hack on Windows XP and then run TZEdit (downloaded for Windows 2000), my time zone shows up properly adjusted for the new rules.
Why don't I just upgrade to SP2? Well, I have an entire load of new PCs to deploy, but I'm not going to get them done by this weekend. Once they are in place, this is a complete non-issue, but for now, I need to get this working.
Both the mechanic and the dentist in your example obviously own their own shops. You, too, can make money on people's problems, if you want to take the risk of running your own business to do so.
Yahoo! will make a robot, but only after Google has had one in beta for two years.
I call, like, bull. In two years of, like, usage, my Mac, like, has never, like, given me a problem.