I think that the beer you speak of so fondly may be clouding your judgment. The holy FRIST POST is a competetion to see who can spew out the most intelligent sounding drivel before any one else has a similar brain-fart.
May be offtopic, but worth pointing out. Microsoft is not in Seattle. It is in Redmond, which is across Lake Washington from Seattle. It is still very close, but I in no way am wrong because Microsoft happens to be based in Redmond. I hope you don't have the mis-conception that all of Seattle support Microsoft (which I doubt you do since Real is ACTUALLY based in Seattle).
I mostly agree with you, even where I disagree. A Good admin is "at heart a lazy, worthless bastard who will do anything, _script_anything_, to get out of work" (emphasis added). These types of admins, while getting the job done well and fast (if they're good) create such arcane scripts that the next person who comes in to do the job needs to spend a huge amount of time learning it, or start from scratch.
I think the best admin writes scripts, but won't go too far to make himself difficult to replace.
its not about punishing them for being successful, its about preventing them from being sucessful simply because they are able to skew the game in their favor in new arena's (OS and browser are different arenas). Its about allowing "little half-assed newcomers" to have a fair shot at succeeding.
does anyone know if CodeRed spawns off other threads that would stay alive when iis is stopped? if so, doing this would help with very little, apart from possibly alerting the admin (assuming there is one) that the website is down. The response most likely with be the typical windows reboot.
Nice analogy. Here in Seattle, every other year or so, the Snohomish river washes people's houses away, developers come along, build shoddy houses (because they only need to last for a few years), people from other parts of the country move into them, flood, repeat.
Microsoft builds shoddy software because by the time exploits are found, they can say "you really ought to upgrade to the latest and greatest, besides, it has all these new features". The software isn't any better, just less well known. If they were to stop for a second, build a stable, secure, extensible framework, they would be able to add all the "features" people are "asking for" without introducing more security flaws. However, that would be like building dikes to contain the flooding river. They would just rather move elsewhere.
unless the real source is behind nat. Imagine the company IIS server getting infected, then infecting the client machines behind the NAT, which then lauch attacks appearing to come from the same IP.
Of course, anyone admin who doesn't put the webserver in a DMZ deserves to clean up all the clients they infected this way.
yes, but the more microsoft locks customers into it's "innovations", more possibilities (new markets) are unlocked for Microsoft as they grow bigger, and bigger, and.....POP (DOJ with a red hot needle -- I pray).
Perhaps a reason people launch DOS attacks against entities such as EFNet for no apparent reason is simply to get press.
I think this is similar to the sports fans who run across a baseball field during the seventh-inning stretch (perhaps minus the alcohol however).
Perhaps slashdot should treat them the same way as the broadcasters treat streakers...DON'T GIVE THEM WHAT THEY WANT -- PRESS.
It sounds really good, except that you have to consider which "public" the US Government needs to protect and benefit.
It seems to me (correct me if I'm wrong) that the US has a higher than average concentration of IP related to computer software. Releasing new code under BSD, GPL, whatever "free"/"open" license they decide to use would dilute that concentration (by making more available to the less concentrated economies), possibly making the US economy not as stable. This may be one reason why politicians are reluctant to support open source software development with public money.
I disagree (respectfully) with your assertion that Mozilla should handle crashes better. I think developer time could be better spent on fixing the root cause of the crash, rather than trying to fix the problem after it is encountered.
Slashdot Mirror
I think that the beer you speak of so fondly may be clouding your judgment. The holy FRIST POST is a competetion to see who can spew out the most intelligent sounding drivel before any one else has a similar brain-fart.
May be offtopic, but worth pointing out. Microsoft is not in Seattle. It is in Redmond, which is across Lake Washington from Seattle. It is still very close, but I in no way am wrong because Microsoft happens to be based in Redmond. I hope you don't have the mis-conception that all of Seattle support Microsoft (which I doubt you do since Real is ACTUALLY based in Seattle).
I mostly agree with you, even where I disagree. A Good admin is "at heart a lazy, worthless bastard who will do anything, _script_anything_, to get out of work" (emphasis added). These types of admins, while getting the job done well and fast (if they're good) create such arcane scripts that the next person who comes in to do the job needs to spend a huge amount of time learning it, or start from scratch.
I think the best admin writes scripts, but won't go too far to make himself difficult to replace.
I purchased WindowsME about 4 months ago.....
its not about punishing them for being successful, its about preventing them from being sucessful simply because they are able to skew the game in their favor in new arena's (OS and browser are different arenas). Its about allowing "little half-assed newcomers" to have a fair shot at succeeding.
does anyone know if CodeRed spawns off other threads that would stay alive when iis is stopped? if so, doing this would help with very little, apart from possibly alerting the admin (assuming there is one) that the website is down. The response most likely with be the typical windows reboot.
Nice analogy. Here in Seattle, every other year or so, the Snohomish river washes people's houses away, developers come along, build shoddy houses (because they only need to last for a few years), people from other parts of the country move into them, flood, repeat.
Microsoft builds shoddy software because by the time exploits are found, they can say "you really ought to upgrade to the latest and greatest, besides, it has all these new features". The software isn't any better, just less well known. If they were to stop for a second, build a stable, secure, extensible framework, they would be able to add all the "features" people are "asking for" without introducing more security flaws. However, that would be like building dikes to contain the flooding river. They would just rather move elsewhere.
unless the real source is behind nat. Imagine the company IIS server getting infected, then infecting the client machines behind the NAT, which then lauch attacks appearing to come from the same IP. Of course, anyone admin who doesn't put the webserver in a DMZ deserves to clean up all the clients they infected this way.
I do something similar. tri-boot win2k (work), winme (games), and mostly linux(everything cool).
......Where do you think Astro-Glide got its name (and no, I don't know the real reason they invented this product, but I have some ideas)
yes, but the more microsoft locks customers into it's "innovations", more possibilities (new markets) are unlocked for Microsoft as they grow bigger, and bigger, and.....POP (DOJ with a red hot needle -- I pray).
Perhaps a reason people launch DOS attacks against entities such as EFNet for no apparent reason is simply to get press. I think this is similar to the sports fans who run across a baseball field during the seventh-inning stretch (perhaps minus the alcohol however). Perhaps slashdot should treat them the same way as the broadcasters treat streakers...DON'T GIVE THEM WHAT THEY WANT -- PRESS.
I see your point. We can't really do much about that (windows crashing) so we need to develop where we can...
It sounds really good, except that you have to consider which "public" the US Government needs to protect and benefit.
It seems to me (correct me if I'm wrong) that the US has a higher than average concentration of IP related to computer software. Releasing new code under BSD, GPL, whatever "free"/"open" license they decide to use would dilute that concentration (by making more available to the less concentrated economies), possibly making the US economy not as stable. This may be one reason why politicians are reluctant to support open source software development with public money.
I disagree (respectfully) with your assertion that Mozilla should handle crashes better. I think developer time could be better spent on fixing the root cause of the crash, rather than trying to fix the problem after it is encountered.
and what, the next time a big company comes along, we need to tweak the licenses for them?