You write "can't even" like acid2 is critical or trivial. It exercises part of the CSS standard that Firefox has trouble with, but that does not mean Firefox's CSS support is no better than IE's.
Applications have been written to support context menus by holding the control key down while clicking since 1997. The second button required a custom mouse driver (which was available) until Mac OS X. But putting a one button mouse in the box by default meant that applications had to support single button mice, too.
This new mouse probably defaults to single button mode until its set up. Hopefully the setting is per user, not system-wide. I don't actually plan on setting up a "second" mouse button on mine... I use Exposé a lot more than context menus.
Yeah, what you said. The last major improvement in Codewarrior was the ability to open multiple projects at once. I asked for a Delete Line command back with Codewarrior 7 Gold (1994-ish), Codewarrior Pro 8 still didn't have it. Anyone who didn't notice the writing on the wall years ago has been living in a happy, happy fantasy world.
I agree with you completely. If they'd had a marketing partner like Sony (or maybe Apple), things would have been different. I don't think any of amount of marketing under under their own name would have made a difference, though.
I thought the main thrust for lift-off came from the booster tank's engines? Like this. I figure a redesigned booster could make up for the lack of the shuttle's engines on lift-off.
If not, I'll grant you it is the stupidest idea of all time. But hey, this is the reason I don't work for NASA. Smarter minds than me are on this problem!;)
I don't really want to post this for fear of being modded a troll, but comparing Firefox 1.0 and Internet Explorer for Windows on a low end system is no contest: Internet Explorer is much faster. Firefox frequently chews up a lot of processor time during mouse movement (for instance, mousing over controls in the Downloads window), whereas Internet Explorer barely takes a hit. I didn't notice a lot of difference one way or the other anywhere else, though.
I'm pretty sure it's a bug and it'll get fixed, but still, it isn't what I expected at all.
I'm not sure about that, but there's other ideas. For instance, there's the booster and the shuttle. The problems are caused by the booster being beside the shuttle. How much work would it take to put the majority of the booster UNDER the shuttle instead and make as few changes as possible to the shuttle?
Okay, sure, we're no longer talking about a minor fix. But neither is it scrapping everything... there IS a middle ground here.
PalmSource can be summed up on one word: irrelevent.
The total number of devices shipping with a "next generation" Palm OS is 0. Very shortly, PalmSource is not even going to be using Palm in their name.
Now, if Palm (formerly PalmOne) was going Linux, this would be a big deal. But PalmSource is just building software or the sake of building software, not for the purposes of having it used by anone in the world.
I actually never played with MSN's offering long enough to notice that -- it is a Microsoft thing, after all, and thus I avoid it by default until shown I should do otherwise.:)
Considering I live outside the US, this shows you how little I played with it.
I don't think anyone thinks it is a conspiracy. It's just really amusing to see that MSN's Virtual Earth is apparently using images that are over ten years old.
I dunno. Apparently they're predicting the locations of professors. That's a lot harder. (I'm assuming the predictions are more specific than "Not in class.")
If you continue reading, you'll discover this is not a Macintosh specific problem. This data integrity problem is part of the drive hardware -- every drive -- not part of the Macintosh.
Every operating system faces this tradeoff. If you pull a power plug, your odds are about 50% of reproducing an out-of-order, partial commit. Mac OS X is the only known operating system to pick data integrity over speed.
Personally, I think this tradeoff should be left up to the user. Seems a UPS would solve much of this. It also seems like the world needs a permanent solution, which would probably be for a capacitor every hard drive with enough power to commit whatever is in the cache.
It might be an issue later, but I've seen a huge increase in the number of customers checking things out at the local dealer. Seems counter intuitive to me...
The reported threading problems were not, in fact, threading problems at all. Instead, they are the result of F_FULLFSYNC fcntl. You will probably find this thread interesting.
At the time (June 2003) it was pretty decent -- slower for some things, faster for others. But it's been two years now with no significant progress (2.0 GHz-> 2.7 GHz), so yeah, it's pretty long in the tooth now.
It's also worth noting that most of the motherboard components have also stayed the same. Not much point in tuning that when the processor has changed so little.
Imagine what the difference will be like in late 2006 with the transition well underway.
I believe it's plain old x86, which makes it even more impressive. Remember the first lines to have a brain transplant scheduled are the lower-end lines which are currently 32-bit. This makes the most sense if the transition is to a 32-bit platform.
Well, the security patches go back to 10.2, which is the first modern Mac OS X. 10.0/10.1 machines should definitely be upgraded that far at least. I understand that may not be an option for you, but it is a fair time back.
Apple's feature additions are usually pretty modest. In fact, this widget manager is the first I can really think of for an 0.0.1 release, and it's arguably a security fix...
But yes, it would be nice if you could get the security fixes without the bug fixes.
You write "can't even" like acid2 is critical or trivial. It exercises part of the CSS standard that Firefox has trouble with, but that does not mean Firefox's CSS support is no better than IE's.
Just curious -- where'd you read that you can't click them both at once?
Applications have been written to support context menus by holding the control key down while clicking since 1997. The second button required a custom mouse driver (which was available) until Mac OS X. But putting a one button mouse in the box by default meant that applications had to support single button mice, too.
This new mouse probably defaults to single button mode until its set up. Hopefully the setting is per user, not system-wide. I don't actually plan on setting up a "second" mouse button on mine... I use Exposé a lot more than context menus.
Yeah, what you said. The last major improvement in Codewarrior was the ability to open multiple projects at once. I asked for a Delete Line command back with Codewarrior 7 Gold (1994-ish), Codewarrior Pro 8 still didn't have it. Anyone who didn't notice the writing on the wall years ago has been living in a happy, happy fantasy world.
I agree with you completely. If they'd had a marketing partner like Sony (or maybe Apple), things would have been different. I don't think any of amount of marketing under under their own name would have made a difference, though.
I thought the main thrust for lift-off came from the booster tank's engines? Like this. I figure a redesigned booster could make up for the lack of the shuttle's engines on lift-off.
If not, I'll grant you it is the stupidest idea of all time. But hey, this is the reason I don't work for NASA. Smarter minds than me are on this problem! ;)
I don't really want to post this for fear of being modded a troll, but comparing Firefox 1.0 and Internet Explorer for Windows on a low end system is no contest: Internet Explorer is much faster. Firefox frequently chews up a lot of processor time during mouse movement (for instance, mousing over controls in the Downloads window), whereas Internet Explorer barely takes a hit. I didn't notice a lot of difference one way or the other anywhere else, though.
I'm pretty sure it's a bug and it'll get fixed, but still, it isn't what I expected at all.
But if you get more and better results than someone else who is doing the same thing you get paid more than they do, even if it took you less time.
Not only that, but often if you get the same results you get paid more than the other person because you took less time.
Knowledge is power, and speed is money.
I'm not sure about that, but there's other ideas. For instance, there's the booster and the shuttle. The problems are caused by the booster being beside the shuttle. How much work would it take to put the majority of the booster UNDER the shuttle instead and make as few changes as possible to the shuttle?
Okay, sure, we're no longer talking about a minor fix. But neither is it scrapping everything... there IS a middle ground here.
I'm not really sure I understand. Unless they're actually lifting money into orbit or offshoring the design, the money is being spent in the US.
I think you need to revisit your assumptions. I code only in C++ and have had no problem making Aqua-looking applications.
PalmSource can be summed up on one word: irrelevent.
The total number of devices shipping with a "next generation" Palm OS is 0. Very shortly, PalmSource is not even going to be using Palm in their name.
Now, if Palm (formerly PalmOne) was going Linux, this would be a big deal. But PalmSource is just building software or the sake of building software, not for the purposes of having it used by anone in the world.
BIOS would seem to still be a possibility, but Apple has already ruled out OpenFirmware.
I actually never played with MSN's offering long enough to notice that -- it is a Microsoft thing, after all, and thus I avoid it by default until shown I should do otherwise. :)
Considering I live outside the US, this shows you how little I played with it.
I don't think anyone thinks it is a conspiracy. It's just really amusing to see that MSN's Virtual Earth is apparently using images that are over ten years old.
I dunno. Apparently they're predicting the locations of professors. That's a lot harder. (I'm assuming the predictions are more specific than "Not in class.")
Xboxes have been sold as an Xbox/Xbox Live combo for a while, too. I'd like to hear how those are counted.
If you continue reading, you'll discover this is not a Macintosh specific problem. This data integrity problem is part of the drive hardware -- every drive -- not part of the Macintosh.
Every operating system faces this tradeoff. If you pull a power plug, your odds are about 50% of reproducing an out-of-order, partial commit. Mac OS X is the only known operating system to pick data integrity over speed.
Personally, I think this tradeoff should be left up to the user. Seems a UPS would solve much of this. It also seems like the world needs a permanent solution, which would probably be for a capacitor every hard drive with enough power to commit whatever is in the cache.
It might be an issue later, but I've seen a huge increase in the number of customers checking things out at the local dealer. Seems counter intuitive to me...
The reported threading problems were not, in fact, threading problems at all. Instead, they are the result of F_FULLFSYNC fcntl. You will probably find this thread interesting.
At the time (June 2003) it was pretty decent -- slower for some things, faster for others. But it's been two years now with no significant progress (2.0 GHz-> 2.7 GHz), so yeah, it's pretty long in the tooth now.
It's also worth noting that most of the motherboard components have also stayed the same. Not much point in tuning that when the processor has changed so little.
Imagine what the difference will be like in late 2006 with the transition well underway.
I believe it's plain old x86, which makes it even more impressive. Remember the first lines to have a brain transplant scheduled are the lower-end lines which are currently 32-bit. This makes the most sense if the transition is to a 32-bit platform.
Well, the security patches go back to 10.2, which is the first modern Mac OS X. 10.0/10.1 machines should definitely be upgraded that far at least. I understand that may not be an option for you, but it is a fair time back.
Apple's feature additions are usually pretty modest. In fact, this widget manager is the first I can really think of for an 0.0.1 release, and it's arguably a security fix...
But yes, it would be nice if you could get the security fixes without the bug fixes.
My apologies that I misunderstood your comment. :)
Java and C++ are different languages and have different uses. I'm not sure who you're trying to convince otherwise, or even why you're bothering.