Live data from Hacker News

Dvxk: A Vulkan-Based D3D11 Implementation for Linux with Wine

github.com

21–30 of 52 posts

Re: Dvxk: A Vulkan-Based D3D11 Implementation for Linux with Wine

#21
post #5

Earlier quoted context omitted.

Win32 is going the way of Carbon even if it takes a couple of years more, like it or not. Desktop bridge is just a migration tool to migrate Win32 into the store, and help developers slowly migrate parts of the apps into UWP ones. The majority of new APIs are UWP only, with userspace drivers, DirectX 12, ReFS being the notable exceptions. Of course you can always switch to GNU/Linux for Vulkan games.

> Win32 is going the way of Carbon even if it takes a couple of years more, like it or not. That's the thing, nobody likes it. They've been pushing "modern apps"[1] since 2012 and nobody notable is writing them. As Surface RT showed in the market, when forced to make the choice people will just abandon the product rather than put up with that mediocrity. [1] Orwellian calling it "modern" just in the name, as if that…

Lots of Windows devs like having a safer, modern OO ABI instead of a clunky C API stuck in the 90's.

If Microsoft behaved like Apple and Google, people would have no option other than just use it.

After all, in spite of all hate for Windows XP, Vista or 7, there was hardly any year of GNU/Linux desktop.

By the way, the new Office will be store only on Windows 10.

Re: Dvxk: A Vulkan-Based D3D11 Implementation for Linux with Wine

#22
post #21

Earlier quoted context omitted.

> Win32 is going the way of Carbon even if it takes a couple of years more, like it or not. That's the thing, nobody likes it. They've been pushing "modern apps"[1] since 2012 and nobody notable is writing them. As Surface RT showed in the market, when forced to make the choice people will just abandon the product rather than put up with that mediocrity. [1] Orwellian calling it "modern" just in the name, as if that…

Lots of Windows devs like having a safer, modern OO ABI instead of a clunky C API stuck in the 90's. If Microsoft behaved like Apple and Google, people would have no option other than just use it. After all, in spite of all hate for Windows XP, Vista or 7, there was hardly any year of GNU/Linux desktop. By the way, the new Office will be store only on Windows 10.

The new stuff is all COM and you are telling me it's not stuck in the 90s?

Many people prefer software that works. My experience with the newer APIs is that they are on average less reliable, more quirky, less thought through and battle tested. I think the larger problem is that the current staff cannot produce works with the same quality of the Microsoft of 10 or 20 years ago. So of course they cannot compete with their own legacy.

(Disclaimer: I was at MSFT from 2008-2011.)

> By the way, the new Office will be store only on Windows 10.

Good for Office. I'm sure it will work fantastically.

Re: Dvxk: A Vulkan-Based D3D11 Implementation for Linux with Wine

#23
post #12

Earlier quoted context omitted.

Currently the JIT only works for x86-32, not x86-64.

That’s true, but quite a lot of modern desktop software still comes with 32-bit binaries. Even Microsoft’s own software: visual studio and skype are still 32 bit, office has both versions…

There is still a 32bit version of Windows 10:

http://news.softpedia.com/news/Microsoft-Explains-Why-Window...

I wonder why they didn’t push fat binaries like Apple did?

Re: Dvxk: A Vulkan-Based D3D11 Implementation for Linux with Wine

#24
post #14

Earlier quoted context omitted.

Microsoft tried that with Windows RT. It's riskier to that specific Windows edition than to the Win32.

And they're going to keep trying until it finally sticks. It's like Palladium or the Scientology Fair Game policy: just because people don't like it doesn't make it not critical to the organization. They just have to backpedal publicly to re-establish good PR, then sneak it in quietly while people's guard is down.

Microsoft isn't Apple. Their entire business relies on retaining as much backwards compatibility as possible

Every time they make any sort of major, sweeping change. They get raked over coals until they're charred to a god damn crisp

When Windows went from the old DOS-ish 95/98/ME to the much more stable NT based 2000 and XP, lots of things broke.

XP only survived the Microsoft EOL chopping block because of the rise of Netbooks. And even then, companies pay millions to keep that afloat due to how entrenched it is (Something likely to be repeated with Windows 7)

Vista brought a ton of (arguably much needed) changes. But its hardware requirements were pretty high for the time. Along with buggy drivers from Nvidia, that sank the entire operating system. Both in public perception and market share

Windows 7 (on release) was arguably a UI-tweaked Vista. Hardware had caught up by then, and a lot of people agreed that this was the "good" upgrade from XP

Windows 8 came out and tried to shoehorn that whole "Metro" interface and converge everything around it. And it flopped almost as hard as Vista did

Windows 10 Microsoft played a much stronger hand and dragged everyone they could (willing or otherwise, if you believed some accounts) over with a "free" upgrade for most. But it also pruned back Metro pretty hard. Instead trying to chase after the "App Store" model

Re: Dvxk: A Vulkan-Based D3D11 Implementation for Linux with Wine

#25
post #21

Earlier quoted context omitted.

Lots of Windows devs like having a safer, modern OO ABI instead of a clunky C API stuck in the 90's. If Microsoft behaved like Apple and Google, people would have no option other than just use it. After all, in spite of all hate for Windows XP, Vista or 7, there was hardly any year of GNU/Linux desktop. By the way, the new Office will be store only on Windows 10.

The new stuff is all COM and you are telling me it's not stuck in the 90s? Many people prefer software that works. My experience with the newer APIs is that they are on average less reliable, more quirky, less thought through and battle tested. I think the larger problem is that the current staff cannot produce works with the same quality of the Microsoft of 10 or 20 years ago. So of course they cannot compete with t…

> The new stuff is all COM and you are telling me it's not stuck in the 90s?

No, because UWP is .NET done right, what was supposed to be COM Runtime, before Java made them create the CLR instead.

AOT compilation to native code, using a high performance object model with productive programming languages, object oriented, instead of plain old rusty C.

Re: Dvxk: A Vulkan-Based D3D11 Implementation for Linux with Wine

#26
post #5
post #4

Earlier quoted context omitted.

Fortunately, most of us aren't interested in UWP bloat and just want to build good old desktop applications.

Win32 is going the way of Carbon even if it takes a couple of years more, like it or not. Desktop bridge is just a migration tool to migrate Win32 into the store, and help developers slowly migrate parts of the apps into UWP ones. The majority of new APIs are UWP only, with userspace drivers, DirectX 12, ReFS being the notable exceptions. Of course you can always switch to GNU/Linux for Vulkan games.

The question is whether Windows will die sooner than UWP will be fixed to become an acceptable replacement for Win32. The main reason why Windows is still relevant (even despite Microsoft's desperate attempts to kill it) is Steam games and some legacy software that hasn't been ported to Electron yet. Forcing new apps to use UWP in its current broken state can only accelerate the death of desktop Windows.

Re: Dvxk: A Vulkan-Based D3D11 Implementation for Linux with Wine

#27
post #5

Earlier quoted context omitted.

Win32 is going the way of Carbon even if it takes a couple of years more, like it or not. Desktop bridge is just a migration tool to migrate Win32 into the store, and help developers slowly migrate parts of the apps into UWP ones. The majority of new APIs are UWP only, with userspace drivers, DirectX 12, ReFS being the notable exceptions. Of course you can always switch to GNU/Linux for Vulkan games.

The question is whether Windows will die sooner than UWP will be fixed to become an acceptable replacement for Win32. The main reason why Windows is still relevant (even despite Microsoft's desperate attempts to kill it) is Steam games and some legacy software that hasn't been ported to Electron yet. Forcing new apps to use UWP in its current broken state can only accelerate the death of desktop Windows.

> some legacy software that hasn't been ported to Electron yet.

«Let's port Photoshop to electron» not

Re: Dvxk: A Vulkan-Based D3D11 Implementation for Linux with Wine

#28

Earlier quoted context omitted.

The question is whether Windows will die sooner than UWP will be fixed to become an acceptable replacement for Win32. The main reason why Windows is still relevant (even despite Microsoft's desperate attempts to kill it) is Steam games and some legacy software that hasn't been ported to Electron yet. Forcing new apps to use UWP in its current broken state can only accelerate the death of desktop Windows.

> some legacy software that hasn't been ported to Electron yet. «Let's port Photoshop to electron» not

I also doubt that it'll be ported to UWP any time soon.

Re: Dvxk: A Vulkan-Based D3D11 Implementation for Linux with Wine

#29
post #5
post #4

Earlier quoted context omitted.

Fortunately, most of us aren't interested in UWP bloat and just want to build good old desktop applications.

Win32 is going the way of Carbon even if it takes a couple of years more, like it or not. Desktop bridge is just a migration tool to migrate Win32 into the store, and help developers slowly migrate parts of the apps into UWP ones. The majority of new APIs are UWP only, with userspace drivers, DirectX 12, ReFS being the notable exceptions. Of course you can always switch to GNU/Linux for Vulkan games.

Steam doesn't play ball with the Microsoft app-store that UWP insists on.

That's pretty much a game-over for UWP in the gaming world.

Post reply on HN