There are a few reasons I strongly disagree with the opinions of those-who-wrote-the-book.
Part 1: MS Office I have yet to be impressed by OpenOffice, it does things a completely different way than I'm used to. Now there is nothing wrong with that and the developers of OO have done and still do a great job for the people that like OO. But consider the thousands of people used to working with MS Office for the past 10> years. From office 97 and before things work in a similar fashion and it's quite easy to understand as MS puts a lot of effort in user-interface design and usability.
Part 2: Visual Studio (.Net versions that is) VS is truly the best IDE I've _ever_ worked with, there is nothing that comes close to it on any OS I've used. KDevelop comes close but as I'm a.Net developer VS is the best tool available.
Part 3: Why switch at all? The warcry of other OS's being FREE (as in beer or completely) doesn't do it for most people. I know of a lot of people who gave different versions of Linux (Ubuntus, Debians, Mandrakes, SuSE's etc) a try and complained that it just was too much fuss to get anything special to work. This way for those group of people a reason to stick with MS software in general, because it's known and looks pretty. I seriously doubt this is going to change until there is someone is prepared to put a _lot_ of money into creating a new and better OS and to lobby like hell with the hardware- and independent software vendors to get support for it.
Conclusion: Just stick with what you need, if you need office applications use MS Office, if you need to run a server take whatever flavor of *NIX you like because it works far better in that area.
Note: I'm not a MS fanboy even my freshly gained MCAD cert doesn't change that.
I've heard that BBNe(d|t) is starting to roll out ADSL2 in the Netherlands (see Tweakers.net (Dutch))
This might be an option on sites which have a long distance to the ADSL point-of-preseance.
Re:Temporary Private Authentication idea
on
Replacing SMTP?
·
· Score: 1
The major drawback for such a solution is that all the firewalls people have, hopefully but I know the didn't, installed there will be an extra open port. And you wouldn't want to open that port to anyone only the mailserver of your ISP totally undoing the solution because you would need to change your firewall when you send a message. This will, in turn, cause such an overhead that it would be impractical to use this. IMHO the SMTP protocol needs to be rewritten with the current knowledge of the Internet and encryption technologies because SMTP is reliable and reasonably fast.
With this technology it should be possible. On the other hand.. bullets travel pretty fast and creating a shockabsorber capable of actually "catching" the bullet would be nearly impossible.
From the post: "The Interceptor is available now" :P
makes me think of a quote from some movie
"None can match The Interceptor for speed!"
There are a few reasons I strongly disagree with the opinions of those-who-wrote-the-book.
.Net versions that is) .Net developer VS is the best tool available.
Part 1: MS Office
I have yet to be impressed by OpenOffice, it does things a completely different way than I'm used to. Now there is nothing wrong with that and the developers of OO have done and still do a great job for the people that like OO. But consider the thousands of people used to working with MS Office for the past 10> years. From office 97 and before things work in a similar fashion and it's quite easy to understand as MS puts a lot of effort in user-interface design and usability.
Part 2: Visual Studio (
VS is truly the best IDE I've _ever_ worked with, there is nothing that comes close to it on any OS I've used. KDevelop comes close but as I'm a
Part 3: Why switch at all?
The warcry of other OS's being FREE (as in beer or completely) doesn't do it for most people. I know of a lot of people who gave different versions of Linux (Ubuntus, Debians, Mandrakes, SuSE's etc) a try and complained that it just was too much fuss to get anything special to work. This way for those group of people a reason to stick with MS software in general, because it's known and looks pretty.
I seriously doubt this is going to change until there is someone is prepared to put a _lot_ of money into creating a new and better OS and to lobby like hell with the hardware- and independent software vendors to get support for it.
Conclusion:
Just stick with what you need, if you need office applications use MS Office, if you need to run a server take whatever flavor of *NIX you like because it works far better in that area.
Note: I'm not a MS fanboy even my freshly gained MCAD cert doesn't change that.
I've heard that BBNe(d|t) is starting to roll out ADSL2 in the Netherlands (see Tweakers.net (Dutch))
This might be an option on sites which have a long distance to the ADSL point-of-preseance.
For the dutch (-speaking) people: Koekel.
The major drawback for such a solution is that all the firewalls people have, hopefully but I know the didn't,
installed there will be an extra open port.
And you wouldn't want to open that port to anyone only the mailserver of your ISP totally undoing the solution
because you would need to change your firewall when you send a message.
This will, in turn, cause such an overhead that it would be impractical to use this.
IMHO the SMTP protocol needs to be rewritten with the current knowledge of the Internet and encryption
technologies because SMTP is reliable and reasonably fast.
We could just switch back to UUCP and let Microsoft choke on that.
With this technology it should be possible.
On the other hand.. bullets travel pretty fast and creating
a shockabsorber capable of actually "catching" the
bullet would be nearly impossible.
See here for google cached version
If you pound something long enough with a hammer you can eventually break anything. It is just a matter of time and resources to this thing is broken.
Use Linux (most likely to be SuSE or some homebrewed version) and get KDE 2.x
I think the I stands for: I own this space station srew the others (Amarican point of view).