I don't think that anyone ignores non-American things on the basis that they aren't American. Someone has already mentioned in this thread that the operating system that most of us go to the bat for is Linux, which we all acknowledge not only to be a Finnish effort, but a *world* effort. Just because an American fails to mention something non-American, doesn't mean that he or she is trying to be pro-American. It's probably that they forgot. Slashdot has seen too much of this 'American-Centric' versus 'Non-American-Centric' debate, when I feel that no one is trying to be American-centric on purpose. Perhaps it's just a misunderstanding? Though many of us live in the U.S. and discuss the U.S., doesn't make us American bigots.
One of your biggest problems in this particular story is that it is talking about legacy technology. And since most of Slashdot's readers happen to live in the U.S., most are going to know about the hardware that was readily available in the U.S. at the various schools and companies. Thus, the most discussed hardware is going to follow this trend. The appropriate approach for mentioning the X1 and X8 would have simply been: "You forgot {..}"
Take a look at the Extreme Programming project at http://www.extremeprogramming.org . It has a lot of useful tips and.. who knows.. a whole process you might want to adapt your staff to. I know at my company we've been trying out different elements of X/P, and we've been getting more efficient every step of the way. This sort of approach to development is refreshing to many, and the only way it is effective is if you, as the manager, push it and work by it.
The efnet (www.efnet.org) IRC network has had these problems for years. I'm not sure how some of their servers have survived, seeing as though many companies donate bandwidth to the cause. I know that a lot of people seemed to have strayed away from it due to the large amounts of DoS attacks, which caused the server links to go up and down (which in turn made a very unstable network). I wonder if they've learned any ways to cope with these attacks? Anyone know of any other networks that have had these issues and are still around?
Cooperation
on
Debian NetBSD
·
· Score: 3, Insightful
To me, this is promising. I like to see cooperation between the Linux world and the *BSD world. Both have their advantages, and it'd be great if both would learn from each other more often. Perhaps this is an instance where some exchange of ideas could come about? Those responsible deserve a pat on the back.
Its not that their website doesn't serve its purpose, but the Tungsten Graphics site doesn't quite instill any security in my mind of their graphics experience. Granted, hardware and DRI-related issues generally don't require good graphical design, but someone should at least offer them a logo.
Slashdot Mirror
Perhaps I'm confused, but isn't OpenSSH a rather well-proven program?
I don't think that anyone ignores non-American things on the basis that they aren't American. Someone has already mentioned in this thread that the operating system that most of us go to the bat for is Linux, which we all acknowledge not only to be a Finnish effort, but a *world* effort. Just because an American fails to mention something non-American, doesn't mean that he or she is trying to be pro-American. It's probably that they forgot. Slashdot has seen too much of this 'American-Centric' versus 'Non-American-Centric' debate, when I feel that no one is trying to be American-centric on purpose. Perhaps it's just a misunderstanding? Though many of us live in the U.S. and discuss the U.S., doesn't make us American bigots.
One of your biggest problems in this particular story is that it is talking about legacy technology. And since most of Slashdot's readers happen to live in the U.S., most are going to know about the hardware that was readily available in the U.S. at the various schools and companies. Thus, the most discussed hardware is going to follow this trend. The appropriate approach for mentioning the X1 and X8 would have simply been: "You forgot {..}"
Take a look at the Extreme Programming project at http://www.extremeprogramming.org . It has a lot of useful tips and.. who knows.. a whole process you might want to adapt your staff to. I know at my company we've been trying out different elements of X/P, and we've been getting more efficient every step of the way. This sort of approach to development is refreshing to many, and the only way it is effective is if you, as the manager, push it and work by it.
The efnet (www.efnet.org) IRC network has had these problems for years. I'm not sure how some of their servers have survived, seeing as though many companies donate bandwidth to the cause. I know that a lot of people seemed to have strayed away from it due to the large amounts of DoS attacks, which caused the server links to go up and down (which in turn made a very unstable network). I wonder if they've learned any ways to cope with these attacks? Anyone know of any other networks that have had these issues and are still around?
To me, this is promising. I like to see cooperation between the Linux world and the *BSD world. Both have their advantages, and it'd be great if both would learn from each other more often. Perhaps this is an instance where some exchange of ideas could come about? Those responsible deserve a pat on the back.
Its not that their website doesn't serve its purpose, but the Tungsten Graphics site doesn't quite instill any security in my mind of their graphics experience. Granted, hardware and DRI-related issues generally don't require good graphical design, but someone should at least offer them a logo.