Wonder what kind of racial new features they might pack into 10.7.
The only difference between Apple and Microsoft is that Microsoft's platform has a MUCH better 64-Bit support than Apple's platform.
As they are both currently in transition it's kind of hard to compare those 2 strategies right now. But in 2 years I think that Microsoft's way is going to seem like a mistake when they're still trying to juggle 2 different systems and forcing the user to decide which one to get.
And why is that? Windows 7, like Vista and XP before it, will be available in both 32-bit and 64-bit versions. The only difference between Apple and Microsoft is that Microsoft's platform has a MUCH better 64-Bit support than Apple's platform, especially when we are talking about hardware drivers. And unlike Apple, Microsoft does not switch their targeted hardware platforms every two years while at the same time abandoning the 'older' architectures.
Nobody says that's how it's going to be. John simply says this would have a lot going for it (and I agree)I don't know if I like that how OS X is going to be in a cycle of new features, then a new version that is just refinements.
with no need to refine, because the features should be optimized already
Apple should just make every new feature with its best software team and leave no room for unnecessary or inefficient code.[/quotemsg]
You quite clearly aren't a programmer, I fear.
What the… have you even read the review? Do you really think Siracusa could get 23 pages (his longest OSX review to date) on a point-number release?I somehow doubt they will "tick-tock" since this update was only above 10.5 due to dropping support for older architecture. It it was mere refinement, I bet it would have been just another point-number version.
A tick-tock cycle doesn't in any way, shape or form require dropping hardware. And dropping which hardware to start with? 10.7 might kill 32bit altogether (though I doubt it, that'll probably be for 10.8 around 2011-2012) which corresponds to the first 6 months of Intel-based macs, but then what are you going to drop? Everything since is EMT64…If Apple will "tick-tock" every 3 years and drop support of hardware only 3 years old, I'd be pissed. That would be death to Apple. If they use a "tick-tock" method of release to merely gain a few extra bucks every 36 months, it might not be so bad if the upgrade is worth it...
Ugh no. The 20+ months between Leopard and SL were already far too much.In my opinion, I it would be nice if Apple was more like MS in the way where instead of putting out a new major version of the OS every 12-18 months, they took maybe 3 years between each version.
I guess it's due to 2 reasons:And why is that?
- 32-bit Windows processes can only have 2 to 3 GB of virtual memory due to the kernel sharing the address space with the process. OSX 32bit processes get 4GB.
- While PAE is enabled on Windows 32b, the maximum "visible" memory is still limited to 4GB (so having 6 or 8GB of RAM in a 32b windows machine wastes them). In OSX, PAE is enabled with no limitation so you get (and use) up to 32GB of RAM (note: processes and kernel are still limited to 4GB of VMEM)
Wait what?And unlike Apple, Microsoft does not switch their targeted hardware platforms every two years while at the same time abandoning the 'older' architectures.
68000 from 1984 to 1996
PPC from 1995 to 2006
x86 from 2006 onwards
Those cycles are more than 10 years long, hardly "every two years"…
If you're ok with Leopard and you don't really want SHINYYYYY new SL, I recommend that you wait for 10.6.1.I haven't upgraded yet.. My Mac runs great as it is. Im still thinking about the doing the upgrade.
I remember when Windows XP came out and I had to upgrade a few computers and all the hell windows gave me just to do a stupid system upgrade... I guess windows has burned nightmares into my head. I doubt that I would have any problems with the snow leapoard...
I'm fairly happy with SL so far, but the software breakage annoys me (a lot of macports ports don't build anymore) and I've had pretty severe stability issues with Mail during the weekend (no data loss, but…).
Apple apps stability will probably be fixed with 10.6.1, and third-party app compatibility is resolving itself slowly (MenuMeters is already back)
Whatever. Too long, did not read.
Press and hold '6' and '4' on the keyboard during boot-up to boot into 64-bit mode. Only works on "newer machines," whatever that means.
OS X 10.7 - Black Panther?
And unlike Apple, Microsoft does not switch their targeted hardware platforms every two years while at the same time abandoning the 'older' architectures.
I have not seen Apple changing architectures every two years.
Nobody says that's how it's going to be. John simply says this would have a lot going for it (and I agree)
with no need to refine, because the features should be optimized already
Apple should just make every new feature with its best software team and leave no room for unnecessary or inefficient code.[/quotemsg]
You quite clearly aren't a programmer, I fear.
What the… have you even read the review? Do you really think Siracusa could get 23 pages (his longest OSX review to date) on a point-number release?
A tick-tock cycle doesn't in any way, shape or form require dropping hardware. And dropping which hardware to start with? 10.7 might kill 32bit altogether (though I doubt it, that'll probably be for 10.8 around 2011-2012) which corresponds to the first 6 months of Intel-based macs, but then what are you going to drop? Everything since is EMT64…
Ugh no. The 20+ months between Leopard and SL were already far too much.
I guess it's due to 2 reasons:
- 32-bit Windows processes can only have 2 to 3 GB of virtual memory due to the kernel sharing the address space with the process. OSX 32bit processes get 4GB.
- While PAE is enabled on Windows 32b, the maximum "visible" memory is still limited to 4GB (so having 6 or 8GB of RAM in a 32b windows machine wastes them). In OSX, PAE is enabled with no limitation so you get (and use) up to 32GB of RAM (note: processes and kernel are still limited to 4GB of VMEM)
Wait what?
68000 from 1984 to 1996
PPC from 1995 to 2006
x86 from 2006 onwards
Those cycles are more than 10 years long, hardly "every two years"…
If you're ok with Leopard and you don't really want SHINYYYYY new SL, I recommend that you wait for 10.6.1.
I'm fairly happy with SL so far, but the software breakage annoys me (a lot of macports ports don't build anymore) and I've had pretty severe stability issues with Mail during the weekend (no data loss, but…).
Apple apps stability will probably be fixed with 10.6.1, and third-party app compatibility is resolving itself slowly (MenuMeters is already back)
you can use more than 4GB of RAM on x86 Windows, but the application has to be coded for it and there are limitations. we used to run SQL Server with 8GB of RAM since 2002 and it would only store cached execution plans past 4GB. MS Exchange which is just MS Access on steroids had no support for PAE and you couldn't use it until Exchange 2003 SP2.
right now we run SQL with 32GB of RAM on most servers, one has 64GB. once 64GB comes down in price to $1500 or so we'll upgrade a few servers. New low end cheapo HP servers support up to 192GB of RAM and it will probably go up 50% to 100% by early next year
Apple could conquer if they made an iWeb program that wasn't so stiff and bloated: something even more versatile for the average person and business owner. The web programming is too complex for average neophytes, and takes too long to study and learn if you are busy doing other things like running a business. iWeb is a great baby step in a lucrative direction, but I doubt Apple will grab hold of that market because they are focused on devices and OS at this time.
Interesting. I doubt they'll do a tick-tock release of OS's though.
It was pure marketing hype (and lies about being "the first 64-bit desktop") when the G5 was released.
The version of OSX that shipped with the G5 had *no* 64-bit capability, so when the first G5s shipped there was no 64-bit software.
The next version of OSX added minimal support for command (terminal.app) applications to use 64-bit addresses.
Wonder what kind of racial new features they might pack into 10.7.
Whatever. Too long, did not read.
... But in 2 years I think that Microsoft's way is going to seem like a mistake when they're still trying to juggle 2 different systems and forcing the user to decide which one to get.
Right now no average users are really thinking about 64 bit on either platform. In 2011 I predict that Apple users still won't be thinking about it (the transition will go unnoticed by most) but your average Window user will finallyl be thinking about it, but in a confused way, not in a good way.
I guess it's due to 2 reasons:
- 32-bit Windows processes can only have 2 to 3 GB of virtual memory due to the kernel sharing the address space with the process. OSX 32bit processes get 4GB.
- While PAE is enabled on Windows 32b, the maximum "visible" memory is still limited to 4GB (so having 6 or 8GB of RAM in a 32b windows machine wastes them). In OSX, PAE is enabled with no limitation so you get (and use) up to 32GB of RAM (note: processes and kernel are still limited to 4GB of VMEM)
Actually if you'd check you'd find that a large percentage (perhaps a majority) of the desktops and laptops at Best Buy and Fry's are already Vista x64. (Any system with 4 GiB of RAM will be x64, and many of the 2 GiB and 3 GiB systems have x64 so that RAM can easily be expanded.)
When Windows 7 systems come out next month, expect to see most of them running x64.
You don't find these 2 sentences funny next to each other?
We're here!
Except not really!