I think it is reasonable to assume many companies won't add every fix to their servers. It's much easier to download one 100+Mb patch and apply it than it is to apply the dozens of fixes individually.
Instead of bitching and bickering about the unfairness of it all, I'd bet that if someone took the 21 patches and put them into one service pack ZDNet would re-do the tests. If not, they're caught in a bold-faced lie.
Keep in mind, if someone starts making service packs available, it's got to be consistent. If 40 different service packs are flying around, no administrator is going to sort through them figuring out which one is the newest (at least, not in ZD's world).
It's very likely he took a flaming tone to tick a lot of "Linux proponents" off, and try to show how many of them don't know a compliment when it's surrounded by flames. He's trying to show why people "fear the wrath of the Linux community."
Every single immature post gives him more reason to write his follow-up column, "See, I told you so." Look at all the posts on ZDNet; they attack: his method of benchmarking, "So what", " can't either", "Your writing sucks"... . About 10% of the responses look like discussion, the rest look like flames.
His job is to stir up emotion and bring hits to ZDNet. I'd say he deserves a raise.
There are good sides to both, and bad. From what I've seen, contractors are usually hired for short-term work, and they don't plan on sticking around, either. Contract work is usually in-between jobs or a second, usually part-time, job. They know their stuff, do it (and usually do it well), and move on.
Employees, on the other hand, tend to stick around longer. Here the possibility of getting a leech exists; but, there's also a good chance of finding someone who works, gets trained, works a few more years, and moves on. You may get some that get trained and leave after getting trained, but if you pay them a reasonable salary or hourly wage, it won't likely happen.
If it's work that will be needed for a long time to come, get an employee who wants to be trained and pay him reasonably well.
A few pointers? Careful mixing contractors and employees. Some contractors get jealous or huffy and leave, and some employees get pig-headed and try to be the boss.
Don't advertise contract to permanent. It shows you aren't sure if you want/need an employee or a contractor. Likewise don't offer a new position, then turn around and let the employee go after a few months. Not only are you both disappointed, the ex-employee will go around bad-mouthing you (intentionally or unintentionally, he will). If you really want to contract to perm, advertise contract, and tell them contract to possible perm in an interview or once they start.
Keep in mind that some of the people who know their worth and have high skill levels also have families and a mortgage, and don't like the idea of contract work (or temp work). You also get peons from temp agencies who have inflated egos and inflated qualifications.
My personal preference? I dislike contract work and despise contract to perm. If a company can't make a commitment because they don't know how long the work will be around, I can accept that. If a company isn't sure of my skill-set or work ethic, they probably have a bad recruitment process, and do I want to work for them? If the work is going to be there, make a commitment.
I couldn't stand reading the whole thing, but here's what I got out of it: He's saying that first, Class D and E aren't being used, and we could simply use those addresses. It's actually not a bad idea. His second idea is idiotic. He's saying that the binary addresses don't need to be 8-bits. Right now, every address is 8-bits, even if the address is 32.32.32.32 (0001 0000.0001 0000.0001 0000.0001 0000 in binary) He's saying there's an alternate address of 10000.10000.10000.10000. Unfortunately, we'd have to re-write how TCP/IP works in order to do that (so why not just implement IPv6 is my question). If you didn't update, you'd choke when trying to get to the binary 10000.10000.10000.10000 website.
Most people should get some kind of paper, certification preferably. If they can't get or can't afford that, get a two-year degree so businesses will at least look at you.
It is definately easier to get a degree at a younger age when you can tolerate "stupidity and beuracracy," but don't go into anything with a bad attitude. Try to understand it's something valuable down the road, and easier to get at a younger age.
The only things truly "wrong" with four-year colleges is their slow-to-accept policy, and downright out-of-date material. It's a place where tenure is the ultimate, as professors can cease to create and review class material.
While neither wrong nor bad, keep in mind a four-year college will force-feed you somewhat irrelevant information (history, English, etc.) in an attempt to make you a better person. A two-year or certification will concentrate on what you really care about.
Slashdot Mirror
I think it is reasonable to assume many companies won't add every fix to their servers. It's much easier to download one 100+Mb patch and apply it than it is to apply the dozens of fixes individually.
Instead of bitching and bickering about the unfairness of it all, I'd bet that if someone took the 21 patches and put them into one service pack ZDNet would re-do the tests. If not, they're caught in a bold-faced lie.
Keep in mind, if someone starts making service packs available, it's got to be consistent. If 40 different service packs are flying around, no administrator is going to sort through them figuring out which one is the newest (at least, not in ZD's world).
The one thing you can always count on, if Larry touches it, it will die.
The only thing that seems to avoid this is his own company. Makes me wonder who runs it.
Every single immature post gives him more reason to write his follow-up column, "See, I told you so." Look at all the posts on ZDNet; they attack: his method of benchmarking, "So what", " can't either", "Your writing sucks"... . About 10% of the responses look like discussion, the rest look like flames.
His job is to stir up emotion and bring hits to ZDNet. I'd say he deserves a raise.
-Cyric
There are good sides to both, and bad. From what I've seen, contractors are usually hired for short-term work, and they don't plan on sticking around, either. Contract work is usually in-between jobs or a second, usually part-time, job. They know their stuff, do it (and usually do it well), and move on.
Employees, on the other hand, tend to stick around longer. Here the possibility of getting a leech exists; but, there's also a good chance of finding someone who works, gets trained, works a few more years, and moves on. You may get some that get trained and leave after getting trained, but if you pay them a reasonable salary or hourly wage, it won't likely happen.
If it's work that will be needed for a long time to come, get an employee who wants to be trained and pay him reasonably well.
A few pointers? Careful mixing contractors and employees. Some contractors get jealous or huffy and leave, and some employees get pig-headed and try to be the boss.
Don't advertise contract to permanent. It shows you aren't sure if you want/need an employee or a contractor. Likewise don't offer a new position, then turn around and let the employee go after a few months. Not only are you both disappointed, the ex-employee will go around bad-mouthing you (intentionally or unintentionally, he will). If you really want to contract to perm, advertise contract, and tell them contract to possible perm in an interview or once they start.
Keep in mind that some of the people who know their worth and have high skill levels also have families and a mortgage, and don't like the idea of contract work (or temp work). You also get peons from temp agencies who have inflated egos and inflated qualifications.
My personal preference? I dislike contract work and despise contract to perm. If a company can't make a commitment because they don't know how long the work will be around, I can accept that. If a company isn't sure of my skill-set or work ethic, they probably have a bad recruitment process, and do I want to work for them? If the work is going to be there, make a commitment.
I couldn't stand reading the whole thing, but here's what I got out of it: He's saying that first, Class D and E aren't being used, and we could simply use those addresses. It's actually not a bad idea. His second idea is idiotic. He's saying that the binary addresses don't need to be 8-bits. Right now, every address is 8-bits, even if the address is 32.32.32.32 (0001 0000.0001 0000.0001 0000.0001 0000 in binary) He's saying there's an alternate address of 10000.10000.10000.10000. Unfortunately, we'd have to re-write how TCP/IP works in order to do that (so why not just implement IPv6 is my question). If you didn't update, you'd choke when trying to get to the binary 10000.10000.10000.10000 website.
Sounds very familiar.
Most people should get some kind of paper, certification preferably. If they can't get or can't afford that, get a two-year degree so businesses will at least look at you.
It is definately easier to get a degree at a younger age when you can tolerate "stupidity and beuracracy," but don't go into anything with a bad attitude. Try to understand it's something valuable down the road, and easier to get at a younger age.
The only things truly "wrong" with four-year colleges is their slow-to-accept policy, and downright out-of-date material. It's a place where tenure is the ultimate, as professors can cease to create and review class material.
While neither wrong nor bad, keep in mind a four-year college will force-feed you somewhat irrelevant information (history, English, etc.) in an attempt to make you a better person. A two-year or certification will concentrate on what you really care about.