Originally posted by AJSB
View Post
Announcement
Collapse
No announcement yet.
Valve Writes About Their Linux Client Plans
Collapse
X
-
-
Originally posted by gamerk2 View Post3: Installable media [Read: DVD] space limitations make it impossible to package both a 32 and 64 bit executable on a single disk. [Multiple disks raises costs]
Leave a comment:
-
I created an open source operating system group a little while ago, on steam, in preparation. Come join me! I said in the description even if you used a BSD form operating system you could still join. I read that they do have a Linux compatibility layer and will work with almost all Linux software so I'm not fully sure if it will work on their but if it does then they can join too.Last edited by Spectre; 17 July 2012, 01:00 PM.
Leave a comment:
-
Originally posted by gamerk2 View PostIn any case, its sounding like MS plans to kill 32-bit support after Win8, so we should see a transition to 64-bit once MS officially confirms that fact. Only question is whether MS will keep WOW32 in place...
Leave a comment:
-
Originally posted by Kristian Joensen View Post"Around 1.5 to 2GB, depending. Varies a LOT by game though. Still, 1.5GB is 16% of your total disk capacity."
Of executables?????
I'm saying that the 32-bit situation is a mess on Windows
At the end of the day, there currently is no financial reason for developers to work on a separate 64-bit executable. Period. If the toolchain supports it, then you might see one spat out, but for most developers, this isn't the case. Same reason why the primary OS target is still Win XP/DX9: Developers do not want to lock out large portions of the market, even if those portions are less likely to purchase their product.
In any case, its sounding like MS plans to kill 32-bit support after Win8, so we should see a transition to 64-bit once MS officially confirms that fact. Only question is whether MS will keep WOW32 in place...
Leave a comment:
-
Originally posted by gamerk2 View PostPutting aside that not all people who buy games are gamers (shocking, I know), why should 10% of the gaming market be ignored, when there is no financial downside to sticking with 32-bit? Try pitching that to upper management some time.
One, I doubt any major game development company is using DMD as their compiler. [Heck, I'd wager 90% of them use MS Visual Studio].
Two, the library tool chain is up to the developers to re-design for 64-bit support. Compilers and the OS libraries have supported 64-bit without issue for quite some time now. Its an issue with the developers, no the OS itself.
GB, or at a bare minimum, a few hundred MB. Try fitting an extra GB onto a DVD9 thats already filled with 8.8GB of data. Woops, can't fit the 64-bit .exe onto the disk, and it doesn't make financial sense to ship a second disk just for a 64-bit .exe.
Your point being? I'm saying that the 32-bit situation is a mess on Windows and not a mess on Linux, not necessarily that it has something to do with the respective kernels.
Oh? The whole binary content of 64-bit UT2004 takes exactly 9.2 MB.
Leave a comment:
-
"Around 1.5 to 2GB, depending. Varies a LOT by game though. Still, 1.5GB is 16% of your total disk capacity."
Of executables?????
Leave a comment:
-
Originally posted by Kristian Joensen View Post"3: Installable media [Read: DVD] space limitations make it impossible to package both a 32 and 64 bit executable on a single disk. [Multiple disks raises costs]"
Could you elaborate on this please? As far as I know executables usually don't take up much space.
Originally posted by GreatEmerald View PostCan't agree with your first point. It was true in 2004 (and even then some games of the era have 64-bit versions), but definitely not now. There was a post over on Stardock blog asking about what machines people use, and 32-bit only machines were 10%, if even that.
Putting aside that not all people who buy games are gamers (shocking, I know), why should 10% of the gaming market be ignored, when there is no financial downside to sticking with 32-bit? Try pitching that to upper management some time.
The second point is pretty much what I meant. There are some compilers that don't support 64-bit as well (DMD, for instance), but there are also many 32-bit only libraries. However, that is definitely not the case on Linux!
Two, the library tool chain is up to the developers to re-design for 64-bit support. Compilers and the OS libraries have supported 64-bit without issue for quite some time now. Its an issue with the developers, no the OS itself.
And can't agree with your third point. DVD space is used by texture, sound and model data, not programming of any kind. A few more MBs wouldn't make any difference.
Leave a comment:
Leave a comment: