OK. He got the screws wrong. Big deal. Try reading the article.
Some of the things NVidia did on their "working board" include: covering the SLI connector, not having the DVI connector wires go through vias, place the PCI-E power connectors wrong from where the board shows they should be, cut off the end of the board with a saw right though where there was more stuff, have half the vents on the back of the card completely blocked...
This isn't just "they used the wrong screws", this is "total fake that couldn't possibly work". Saying it was a working board was a total lie.
Have you used Stack Overflow? It's quite different from a Wiki, and is much more focused than a bulliten board. The ability to rate questions and answers makes it much easier to find good responses than generic phpBB sites.
I just wish they showed the cars up close afterwards. While both are trashed, it's clear from the video that the A pillar just collapses on the Bel Air and the driver is probably crushed to death. Showing that (or whatever you can film) versus the still mostly intact cockpit of the Malibu would have driven the point home really well.
Re:Duct tape is fine, if you throw it away quickly
on
The Duct Tape Programmer
·
· Score: 4, Insightful
Everyone seems to be taking this article as "do anything it takes to ship" and saying that's a horrible attitude.
Your comment is the first I've seen that seems to be more along my understanding of the piece. Duct Tape Programming is about getting what is needed done and building from there.
"I need a website that lets people share videos".
So what do you do? Do you make a little site that serves flash videos? That's Duct Tape Programming.
Making a little site that takes videos and catalogs them and tries to analyze them for similarity and has editing tools and needs to be able to scale to 20 computers and... That's the problem.
When you start your site, it's OK to have it not be able to instantly scale out to 10,000. Sometimes it's better to get the basic features there and build them up and fix them as you go. Not everything needs to be there from day one. Not everything needs 3 layers of abstraction because it's "what people do".
As your program goes on, you clean it up, add abstractions where needed. The first version of Word for Windows didn't look ANYTHING like the current version. If you are going to make a new word processor, you go after the old version, not aim at the sky.
Your understanding of his post agrees with mine. This isn't about a system to last 20 years, this is about a system to fix things NOW while you make it better so your users don't have to keep doing things by hand for 6 months while you try to figure out why your framework build on another framework isn't interacting correctly with some other thing.
We here at Bob's Atrocious Dealings are having a problem and require your help.
As you may know, Neodyne Inexpensive Care-taking Equipment gives away free diabetes test strips as an incentive to get people to buy their Glucodex 1726 Blood Glucose Meter. These strips are coded to only work with their meter.
We here at B.A.D. sell a competing meter, the Blud-O-Matic 666, which has been designed to use their free strips by pretending to be their meter.
Now you may not have known about our device, as we didn't submit it to you for review. You approved our previous product, the Seth's-Audi-Scope 1996, so we figured you'd be good.
Now our customers, who use the free strips that N.I.C.E. provides their users, are having problems since they keep changing the way their meter works. This is causing us problems, and our confused customers aren't even asking us for support sometimes since they think it's N.I.C.E.'s fault.
FDA, please slap down N.I.C.E. for hampering competition by making it hard for us to profit off their hard work by deliberately changing their strips to fail with our unregistered, uncertified meter. It's confusing our customers that one of the features we trumpet in all our marketing keeps breaking.
So the whole "Doomsday Machine" thing was an automated system based on ground sensors to launch the missiles in case US attacks.
On the first page it explains all the conditions that must be met for this thing to go off. They include:
Enabled by military
No contact from headquarters
Detected nuclear detonation
Button press by guy in bunker
It's not automated. All it does it make sure someone is always able to fire the nukes, no matter which parts of the country get bombed. If the US detonated some new bomb that removed all human life within Russian borders, down to 500 miles underground, this system wouldn't be able to launch because the guy with his finger on the button would have been vaporized.
Actually the idea in the article that it was to keep the USSR generals and stuff from doing stupid things like launching first attacks because it would make sure they could always strike back was quite interesting.
At this point, the thing that would worry me most is that it's sounds like it's targeted at the US. So if some group in Afghanistan decides to take revenge for their war 2-3 decades ago (or N.K. attacks to prove they're cool, or...), then if this system enables the button the terrified guy at the button can fire back in defense... which would promptly attack the US because in panic he didn't realize that was who this was designed to defend against.
The article says there is a checklist he is supposed to follow too, but that's not a big comfort.
The headaches your job provides may end up being too much for the benefit. It may be worth it to people.
Even if you don't judge it worth leaving, are you telling me that if management was constantly saying "use X" when it's not even in the right class, you wouldn't prepare to leave when the opportunity came? You don't want to have to fix problems that you predicted and warned against ahead of time forever.
Remember, you don't have to leave until you have a new job. You could slowly look on the sly for 6 months or a year.
Why not ask the teacher what it's being used for? I can think of a couple of things.
You're only doing the strap, so this is just for hygiene and he'll wear it either way
It's so they can teach the kids to recognize when their heart rate is high enough to be cardiac exercise or when they are working too hard
It's so they can chart the kids over the semester to see if what they are teaching them is working (i.e. to evaluate the teacher/program, not the kids)
Maybe it's to make teaching how your heart rate changes in response to stress/exercise easier than when I was in school (and you had to take your own pulse to a stopwatch)
Just find out what they are using it for. If you are really paranoid, get the principal to sign some slip saying that can only use it for those purposes.
Not everything has to be sinister. This doesn't seem like any real invasion of privacy. Would you be worried if the kids were running on fancy treadmills that already do this anyway?
Knowing your heart rate can be an important thing in exercising.
That way my immediate thought. It's a nice thing to do (compared to the "we own everything you type" option), but I figured this way simply because they are getting too many contacts from people's lawyers and want to put themselves in a position of lower risk.
Not that it stops screwballs from suing you. Google has been sued over stuff that has nothing to do with them because their search engine points to pages that say whatever.
If you don't want things to look executable, mount it with the noexec option (which you could put in fstab). That way nothing on the device, even with FAT, will appear executable.
Since you are moving the files between computers, is the permissions loss really a problem? Aren't you just going to copy things off anyway?
If you need to limit access to certain users, you could use encrypted loopback file systems. But really, why not just use separate USB keys for different sets of permissions.
FAT is a lowest common denominator for a reason. If you want to interact with Windows, your only other real choice is NTFS, which isn't a bad option.
Sure you could use Ext3, or Reiser, or BTFS, or something else, but then you can't use your flash drive on any machine, thus defeating it's purpose.
Instant. I can the text on the page as I'm turing it. If someone is interrupting me and I have to re-read the last paragraph on the last page because I forgot it, I can do that really fast on real book.
With eInk, you have to put up with the switching delay.
I know they're getting better, but it is an issue right now.
I think a big part of the problem is that the full screen has to turn one color then the other to prevent ghosting. That effectively doubles refresh time and that "flash" makes it much more noticeable than if, like the LCD I'm typing on right now, it only switched the pixels that changed.
eInk works great once you have the page displayed, especially if you have a large screen. Wouldn't something iPhone sized (or a little bigger) with an eInk screen be pretty great? Imagine the batter life! But all the page refreshes would make it rather annoying to use.
If we could get something with a refresh rate akin to an old passive matrix LCD, we'd be in good shape. What was that, 50ms or so?
We had that discussion. In fact, that story was posted just 26 hours before this one.
We know Apple wouldn't let them do this. It's the same as it was when Apple first announced the rules for making applications. It's the same reason you can't sell Python. You can't let users program the phone. This is because Apple is careful, evil, protecting a sandbox, just a jerk, blah blah blah.
We've had it all out before. We had it out 26 hours ago. This story wasn't useful. This is the kind of story that used to go into the quickies updates, because that's all it is, a one line update.
This is a non-story. They weren't allowed to sell the app because it had BASIC. They snuck BASIC in, and Apple pulled it since they weren't allowed to sell it.
This is not news.
We don't need the "Apple should allow..." discussion. We had that 2 days ago when this was approved. And the last app that did something. And two before. And the next one.
This isn't a story. "Apple does exactly what it said it would." Call CNN.
I don't support it at all. I think it's a horrible idea for the US to get single payer healthcare.
I'll grant you the idea isn't bad. I just don't trust the government enough to do it. I'm not some anti-government nut, but let's look at some of their track record:
Social Security - Pyramid scheme, out of money, massive tax burden, has become an entitlement to live off of and almost the default retirement plan instead of a worst case backup. And politician's won't cut it back because that would upset important voters.
Medicate/Medicaid - Massive tax burden, growing too fast.
Fannie May/Freddie Mac - Went broke, needed bailout (these were spun off).
Basically, I don't trust that this won't become another giant mess of regulation and debt that we can't get out of. If they fixed Medicare or Social Security and it actually worked, they'd have credibility. As it is, this just seems like a chance for a giant boondoggle.
Don't forget the fun regulation that comes with government regulations. When my grandmother died, her life insurance was enough that my grandfather would have been pushed out of Social Security, his only means of support. So he had to spend it in one of the ways that was approved. He bought a new car.
He could have saved that money, used it to make his retirement more comfortable, or to pay medical bills that would inevitably happen later.
Instead he had to buy a new car (other choice: buy/fix home, may be others) so he wouldn't get kicked out. But it wasn't enough money for him to live off of for even a year, so he had to comply.
Fun stuff, those government regulations.
Giant entitlement debt ridden morass of weird regulations. That is what the current track record leaves me to expect, and I don't want it.
Fix medicare, make it solvent. Or SS. Once they have that record that they can actually run a program like this, we can talk about single payer healthcare.
I see three possibilities. First, AT&T hasn't invested in their network enough. That's a given. Second, iPhone users are just network hogs, I don't think so.
So that leaves us with possibility three: the iPhone is the first phone that isn't an incredible pain to use.
I think that all other smart phones are artificially low in bandwidth usage because they're hard to use. The IE5 based browser on Windows Mobile (I know they recently improved it) in my experience was a total joke and almost unusable. The browser on BlackBerries, in fact the UI as a whole, is not designed to ease of use at all, it's "here's an empty button we can use". That only really leaves non smart phones, and even IF you had a data plan, I'm sure we all know how easy browsing with those things was.
Basically the iPhone is the first device it's possible to easily surf the web without wanting to throw the phone into a wall.
When you give your customers something that actually works and is usable... they use it.
I realize the benefits of Android, they're quite clear. I would have loved something like Android before I got my iPhone.
I just worry the G1 hasn't made much of a splash, and if the other phones coming don't, I wouldn't put it past the carriers to say "We don't want another Android phone, those don't sell well." I worry that Android won't get the chance it should because it's not attached to a better phone. If things had started with 3 phones, I'd think of it in a better position.
Next year will be the big year. That's when we will see what happens. But the cell phone market (at least in the US) has it's priorities so strange (usability? What's that?), I'm not sure this approach is going to work.
I was referring to the market for physical phone it's self, not the app market. I really don't know the state of the Android app market (other than it's bigger than the Pre's, which is not hard to do).
Where is the market? AT&T has the iPhone, the phone. The one everyone wants to beat.
Sprint has the Pre. It's a pretty decent phone with a few build quality issues. Once Palm gets a brain and starts letting apps come out, it could be pretty good.
Verizon has... who knows. Standard Blackberries?
And then there is little T-Mobile with.. Blackberries.
I don't remember seeing many (any?) ads for the G1. I don't remember anyone talking about it except release day calling it "the google phone" when it's not Googly in any way. Basically, not many people care, because I don't think many people know about it. My boss has one, and it's quite nice. But it has no mindshare.
Why should it? It doesn't have an amazing app store (like the iPhone). It doesn't have sexy hardware (like the iPhone or many imitators). It doesn't have an amazingly cheap price. There is nothing to stand out about it other than running "google OS". And since Android doesn't have a reputation yet, that doesn't sell phones.
Great apps would help, but people won't build those until the thing is more popular. Better hardware would help a little so it doesn't look so blocky (the G2 should help here).
Microsoft has this same problem. When Apple wants the hardware to do something, it builds it. When Microsoft wants it, they push and prod and within a few years it happens. Dell (et all) don't make sexy computers, or at least didn't start until after years of Apple taking the "good looking" market.
Android could be something great, even if it takes the "low end smartphone" market. But it could take years to get there, and companies may not be willing to wait that long. If Google had taken some of the risk and co-developed a phone (a Honda or Acura to Apple's BMW, instead of the Ford Focus we got) Android could be in a better spot.
But the Pre is the weakest right now, in my eyes. They've had months and released almost no apps. You know what they just released in the last week or two? Out of the 4 or 5 apps, two were to help people with Jewish observances. Not exactly "phone moving" applications. Floodgates may not open until Christmas or later, and without some lower-level stuff there might not be good games. Some strong funded development in apps and some marketing could really help Android. More phones certainly would.
The question is, will this be the next DOS/Windows (good enough, builds up to dominance), or OS/2 (better than the common, but never achieves critical mass and becomes irrelevant)?
How about a series of ads showing how easy it is to navigate/use the phone, compared to the nightmare of a UI that Blackberries use? Aim for that market. Aim for consumers (not necessarily businesses) who want a smartphone, but don't want and iPod.
Of course, I wouldn't want to fight against a $99 iPhone. The only reason that thing hasn't destroyed the market is it's tied to AT&T.
It was 10.1 which was free, sort of a thank you gift to everyone who used 10.0. I remember using 10.0 on my brother's Mac. It was neat, but it was quite slow and bloated feeling compared to OS 9.
Slashdot Mirror
Ooh! I get it. This is The Argument Sketch.
*clears throat*
Yes they are.
No it doesn't.
Of course they have.
Could too.
OK. He got the screws wrong. Big deal. Try reading the article.
Some of the things NVidia did on their "working board" include: covering the SLI connector, not having the DVI connector wires go through vias, place the PCI-E power connectors wrong from where the board shows they should be, cut off the end of the board with a saw right though where there was more stuff, have half the vents on the back of the card completely blocked...
This isn't just "they used the wrong screws", this is "total fake that couldn't possibly work". Saying it was a working board was a total lie.
Plus, the first time an application tries to use it, the iPhone pops up a little notification asking you for your permission.
WINE and ReactOS aren't redistributions of Windows.
This is more like if MS told people making Windows XP slimming programs to not distribute Calculator with their mods because MS owns Calculator.
Of course, you can't redistribute Windows like that, where you can Android.
There weren't, at least not This American Life. They've had their podcast for a while now, although it was available from Audible before that.
They just re-aired the episode last week (due the to movie, as Kozz said), so it's available for free right now. It was a really great story.
Have you used Stack Overflow? It's quite different from a Wiki, and is much more focused than a bulliten board. The ability to rate questions and answers makes it much easier to find good responses than generic phpBB sites.
I just wish they showed the cars up close afterwards. While both are trashed, it's clear from the video that the A pillar just collapses on the Bel Air and the driver is probably crushed to death. Showing that (or whatever you can film) versus the still mostly intact cockpit of the Malibu would have driven the point home really well.
Everyone seems to be taking this article as "do anything it takes to ship" and saying that's a horrible attitude.
Your comment is the first I've seen that seems to be more along my understanding of the piece. Duct Tape Programming is about getting what is needed done and building from there.
"I need a website that lets people share videos".
So what do you do? Do you make a little site that serves flash videos? That's Duct Tape Programming.
Making a little site that takes videos and catalogs them and tries to analyze them for similarity and has editing tools and needs to be able to scale to 20 computers and... That's the problem.
When you start your site, it's OK to have it not be able to instantly scale out to 10,000. Sometimes it's better to get the basic features there and build them up and fix them as you go. Not everything needs to be there from day one. Not everything needs 3 layers of abstraction because it's "what people do".
As your program goes on, you clean it up, add abstractions where needed. The first version of Word for Windows didn't look ANYTHING like the current version. If you are going to make a new word processor, you go after the old version, not aim at the sky.
Your understanding of his post agrees with mine. This isn't about a system to last 20 years, this is about a system to fix things NOW while you make it better so your users don't have to keep doing things by hand for 6 months while you try to figure out why your framework build on another framework isn't interacting correctly with some other thing.
On the first page it explains all the conditions that must be met for this thing to go off. They include:
It's not automated. All it does it make sure someone is always able to fire the nukes, no matter which parts of the country get bombed. If the US detonated some new bomb that removed all human life within Russian borders, down to 500 miles underground, this system wouldn't be able to launch because the guy with his finger on the button would have been vaporized.
Actually the idea in the article that it was to keep the USSR generals and stuff from doing stupid things like launching first attacks because it would make sure they could always strike back was quite interesting.
At this point, the thing that would worry me most is that it's sounds like it's targeted at the US. So if some group in Afghanistan decides to take revenge for their war 2-3 decades ago (or N.K. attacks to prove they're cool, or...), then if this system enables the button the terrified guy at the button can fire back in defense... which would promptly attack the US because in panic he didn't realize that was who this was designed to defend against.
The article says there is a checklist he is supposed to follow too, but that's not a big comfort.
The headaches your job provides may end up being too much for the benefit. It may be worth it to people.
Even if you don't judge it worth leaving, are you telling me that if management was constantly saying "use X" when it's not even in the right class, you wouldn't prepare to leave when the opportunity came? You don't want to have to fix problems that you predicted and warned against ahead of time forever.
Remember, you don't have to leave until you have a new job. You could slowly look on the sly for 6 months or a year.
Why not ask the teacher what it's being used for? I can think of a couple of things.
Just find out what they are using it for. If you are really paranoid, get the principal to sign some slip saying that can only use it for those purposes.
Not everything has to be sinister. This doesn't seem like any real invasion of privacy. Would you be worried if the kids were running on fancy treadmills that already do this anyway?
Knowing your heart rate can be an important thing in exercising.
True. But it would solve his "GNOME asks me about executing everything" problem.
Or at least it would if it worked the way I thought it did. Turns out you need to use the fmask option to hide the execute bit.
That way my immediate thought. It's a nice thing to do (compared to the "we own everything you type" option), but I figured this way simply because they are getting too many contacts from people's lawyers and want to put themselves in a position of lower risk.
Not that it stops screwballs from suing you. Google has been sued over stuff that has nothing to do with them because their search engine points to pages that say whatever.
If you don't want things to look executable, mount it with the noexec option (which you could put in fstab). That way nothing on the device, even with FAT, will appear executable.
Since you are moving the files between computers, is the permissions loss really a problem? Aren't you just going to copy things off anyway?
If you need to limit access to certain users, you could use encrypted loopback file systems. But really, why not just use separate USB keys for different sets of permissions.
FAT is a lowest common denominator for a reason. If you want to interact with Windows, your only other real choice is NTFS, which isn't a bad option.
Sure you could use Ext3, or Reiser, or BTFS, or something else, but then you can't use your flash drive on any machine, thus defeating it's purpose.
Instant. I can the text on the page as I'm turing it. If someone is interrupting me and I have to re-read the last paragraph on the last page because I forgot it, I can do that really fast on real book.
With eInk, you have to put up with the switching delay.
I know they're getting better, but it is an issue right now.
I think a big part of the problem is that the full screen has to turn one color then the other to prevent ghosting. That effectively doubles refresh time and that "flash" makes it much more noticeable than if, like the LCD I'm typing on right now, it only switched the pixels that changed.
eInk works great once you have the page displayed, especially if you have a large screen. Wouldn't something iPhone sized (or a little bigger) with an eInk screen be pretty great? Imagine the batter life! But all the page refreshes would make it rather annoying to use.
If we could get something with a refresh rate akin to an old passive matrix LCD, we'd be in good shape. What was that, 50ms or so?
We had that discussion. In fact, that story was posted just 26 hours before this one.
We know Apple wouldn't let them do this. It's the same as it was when Apple first announced the rules for making applications. It's the same reason you can't sell Python. You can't let users program the phone. This is because Apple is careful, evil, protecting a sandbox, just a jerk, blah blah blah.
We've had it all out before. We had it out 26 hours ago. This story wasn't useful. This is the kind of story that used to go into the quickies updates, because that's all it is, a one line update.
This is a non-story. They weren't allowed to sell the app because it had BASIC. They snuck BASIC in, and Apple pulled it since they weren't allowed to sell it.
This is not news.
We don't need the "Apple should allow..." discussion. We had that 2 days ago when this was approved. And the last app that did something. And two before. And the next one.
This isn't a story. "Apple does exactly what it said it would." Call CNN.
I don't support it at all. I think it's a horrible idea for the US to get single payer healthcare.
I'll grant you the idea isn't bad. I just don't trust the government enough to do it. I'm not some anti-government nut, but let's look at some of their track record:
Basically, I don't trust that this won't become another giant mess of regulation and debt that we can't get out of. If they fixed Medicare or Social Security and it actually worked, they'd have credibility. As it is, this just seems like a chance for a giant boondoggle.
Don't forget the fun regulation that comes with government regulations. When my grandmother died, her life insurance was enough that my grandfather would have been pushed out of Social Security, his only means of support. So he had to spend it in one of the ways that was approved. He bought a new car.
He could have saved that money, used it to make his retirement more comfortable, or to pay medical bills that would inevitably happen later.
Instead he had to buy a new car (other choice: buy/fix home, may be others) so he wouldn't get kicked out. But it wasn't enough money for him to live off of for even a year, so he had to comply.
Fun stuff, those government regulations.
Giant entitlement debt ridden morass of weird regulations. That is what the current track record leaves me to expect, and I don't want it.
Fix medicare, make it solvent. Or SS. Once they have that record that they can actually run a program like this, we can talk about single payer healthcare.
I see three possibilities. First, AT&T hasn't invested in their network enough. That's a given. Second, iPhone users are just network hogs, I don't think so.
So that leaves us with possibility three: the iPhone is the first phone that isn't an incredible pain to use.
I think that all other smart phones are artificially low in bandwidth usage because they're hard to use. The IE5 based browser on Windows Mobile (I know they recently improved it) in my experience was a total joke and almost unusable. The browser on BlackBerries, in fact the UI as a whole, is not designed to ease of use at all, it's "here's an empty button we can use". That only really leaves non smart phones, and even IF you had a data plan, I'm sure we all know how easy browsing with those things was.
Basically the iPhone is the first device it's possible to easily surf the web without wanting to throw the phone into a wall.
When you give your customers something that actually works and is usable... they use it.
Go figure.
I don't know, go ask Mr. Owl.
I'm a fan of Gruber, which may be why.
I realize the benefits of Android, they're quite clear. I would have loved something like Android before I got my iPhone.
I just worry the G1 hasn't made much of a splash, and if the other phones coming don't, I wouldn't put it past the carriers to say "We don't want another Android phone, those don't sell well." I worry that Android won't get the chance it should because it's not attached to a better phone. If things had started with 3 phones, I'd think of it in a better position.
Next year will be the big year. That's when we will see what happens. But the cell phone market (at least in the US) has it's priorities so strange (usability? What's that?), I'm not sure this approach is going to work.
I was referring to the market for physical phone it's self, not the app market. I really don't know the state of the Android app market (other than it's bigger than the Pre's, which is not hard to do).
Where is the market? AT&T has the iPhone, the phone. The one everyone wants to beat.
Sprint has the Pre. It's a pretty decent phone with a few build quality issues. Once Palm gets a brain and starts letting apps come out, it could be pretty good.
Verizon has... who knows. Standard Blackberries?
And then there is little T-Mobile with.. Blackberries.
I don't remember seeing many (any?) ads for the G1. I don't remember anyone talking about it except release day calling it "the google phone" when it's not Googly in any way. Basically, not many people care, because I don't think many people know about it. My boss has one, and it's quite nice. But it has no mindshare.
Why should it? It doesn't have an amazing app store (like the iPhone). It doesn't have sexy hardware (like the iPhone or many imitators). It doesn't have an amazingly cheap price. There is nothing to stand out about it other than running "google OS". And since Android doesn't have a reputation yet, that doesn't sell phones.
Great apps would help, but people won't build those until the thing is more popular. Better hardware would help a little so it doesn't look so blocky (the G2 should help here).
Microsoft has this same problem. When Apple wants the hardware to do something, it builds it. When Microsoft wants it, they push and prod and within a few years it happens. Dell (et all) don't make sexy computers, or at least didn't start until after years of Apple taking the "good looking" market.
Android could be something great, even if it takes the "low end smartphone" market. But it could take years to get there, and companies may not be willing to wait that long. If Google had taken some of the risk and co-developed a phone (a Honda or Acura to Apple's BMW, instead of the Ford Focus we got) Android could be in a better spot.
But the Pre is the weakest right now, in my eyes. They've had months and released almost no apps. You know what they just released in the last week or two? Out of the 4 or 5 apps, two were to help people with Jewish observances. Not exactly "phone moving" applications. Floodgates may not open until Christmas or later, and without some lower-level stuff there might not be good games. Some strong funded development in apps and some marketing could really help Android. More phones certainly would.
The question is, will this be the next DOS/Windows (good enough, builds up to dominance), or OS/2 (better than the common, but never achieves critical mass and becomes irrelevant)?
How about a series of ads showing how easy it is to navigate/use the phone, compared to the nightmare of a UI that Blackberries use? Aim for that market. Aim for consumers (not necessarily businesses) who want a smartphone, but don't want and iPod.
Of course, I wouldn't want to fight against a $99 iPhone. The only reason that thing hasn't destroyed the market is it's tied to AT&T.
It was 10.1 which was free, sort of a thank you gift to everyone who used 10.0. I remember using 10.0 on my brother's Mac. It was neat, but it was quite slow and bloated feeling compared to OS 9.