If you want some good, cheap, mexican food in the Boston area, check out El Taquaria Mexico in Waltham (bitch to find, but _damn_ good) Great food, cheap, too.
[p.s. I'm not serious. Don't stick magnets on your diskettes or else solar flares will be the worst of your worries].
Hate to say this, but I've tried sticking floppies to the fridge with your average fridge magnet, left there for about a week. No problems. Nothing wrong. Not a bit flipped.
Could we get an interview with Gore himself. (actually 2-3 to get more of a conversation, for example:
Us: Why do you say on your site http://www.algore2000.com/agenda/issue_technolo.ht ml That you are for educating children by using technology, and _on the same page_ you also want schools to hide information from them? How can you promote education with one hand and take it away with the other? Don't you trust the teachers and parents to guide our country's children anymore?
Gore: That's not what I meant.
Us: But that's what you said. Now, could you please, say what you really mean? Long answers are fine (we read JonKatz articles) as long as they are clear, consistant, and have real meaning.
-end example
It just seems to me that the people around here have a fairly high intelligence and a fairly low tolerance for being smoothtalked. I'm sure that having Gore don the official Slashdot Asbestos Underwear (tm) and actually converse with us would go a long way (heck, it might get us out of our chairs long enough to actually *gasp* vote!)
"When you try something new. It wants you to reboot all the time."
Actually, IMHE, there are only a few times when you need to reboot an NT box. Updating some required.dll's, changing hardware, etc.
I know in the versions of InstallShield that I've used to build installs with, at the very end there is a checkbox asking you if the user should reboot their machine. The default is 'yes'. 9 times out of 10, if you know what is being installed, and there's usually a list hanging around, you don't have to reboot the machine.
I do have problems with getting hardware to work on NT boxes, as well as some software, but only rarely is it NT's fault.
BTW, I don't work for MS, I've just used their systems alot, and I do wish they worked better.
preface: I've been writing software for years, and in every company I've worked for, one of the things we've always tried to do is to do no harm to the system. That involves testing.
I don't think source code is the answer to everything. Microsoft has very good documentation for all (most) of their APIs, etc. I don't need to know exactly how a particular function works, as long as it acts the way that it is documented, which in the case of Microsoft, I've always found to be true.
Microsoft _can't_ change their APIs without announcing it, because it would probably break any piece of software that used that API. Yes, things change between versions, and it's all documented.
People around here like to bash Microsoft for their buisness practices and their software. No problem with that. Their APIs are some of the best documented and explained that I've seen, on a function-by-function level. Higher level views can be a bit more difficult to find, especially for things like implementing their asyncronous I/O systems (using them is easy, implementing is difficult).
The GM analogy is a bit flawed. They tell you how much torque their engines have, but not _how_ they produce them.
I'm not trying to say that having the source code isn't valuable, but it is not the best solution to everything.
preface: I've been writing software for years, and in every company I've worked for, one of the things we've always tried to do is to do no harm to the system. That involves testing.
I don't think source code is the answer to everything. Microsoft has very good documentation for all (most) of their APIs, etc. I don't need to know exactly how a particular function works, as long as it acts the way that it is documented, which in the case of Microsoft, I've always found to be true.
Microsoft _can't_ change their APIs without announcing it, because it would probably break any piece of software that used that API. Yes, things change between versions, and it's all documented.
People around here like to bash Microsoft for their buisness practices and their software. No problem with that. Their APIs are some of the best documented and explained that I've seen, on a function-by-function level. Higher level views can be a bit more difficult to find, especially for things like implementing their asyncronous I/O systems (using them is easy, implementing is difficult).
I'm not trying to say that having the source code isn't valuable, but it is not the best solution to everything.
A year has approximately 9000 hours in it To get mean uptimes of ~77,000, simply run, for example, 9 computers for a year. One should crash once.
There are a lot more than 9 computers in the world running -BSD, so you could take a sample on the number of computers running -BSD, and the number of times those computers had to reboot in, say a month. In 31 days, there are 744 hours. To get a total uptime of ~77,000 hours, simply run 1000 computers all month.
Given, you'd need more than just this to get an average mean uptime, but you get the idea.
IIRC The Suez was fairly easy to do. Relatively short canal connecting two large bodies of water that were at about the same level. Only had to cross dry, flat desert.
The Panama Canal had to go over mountains, through a tropical rainforest. They had problems with mudslides, malaria, building a lock system, and many other things.
de Lesseps started the Panama canal, and gave up. He was basically a celebrity at the time because of the Suez.
The Panama canal was built because there was almost a complete misunderstanding of the challenges involved. Ran _way_ over budget and time.
disclaimer: I'm writing all this from recollection. Feel free to refute me.
One thing I haven't seen mentioned anywhere as a solution is to make Microsoft provide free (or limited) support for their products, and to have them be held responsible for failures.
Right now, Gateway, Dell, and others are the people you call if you have a Windows problem. Shouldn't you call Microsoft?
If the OS crashes and ruins files, hardware, etc. because of a failure in the OS, not the apps, difficult, but not impossible to prove, shouldn't Microsoft have some responsibility? Right now, the EULA frees them from that.
It's not a total, immediate, solution, but something, IMHO, that ought to be considered. Who knows, the quality might go up.
When reading this the words "Tyranny of the Majority" suddenly popped into my head.
What is the worst that can happen from this interview? More people not familiar with him (like me) will learn who he is and what he does. Maybe he'll say something insightful, or maybe he'll say something inciteful.
From some of the other comments, this looks like it could be similiar to interviewing a KKK member at a Black Panther meeting.
Slashdot Mirror
Dragging up my Quaker upbringing (It's been awhile since I've thee'd and thou'd, and I never used them much)
I believe that you would want to use
...thee would not be out of place in the surprisingly...
Of course it's been a good while, so I might be mistaken.
BitPoet
If you want some good, cheap, mexican food in the Boston area, check out El Taquaria Mexico in Waltham (bitch to find, but _damn_ good) Great food, cheap, too.
[p.s. I'm not serious. Don't stick magnets on your diskettes or else solar flares will be the worst of your worries].
Hate to say this, but I've tried sticking floppies to the fridge with your average fridge magnet, left there for about a week. No problems. Nothing wrong. Not a bit flipped.
Of course, when you use a _strong_ magnet...
Could we get an interview with Gore himself.
t ml
(actually 2-3 to get more of a conversation,
for example:
Us: Why do you say on your site http://www.algore2000.com/agenda/issue_technolo.h
That you are for educating children by using technology, and _on the same page_ you also want schools to hide information from them? How can you promote education with one hand and take it away with the other? Don't you trust the teachers and parents to guide our country's children anymore?
Gore: That's not what I meant.
Us: But that's what you said. Now, could you please, say what you really mean? Long answers are fine (we read JonKatz articles) as long as they are clear, consistant, and have real meaning.
-end example
It just seems to me that the people around here have a fairly high intelligence and a fairly low tolerance for being smoothtalked. I'm sure that having Gore don the official Slashdot Asbestos Underwear (tm) and actually converse with us would go a long way (heck, it might get us out of our chairs long enough to actually *gasp* vote!)
"When you try something new. It wants you to reboot all the time."
.dll's, changing hardware, etc.
Actually, IMHE, there are only a few times when you need to reboot an NT box. Updating some required
I know in the versions of InstallShield that I've used to build installs with, at the very end there is a checkbox asking you if the user should reboot their machine. The default is 'yes'. 9 times out of 10, if you know what is being installed, and there's usually a list hanging around, you don't have to reboot the machine.
I do have problems with getting hardware to work on NT boxes, as well as some software, but only rarely is it NT's fault.
BTW, I don't work for MS, I've just used their systems alot, and I do wish they worked better.
preface: I've been writing software for years, and in every company I've worked for, one of the things we've always tried to do is to do no harm to the system. That involves testing.
I don't think source code is the answer to everything. Microsoft has very good documentation for all (most) of their APIs, etc. I don't need to know exactly how a particular function works, as long as it acts the way that it is documented, which in the case of Microsoft, I've always found to be true.
Microsoft _can't_ change their APIs without announcing it, because it would probably break any piece of software that used that API. Yes, things change between versions, and it's all documented.
People around here like to bash Microsoft for their buisness practices and their software. No problem with that. Their APIs are some of the best documented and explained that I've seen, on a function-by-function level. Higher level views can be a bit more difficult to find, especially for things like implementing their asyncronous I/O systems (using them is easy, implementing is difficult).
The GM analogy is a bit flawed. They tell you how much torque their engines have, but not _how_ they produce them.
I'm not trying to say that having the source code isn't valuable, but it is not the best solution to everything.
BitPoet
preface: I've been writing software for years, and in every company I've worked for, one of the things we've always tried to do is to do no harm to the system. That involves testing.
I don't think source code is the answer to everything. Microsoft has very good documentation for all (most) of their APIs, etc. I don't need to know exactly how a particular function works, as long as it acts the way that it is documented, which in the case of Microsoft, I've always found to be true.
Microsoft _can't_ change their APIs without announcing it, because it would probably break any piece of software that used that API. Yes, things change between versions, and it's all documented.
People around here like to bash Microsoft for their buisness practices and their software. No problem with that. Their APIs are some of the best documented and explained that I've seen, on a function-by-function level. Higher level views can be a bit more difficult to find, especially for things like implementing their asyncronous I/O systems (using them is easy, implementing is difficult).
I'm not trying to say that having the source code isn't valuable, but it is not the best solution to everything.
BitPoet
So, just create one for yourself.
My official title is "BitPoet"
Of course, our CEO is the "BitMeister"
the head of sales is the "Minister of Commerce"
the head of marketing is "Marketing Guy"
The list goes on.
Anyone else?
Can't believe he missed duct tape.
Also add Swiss Army knives (or your favorite variant).
BitPoet
Well, let's look at some pros and cons here:
There's the linux-fish logo from thinkgeek.com
You can eat fish, you can't eat Linux (Though you could eat Linus, I guess)
Fish have adapted to their living enviornment. So has Linux
Fish can swim. Linux can't.
Fish smell after being out for awhile. Linux doesn't smell even after being left out for a great while.
Fish DNA contains quite a bit more data than Linux' code. (I think)
Fish have been around longer. The Selacanth (sp?)) have eluded extinction for millions of years.
Both the Fish and Linux can perform distributed tasks (think Beowulf, think schools of pirhanas)
Microsoft may be eaten up by Linux. If Gates died at sea, he would be eaten up by the fishes.
Anyone care to add more?
Take a look at Dolch. They make some pretty tough machines (some are even bulletproof)
www.dolch.com
A year has approximately 9000 hours in it
To get mean uptimes of ~77,000, simply run, for example, 9 computers for a year. One should crash once.
There are a lot more than 9 computers in the world running -BSD, so you could take a sample on the number of computers running -BSD, and the number of times those computers had to reboot in, say a month. In 31 days, there are 744 hours. To get a total uptime of ~77,000 hours, simply run 1000 computers all month.
Given, you'd need more than just this to get an average mean uptime, but you get the idea.
Of course, I could be wrong.
BitPoet
VideoServer changed their name to Ezenia.
VideoServer... Pretty sure it has something to do with video on the net. (Videoconferencing, actually)
What the fuck is Ezenia?
BitPoet
Here in Boston, there's
DeathWish piano movers
and
Bunghole Liquors
Can't use that one. Proper noun. You don't get the extra 50 for the 7-letter thing, either, unless it's the first word on the board.
The word you're looking for is "quixotic". I think that on the triple word, it tops off at something like 150.
Ok, so I've played _way_ too much scrabble...
BitPoet
IIRC The Suez was fairly easy to do. Relatively short canal connecting two large bodies of water that were at about the same level. Only had to cross dry, flat desert.
The Panama Canal had to go over mountains, through a tropical rainforest. They had problems with mudslides, malaria, building a lock system, and many other things.
de Lesseps started the Panama canal, and gave up. He was basically a celebrity at the time because of the Suez.
The Panama canal was built because there was almost a complete misunderstanding of the challenges involved. Ran _way_ over budget and time.
disclaimer: I'm writing all this from recollection. Feel free to refute me.
Made by John Carmack in a day on a bet.
Makes me think, "damn, that guy is good"
One thing I haven't seen mentioned anywhere as a solution is to make Microsoft provide free (or limited) support for their products, and to have them be held responsible for failures.
Right now, Gateway, Dell, and others are the people you call if you have a Windows problem. Shouldn't you call Microsoft?
If the OS crashes and ruins files, hardware, etc. because of a failure in the OS, not the apps, difficult, but not impossible to prove, shouldn't Microsoft have some responsibility? Right now, the EULA frees them from that.
It's not a total, immediate, solution, but something, IMHO, that ought to be considered. Who knows, the quality might go up.
Nope. He's still alive.
Darwin awards require removing yourself, and all descendants (If applicable) from the gene pool.
Sorry.
I'd like to take it, reverse the mic. and the speaker, and add a borkification engine. Voila! Everyone sounds like the sweedish chef.
Company meetings would suddenly be a source of amusement.
When reading this the words "Tyranny of the Majority" suddenly popped into my head.
What is the worst that can happen from this interview? More people not familiar with him (like me) will learn who he is and what he does. Maybe he'll say something insightful, or maybe he'll say something inciteful.
From some of the other comments, this looks like it could be similiar to interviewing a KKK member at a Black Panther meeting.
-BitPoet
Recently I ran across this article on assumptions people make when building their e-commerce sites. Thought it might be relevant.
"E-commerce myths"
Funny, I got the image of a lovesick wheat-thin.
Eternal Warriors
So, I guess I ought to register iCyberEOnline.com
Ought to get the $$ rolling in on that one.