Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
NathanE said:That's not true though is it. The problem has many factors and lazy software developers is quite high up the list of reasons.
C and C++ aren't modern. These languages do require a certain amount of code changes to get the best out of 64-bit.Hades said:In the vast majority of instances it is the compiler which makes the decision on how to handle numbers. The programmer has very little to do with it. If software was written in Assembler then it would. But with modern languages such as C, C++, Java, C#, etc, there is not much the programmer can do other than choosing the datatype - and if a large datatype is needed then it will be chosen usually irrespective of 32bit / 64bit environment.
An example? Like changing index data structures to use 64-bit pointers so they can properly take advantage of x64's enhanced memory space. That's where I'd probably start anyway. Do a few Google searches and you'll find plenty of ideas for optimising your code for x64.Hades said:C++ and C being "modern" was in relation to Assembly. So could you give an example of where the programmer can make a big difference to the execution speed of code by refactoring from 32 bit to 64 bit on a 64 bit system?
That's wierd because most OS critics agree that XP X64 is the most stable and performant at the present time for AMD64. Have you seen the state of the Linux codebase to actually make any real comment on that last point?FrankJH said:and lets face it, MS has never been the best at optimizing code (after all the majority of home users who are using 64 bit os will be using windows, even though a Linux distribution would probably work "faster" and more optimally depending on what you are doing)
Win XP 64 is a step in the right direction, but its still relative bloatware and the OS is where you have to start before even considering drivers etc etc before the applications / games last of all (imo)
NathanE said:That's wierd because most OS critics agree that XP X64 is the most stable and performant at the present time for AMD64. Have you seen the state of the Linux codebase to actually make any real comment on that last point?
Also if driver developers want to get WHQL signing their Vista drivers must be a dual 32-bit and 64-bit package. Both of which will undergo testing. So in a couple months the 64-bit driver issue will be well on its way to being solved.
NathanE said:That's wierd because most OS critics agree that XP X64 is the most stable and performant at the present time for AMD64. Have you seen the state of the Linux codebase to actually make any real comment on that last point?
Also if driver developers want to get WHQL signing their Vista drivers must be a dual 32-bit and 64-bit package. Both of which will undergo testing. So in a couple months the 64-bit driver issue will be well on its way to being solved.
Whatever I don't know enough about the alternatives on this matter to make any worthwhile replyFrankJH said:Surely thats comparing Windows XP 64 to any other OS - rather than XP to itself - ie how it could be written if done better more streamlined?I was talking in generla though in regards to MS software as one entity where their applications /OS / games while reliable arent always as lean as they should be
This is just from what I have read and installed over 20 years experience in building pc's and knowing about IT in general - just my opinion mind
MS is often bloatware
Depending on the distribution Linux can be as bad, and can be a lot better. At least Linux works from the opposite direction and you can choose never to install stuff, or just install what you want, Windows as far as I have ever seen to start with you always have to install everything and then take out or uninstall a lot of ****
Yup it's compulsory. If they want a WHQL certificate then it has to be a working dual 32-bit and 64-bit driver package. Both drivers of which must past the tests. I agree it definately is good news and it too caught me by surprise a couple months agotomos said:i had no idea that WHQL will *demand* they be written for both. i want to run the 64 bit vista Ed next year sometime and this is good news.
this doesnt mean apps will work tho does it? afaik 32bit apps wont work in 64bit vista
NathanE said:An example? Like changing index data structures to use 64-bit pointers so they can properly take advantage of x64's enhanced memory space. That's where I'd probably start anyway. Do a few Google searches and you'll find plenty of ideas for optimising your code for x64.
NathanE said:Yup it's compulsory. If they want a WHQL certificate then it has to be a working dual 32-bit and 64-bit driver package. Both drivers of which must past the tests. I agree it definately is good news and it too caught me by surprise a couple months ago
NathanE said:Whatever I don't know enough about the alternatives on this matter to make any worthwhile reply
Yup it's compulsory. If they want a WHQL certificate then it has to be a working dual 32-bit and 64-bit driver package. Both drivers of which must past the tests. I agree it definately is good news and it too caught me by surprise a couple months ago
32-bit apps will work just fine. Well, 95% of them - and average joes won't really encounter the 5% that don't.