Quoting: DuncAs with others here, it's going to take a lot more than friendly words for me to trust Microsoft.

Quoting: JanneBut they are clearly a different company than they were 15-20 years ago. Companies consist of people, and as people change, so can companies.

I'm not sure they change all that much. Despite numerous changes in personnel, and even a short (second) period as a successful PC manufacturer, I don't think IBM ever reconciled itself to the fact that it wasn't going to own the PC market in the way it had with previous generations.

I see Microsoft in the same light. It's a company that was founded on the productization of software, playing its cards close to its chest, jealously guarding its source. It's trying to adapt to open source because it sees the way the wind's blowing. But corporate cultures run deep, and it's always going to be an uncomfortable fit. As others have said, I'll begin to believe it when major Microsoft projects - Office, DirectX, even Windows - go open source. I'm not holding my breath.

Well, I'm pretty certain that these older code bases will never go open source. Actually I don't know of any code base of that scale that is still being maintained to ever being open sourced. Waiting for this to happen is just waiting for your own prophecies to come true, thus to only confirm your own believe that Microsoft is the company from the 1980's.
I think that Mircosoft, like all major players, is a pretty big company with a lot of different departments that have now much more independent control than in the early days. Some of these departments (or better the people working and directing there) understood the value of Open Source and made it part of their "department culture", e.g the VS Code team or the .Net Core team. Other departments, Windows and Office, are still more traditional departments and due to history likely not even in a position to change that rapidly (or don't want to change).

To be honest, what would Microsoft (or e.g. NVidia) gain by just dumping these code bases on github? I guess nothing except bad press due to being an old code bases (even the best code tends to rot over time) and may be issues with embedded third party IP. If these companies do go open source, they usually do it with greenfield projects and of course it has to benefit them (which is fine if it's a win-win in the end ).

View this comment - View article - View full comments

Oh this one looks nice, wishlisted.

View this comment - View article - View full comments

Quoting: Comandante ÑoñardoI wonder when We gonna see this on Proton.

I guess it's wise to wait with a Proton rebase until e.g. support for Media Foundation is completed. There's currently a lot of work going on for this topic afaik.

View this comment - View article - View full comments

Quoting: scaineEasier just to ignore it and move on to something that interests you. Define yourself by things you love, not the things you hate.

Thanks, the world would indeed be a much nicer place when people would more act like this.

View this comment - View article - View full comments

oh this is really cool, thanks a lot dreamer_ and colleagues!
Out of curiosity, is it known why the original project somehow got "stuck" in time?

View this comment - View article - View full comments

Quoting: Guest

Quoting: jensThanks a lot for the great explanation. So in my own words that extension is mostly for defining (make sure it is fast and looks everywhere the same) sort-of currently undefined behavior?

To be more precise, adding different possible defined behaviour. Vulkan is much more tight on definitions, so what to do always had to be defined, this just gives more options of what to do. In a fast and looks everywhere the same manner.

Got it, thanks again!

View this comment - View article - View full comments

Quoting: Guest

Quoting: jensMay I ask what border-color actually is/means in 3D world?
The term sounds rather simple for my naive mind, but I guess there is a whole lot of magic considering it needs a separate extension...

When mapping from a texture (let's presume 2D texture) to a triangle (2D or 3D, but let's presume in 3D co-ordinate space), what happens when you go beyond the bounds of the texture? This can happen easily enough, and indeed can be used to great effect. It can also affect texture filtering (if you average over 4 texels, or points of the texture, then what happens on the edges and corners needs defining).

Often it's defined as treating the texture data beyond the limits of the texture as black, or white, or just repeat what's on the border of the texture. This extension allows that border colour to be defined to something else.

That's the hand-wavy simplified version of the what, but why the dedicated extension? Not all hardware supports it for a start. Some may be hard coded to black or white. Some may need it specified in a different manner - hardware, or extras tacked onto shaders. And then there's consideration of different colour spaces (CMYK vs RGBA). Vulkan doesn't just cover desktop hardware for gaming after all.

Thanks a lot for the great explanation. So in my own words that extension is mostly for defining (make sure it is fast and looks everywhere the same) sort-of currently undefined behavior?

View this comment - View article - View full comments

May I ask what border-color actually is/means in 3D world?
The term sounds rather simple for my naive mind, but I guess there is a whole lot of magic considering it needs a separate extension...

View this comment - View article - View full comments

Just updated two machines. The update went pretty smooth, that said I always switch to nouveau before doing the actual update to prevent any weird driver/kernel mismatches.

Really cool to have an updated system! The updated Gnome Desktop feels again a bit faster.

View this comment - View article - View full comments

.Net Core and GTK, updating Fedora for two machines is also on my list ;)
When time permits, once in a while a few laps in ACC.

View this comment - View article - View full comments