MS has been very mum on Longhorn so far, they haven't talked about what features they're adding past what they need to tell developers. By the end of this year we should have an idea of what the major features will be, what the marketing push will be, and if it will be worth it as a result.Originally posted by: Link19
Considering the fact that they've made a Windows XP 64 which just went RTM, what point is there in upgrading to Longhorn next year? What other features is it going to have besides just more BLOAT, idiot user treatment and being a resource hog?
Originally posted by: ViRGE
MS has been very mum on Longhorn so far, they haven't talked about what features they're adding past what they need to tell developers. By the end of this year we should have an idea of what the major features will be, what the marketing push will be, and if it will be worth it as a result.Originally posted by: Link19
Considering the fact that they've made a Windows XP 64 which just went RTM, what point is there in upgrading to Longhorn next year? What other features is it going to have besides just more BLOAT, idiot user treatment and being a resource hog?
About the BLOAT, wouldn;t it be easier if we went only text based and the apps still can run in its current state? How's that for resource saving?
I second this, I think M$ needs to get some features out and all that. About the BLOAT, wouldn;t it be easier if we went only text based and the apps still can run in its current state? How's that for resource saving?
Look in to Apple's OS X 10.4(Tiger) some time, and read up on CoreImage; MS is looking at implementing some very similar features in to Longhorn.Originally posted by: Link19
I second this, I think M$ needs to get some features out and all that. About the BLOAT, wouldn;t it be easier if we went only text based and the apps still can run in its current state? How's that for resource saving?
That's not what I'm talking about. What I mean is more things stuffed into the OS that run on system startup by default and a more GUI animated desktop. I like a nice lokking GUI and click and point interface, but what we have now is fancy enough, and doesn't need to get any more fancy to add to the bloat. What's the whole point of releasing XP 64 if there aren't any programs that are going to take advanatge of 64-bit access to memory for quite some time? Miswell just wait for Longhorn 64-bit if it is still going to be a while before applications take advanatge of 64-bit access to memory. That is why I can see Longhorn being bloated and containing unnecessary features. Why else would XP 64-bit be released today and made to have a bright long future if Longhonr is going to be the OS of the future for 64-bit computing?
What's the whole point of releasing XP 64 if there aren't any programs that are going to take advanatge of 64-bit access to memory for quite some time?
To give developers a 64-bit Windows platform to develop on, you can't have 64-bit apps until you have a 64-bit system to run them on. But even so most apps will hopefully never be 64-bit because there's no reason for them to be, for instance what would Word need >4G VM addressing for? Things like databases, 3D renderers, etc that actually need the additional VM are already 64-bit on unix so very little will change with the release of XP64 other than many people crying that they can't find 64-bit Windows drivers. Eventually games will probably have 64-bit releases but I doubt that'll happen soon either because they'll still need 32-bit versions for compatibility purposes.
So, does that mean that there is absolutely no benefit to developing 64-bit applications unless you have more than 4GB of RAM in the system? Because 32-bit applictaions can access up to 4GB of RAM? So would a 64-bit application have no performance advanatge over a 32-bit application unless you have more than 4GB of RAM?
Well, when you put things in perspective on the x86 side, we jumped to 32bits in 1985(386), and didn't make another jump until nearly 20 years later. This time around we're adding twice as many bits, so it should in theory take us twice as long(40 years) to outgrow 64bit addressing.Originally posted by: bsobel
So, does that mean that there is absolutely no benefit to developing 64-bit applications unless you have more than 4GB of RAM in the system? Because 32-bit applictaions can access up to 4GB of RAM? So would a 64-bit application have no performance advanatge over a 32-bit application unless you have more than 4GB of RAM?
No, there is no where near 2 gig of contigous address space available to apps. As an industry it will start being used, and products will come out that no-one here will expect (people said we didn't need 32bit addresssing too!). The 64bit address space should keep us busy for the next decade possibly two.
Bill
Well, when you put things in perspective on the x86 side, we jumped to 32bits in 1985(386), and didn't make another jump until nearly 20 years later. This time around we're adding twice as many bits, so it should in theory take us twice as long(40 years) to outgrow 64bit addressing.
But it isn't linear growth, it's exponential. The average RAM configuration doubled nearly every 12-18 months; which is why we burnt through 32bit space in 20 years. At that same rate, it would take 40 years to burn through 64bit space, so the only way we can burn through 64bit space any faster is to end up on a 8-12 month timeline, which I don't see happening. I actually think it's more likely that 64bit space will last longer than 40 years, but we'll see.Originally posted by: bsobel
Well, when you put things in perspective on the x86 side, we jumped to 32bits in 1985(386), and didn't make another jump until nearly 20 years later. This time around we're adding twice as many bits, so it should in theory take us twice as long(40 years) to outgrow 64bit addressing.
That presumes the industry has grown linerally, it hasn't...
Bill
But it isn't linear growth, it's exponential. The average RAM configuration doubled nearly every 12-18 months; which is why we burnt through 32bit space in 20 years. At that same rate, it would take 40 years to burn through 64bit space, so the only way we can burn through 64bit space any faster is to end up on a 8-12 month timeline, which I don't see happening. I actually think it's more likely that 64bit space will last longer than 40 years, but we'll see.
So, does that mean that there is absolutely no benefit to developing 64-bit applications unless you have more than 4GB of RAM in the system? Because 32-bit applictaions can access up to 4GB of RAM? So would a 64-bit application have no performance advanatge over a 32-bit application unless you have more than 4GB of RAM?
Well, when you put things in perspective on the x86 side, we jumped to 32bits in 1985(386), and didn't make another jump until nearly 20 years later. This time around we're adding twice as many bits, so it should in theory take us twice as long(40 years) to outgrow 64bit addressing.