No one should ever force a service pack installation unless they're prepared to deal with the consequences if it goes wrong. Some people are stubborn.and Microsoft has no obligation to them a decade after the product launched. Microsoft had the appropriate expectation that Windows 10 would take over. Windows 10 isn't perfect by any means but Microsoft did the absolute best they could to unify past versions of Windows.and they gave it away free to boot. Windows 7 lacks the scaling features required for ridiculous high DPI displays.nevermind touch. At the same time, Windows 7 absolute sucks for devices like the Surface Pro with a near 4K screen in something like 13". Yes, Windows 10 isn't as good as Windows 7 for strictly mouse use. Stop messing about and let us gameĬlick to expand.Correct me if I'm wrong but isn't Windows 10 still the only operating system on the planet that is acceptable for both mouse/keyboard and touch screen support? That's what Windows 8 started by going full touch, then they pulled some Windows 7 mouse and keyboard up with the result being the merger that is Windows 10. MS should not want anything, they should be serving the market to their best ability and stop trying to redirect it all the time. That goes right up there in the top 3 along with using Internet Explorer so you can download another browser It was best described, I think, by the first measure gamers had to do when installing Windows 10: disable the Xbox Game DVR to prevent your games from crashing. And what happened to that Windows 10 anti-cheat measure? TruePlay? Its just another example in the near infinite list of MS and gaming failures. They 'wanted' an Xbox bundled only with Kinect and forcing an always online requirement. They want all sorts of things but the practical outcome is always a major letdown. They 'want' to unify Xbox and PC platforms, or at least to some degree bring them together. That started with bundling DX12 with Windows 10, look where we are today. what they want is often so far from reality, its downright crazy. Microsoft wants to retire D3D11 and older just as bad as they want to retire Windows 7 but they can't do that when so many people refuse to upgrade to Windows 10 so game developers are put in an awkward position of balancing priorities. Everyone should be targeting low level APIs (be it D3D12 or Vulkan) so this move is Microsoft trying to make that happen. so yeah.look at games like The Division where it claims to be DirectX 12 but there's no performance benefit really to speak of. This makes me think that Blizzard only pursued creating a D3D12 renderer because they got assurance from Microsoft that it will benefit Windows 7 gamers too. The low-level framework of D3D12 is not backwards compatible with Windows 7 which is stuck on D3D11. The prevalence of Windows 7 and the need to support it to maximize market exposure is prohibiting the adoption of D3D12. It is more like trying to take the shared DNA of one puppy out of all the puppies in the litter.I finally read this which contains a quote from presumably the Microsoft lead on this subject ("Max McMullen"). To take the Wine code out of ReactOS is not like taking one puppy out of a litter. Wine and ReactOS must solve some of the same problems, thus using select pieces of Wine code is helpful to the ReactOS project. This is another method that open source projects use when sharing code. Instead, ReactOS uses Wine code in bits and pieces. However, ReactOS does not use Wine's code that way. Some open source projects are built in that fashion, using another project's work as a subsystem to perform a distinct function or service for the project's own software. When we of the ReactOS community say that ReactOS uses Wine or (more accurately) that ReactOS uses Wine code, some of our readers naively conclude that there's a separate module/routine/subsystem in ReactOS marked 'Wine'. When the class was given a brief tour of the air-conditioned computer room, I asked "Where is the compiler?" (That was a very embarrassing mistake.) This description led me to (mistakenly) expect to see a box marked "compiler" attached to the computer. The instructor described how our student FORTRAN programs would (I paraphrase from memory) be read by the card reading machine, then sent to the compiler to be processed into machine code before being run on the computer. This happened back in the days of 'Big Iron', pre-Altair 8800. It is of course a wrapper that helps to maybe convert DirectX to OpenGL to Hardware.Īdcock's remarks remind me of the first formal programming class that I ever took. I did not try it (WineD3D/WineD3D panel) much.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |