Author Topic: Tim Sweeney thinks Windows 10 may break Steam  (Read 1542 times)

i seriously doubt microsoft is going to drop win32 support. that's not just going to affect steam, that's going to affect pretty much loving everybody who has develops for windows. i don't buy it, it would be a terrible business move. microsoft is generally somewhat obsessive about backwards compatibility as well, it would make zero sense for them to do this just to spite valve. valve isn't nearly enough competition for them to take such massive measures.

basically what otto said

Architecture compatibility is down to the manufacturers of the processors, not Microsoft. 16-bit was dropped in the x86 architecture and the only reason that Windows Vista/7 could support 16-bit applications was because it had an inbuilt subsystem for backwards compatibility which has since been dropped.

At this stage, comparatively few programs are designed for 64-bit, so there's literally no reasons to to kill 32-bit. Hell; most of the Windows 10 OS uses 32-bit services and applications, even if you get the 64-bit version.

Architecture compatibility is down to the manufacturers of the processors, not Microsoft. 16-bit was dropped in the x86 architecture and the only reason that Windows Vista/7 could support 16-bit applications was because it had an inbuilt subsystem for backwards compatibility which has since been dropped.

At this stage, comparatively few programs are designed for 64-bit, so there's literally no reasons to to kill 32-bit. Hell; most of the Windows 10 OS uses 32-bit services and applications, even if you get the 64-bit version.

this too

we aren't ready to kill 32 bit yet

32 bit is here to stay for a LONG time, believe me.

32 bit is here to stay for a LONG time, believe me.
i give it 3 days

i give it 3 days
so basically 32-bit is the opposite of jesus

it's not about money, it's about control
One store to rule them all, One store to find them,
One store to bring them all and in the darkness bind them

Architecture compatibility is down to the manufacturers of the processors, not Microsoft. 16-bit was dropped in the x86 architecture and the only reason that Windows Vista/7 could support 16-bit applications was because it had an inbuilt subsystem for backwards compatibility which has since been dropped.

At this stage, comparatively few programs are designed for 64-bit, so there's literally no reasons to to kill 32-bit. Hell; most of the Windows 10 OS uses 32-bit services and applications, even if you get the 64-bit version.
this has less to do with hardware and more to do with software. when you write an app for windows 10, now you have to decide whether to use the new UWP APIs or to stick with win32 APIs. my understanding is that the advantage of UWP is that it's designed to work across all compatible platforms in the same "device family", so ideally you won't have to create separate builds for each target because they all use one API set

https://msdn.microsoft.com/en-us/windows/uwp/get-started/whats-a-uwp

there's also an effort by microsoft to help developers convert their apps to UWP through "project centennial", but i doubt many are going to bite. it's a good idea, but it's going to take a while to shift over to a new standard

i give it 3 days
i give it 231-1 seconds (~68 years)

there's also an effort by microsoft to help developers convert their apps to UWP through "project centennial", but i doubt many are going to bite. it's a good idea, but it's going to take a while to shift over to a new standard
Their "universal" standard is stuffty. Not many are going to bite.

whoever thinks steam is actually going to be "broken" is flat out wrong