Note how they don’t contribute anything to X/Wayland, they only _extend_ it so that DX12 and other proprietary, Windows-only systems can interact with Linux. These are anti-features. Like they could also just use Vulkan and be done with, but they don’t; EEE is in full swing.
Could someone use this to improve the DirectX on Wine compatibility? I know that the DXVK reached a state where most of things work but some games will need special patches. a fix for one game will break other game.
Thats not entirely true. They have been contributing to the Clover OpenCL implementation in Mesa, and added RDP shell to the Weston wayland compositor for example.
That being said, just using the established standards instead of jumping through hoops to support their own standards on the linux platform would be nicer.
Also, why should "just use Vulkan and be done with"? Vulkan is just another standard, being open doesn't mean it's better, or more suited to their needs (they have a platform to consider, they're not about cross-platformness).
Yeah, if "embrace, extend, extinguish" has been going for the past 22 years and they're still busy embracing and occasionally extending and haven't figured out how to extinguish, I see no reason to discourage them :)
You forget they set the web browser market back a decade, and in doing so held back Linux desktop adoption.
It was not that long ago that some important websites, such as bank or government, required IE.
Microsoft embraced the browser market, extended it (activex along with some genuine innovatives such as ajax) and then extinguished it by letting IE languish.
The technological progress recovered thanks to efforts by Mozilla, KDE, Google and Apple, but who knows how our world might have looked like if Microsoft had not been successful in EEE'ing the web.
That a company wants its own API to move freely and faster is often described as evil when it is merely sensible for them. It used to cause lock-in, but nowadays there are enough tech stack that isolate you from the underlying API to make it irrelevant.
Do note that until, oh let's arbitrarily say 10 years ago, DirectX was ahead feature-wise to OpenGL and OpenGL was moving at turtle pace.
>They can do whatever they want, of course. But don't kid yourself about the reasons.
Isn't the people kidding themselves that ones that consider it a "strange" or "troubling" reason that a company has a product and wants to sell that product?
A platform has APIs. Who said an OS should use "open" graphics APIs?
The whole point of having an OS is that it's different than another OS. If all OSes just used the same APIs (filesystems, graphics, sound, etc) we'd just have one OS.
That's something shared by unices and Linux follows course, but it's not the idea behind (or the ideal of) other OSes.
And I don't want a world where there's a single set of APIs for all OSes, and all OSes give the same core functionality in the same implementation (e.g. Vulcan + OpenAL + POSIX + ...).
Having all OSes be that (e.g. all use Vulcan), would be the same situation as everybody using DirectX (innovation wise), the only exception being that Vulcan is free/open.
But I don't want openess about all, I also want variety and different innovations, and platforms offering unique stuff...
It is in your users interest to have access to APIs that are as useful as possible.
The moat APIs created by OS vendors are mostly in their interest. Does anyone but Apple want an API like Metal? Developers don't. User see no benefit. Only Apple benefits.
I'm not saying there should be only one globally used API for every task, but praising APIs that exist only to be moats to increase corporate profits is another.
About innovation, everyone can join Khronos (for free) and contribute to their API of choice. You can add whichever extension you want to these APIs, and if they are found useful they are included in the main standard.
Which is why Khronos APIs are a clusterf..... of extensions, only those that never actually wrote portable OpenXX code across multiple platforms, graphics cards and had to deal with driver bugs on top praise their portability.
Taking a guess, this seems mostly like a plan to get machine learning developers back onto Windows as main development boxes. If so, the first iteration of WSL itself was about web development. The integration of cross compilation and remote debugging for Linux into Visual Studio points into a similar direction.
MS seems to accept Linux on servers, but allowing Linux on desktop machines might actually end up eating a significant chunk of the Windows market share.
I think Microsoft's strategy (I work there, but I don't have any special knowledge of this) is to be the best possible platform for development in general, not just machine learning. That's why they bought GitHub, and it's also why they have WSL, remote debugging on Linux, etc. I expect they will go wherever they think developers want to be to achieve that goal.
I can see this hurting traditional Linux graphics systems and development tooling, but I think the main dynamic driving this is not proprietary-vs-open, it's Microsoft's ability to coordinate large numbers of developers, because they have a massively more united org than random hobbyists.
If you combined all of the efforts of all of the people working on Linux tools for the past 20 years and got them working on the same thing, it would probably be an amazing stack, and Microsoft would probably just support it. Instead, the open source efforts have been scattered among a lot of different ideas, which means there hasn't been a single windowing toolkit, IDE, or whatever for people to rally around and all contribute to. And as a result, Microsoft can show up, get a few hundred people pulling in the same direction, and have the market-leading product not through any dirty tricks, but just by putting in more coordinated effort than anyone else.
> the main dynamic driving this is not proprietary-vs-open,
Some would say that's the whole point. Not which company wins, not even which standard wins, but that openness wins.
Of course the fragmentation strategy can be successful against such a push. It's bascially the oldest trick in the book. That doesn't mean it will win in the long run.
>I can see this hurting traditional Linux graphics systems and development tooling, but I think the main dynamic driving this is not proprietary-vs-open, it's Microsoft's ability to coordinate large numbers of developers, because they have a massively more united org than random hobbyists.
As one of the people using this wonderful free technology, I would like to actively state that I will fight MS and any other Tech provider remotely involved in destroying my most productive way of working, and trying to supplant me back into a machine that sells only advertising.
I didn't pay for a machine to sell me advertising.
"Oh you can disable ads".
Why should I need to?
On that note:
>"If you combined all of the efforts of all of the people working on Linux tools for the past 20 years and got them working on the same thing,"
Why don't all car manufacturers focus on the same thing?
Why is there more than one company for anything then?
Shouldn't the government just run everything then?
Who needs competition and a free market?
But, really, the reason we all know deep down inside is:
Because if we did that we would end up with Microsoft, a company that builds AI to find novel ways of forcing you to interact with advertising, somewhat akin to a Black Mirror episode.
Agreed - I will note however how badly Microsoft has bungled this same story on Windows itself. They went from a very high productive and unified development story in mfc/winforms to a super fragmented space.
I am getting going with WPF. (But that was then followed by maybe Silverlight? Then HTML with bindings?). Now we have been told that UWP is the big future (basically Windows Phone framework?). Gah! XAML? I mean, we went from a drag and drop unified and simple and extendable dev experience that was actually fast to develop into this GUI nightmare - all produced by ONE company with total command and control over their developers.
It tells you something that google web browser is almost a more stable and targetable platform than the native Windows platform (chromium / electron). I mean, that is desparation right there. At least someone was smart enough at microsoft to just give up on IE even on their own platform!
If QT had a bit of a simpler onboarding flow or linux was more unified I think there actually is an opportunity to actually be a good standard for line of business apps that want snappy responsiveness etc. But I just can't believe how badly Microsoft has screwed up their GUI story for the developers they claim to care so much about.
My thoughts exactly on QT! A good bridge to C# and a good "get a button on a page that triggers "onClick" quickstart workflow" and they'd be in a great position.
There is a lot of confusion on their site between QT creator, Design Studio, bindings, etc etc - so simplifying all that would be great.
They could target C# and (maybe) python (since it already is developed) for the windows story.
Add C++/WinRT to the mix, which dropped the productivity features of C++/CX, with the team that managed to kill it telling us to just wait for ISO C++ to catch up, while dealing with IDL files pre-.NET style.
Naturally the reception has been less than stellar and they are finally acknowledging that waiting isn't not an option and something is being discussed, however don't expect any improvements in 2020.
This puzzles me as well. Win32 is fine. If you download Dolphin Smalltalk or Corman Lisp or Free Pascal/Lazarus, they're still targeting Win32 for GUIs. Especially since, with Wine, Win32 GUIs are effectively cross platform.
What boggles the mind is the insane peoplepower they have poured into the redo redo redo here. They spin up huge documents on MSDN, platform toolkits etc.
Instead of trying to chase every random idea out there if they'd just gone deep on Win32 (now effectively x-platform) I think they could have gone a LOT further / faster. The new setups are also super complex and feel a lot more brittle by the time you build out all the toolchain.
Maybe my memory is going, but powering up VS and doing stuff was quick on windows in the past, now it's GB's of junk to just say hello world.
That beat Microsoft dead in the server market. In academic and scientific computing. How about the embedded market?
From my perspective the random hobbyists have Microsoft backed into a corner, with only their hold on a narrowing desktop market share remaining.
How many 0-days has Microsoft left hanging open for the better part of a decade while trying to figure out how to defeat open source software?
I think that if Microsoft focused on being the best of something they'd not have a problem right now. I think they focused on being the only of something, trying to make sure no one else could enter the market. I think now they're trying to use money to make themselves an asset in that market.
Those hobbyists know how to build tools they want; that translates well into server related stuff.
Microsoft knows how to build tools that untechnical people can use. They are the best at this; that's why they have the desktop market. If Microsoft can make user centric tools that have at their backend Linux tech, then they will have the best of both worlds.
Any idiot can click around Excel or Active Directory and get something good enough. That's what Microsoft is good at facilitating. If Microsoft can make the rest of the Linux stack as easy to use as visual studio code, then why should a random busy sysadmin or webdev bother with buggy Ubuntu? Windows 10 will have everything they need, with more convenience.
Microsoft isn't backed into a corner: you're resting on your laurels. They're about to Embrace everything about Linux that's awesome. Get ready for what comes after.
let's consider PowerShell for a moment. when it came out the bulk of windows admins noted as much as the command prompt changing its Color, and the bulk of Unix admins did not even pay a cent, cause they are so happy with existing Unix tools.
no one noted that PS is literally taking 'the best of Unix shells and then some', putting this on steroids which vastly simplifies all DevOPs and does so in a fairly structured-OO-fancy. Even even the worst PS1 program is practically more comprehensible than arbitrary /etc/init.d script. And it pumps objects, not streams that you need to through Regexes against to parse.
It's been very clear that MS is very well into the idea of embrace opensource, because there is value to it, which even blind opensource advocates can not properly evaluate and then put to work.
The non-developer crowd blindly believes that open source is about free software and daring David-vs-Goliath, but open software actually has cost, and this cost can be quite high. at the end - someone pays the bill.
For example - number of big organizations put money into Postgre and it's why it's still there. Put money in RedHat, do put money and effort for linux kernel, and I really hope Mozilla will transform soon to actually be able to sell some stuff. Opensource is key asset in this case but likely valued are the communities around it.
By no means is open software built by enthusiasts, the most fundamental parts opensource software are built by top-notch hard-core developers unmatched in their coding skills.
Putting the whole .net library as available to use as well as any CLI tool is very interesting. The syntax is a slightly on the quirk side. But not terrible and it is consistent in its own logic.
To put it to someone who has not used PS it is like taking the entirety of the C/C++ runtime and whatever lib is in your libs folder available to use without writing a bunch of wrapper bits of code to use it. Then still being able to use the existing set of wrapper bits.
MS has lost the server space, and a good chunk of the developer space on desktop to opensource and macos. To expect them to sit back and not do something would be astonishing. Of course they are going to make software for those platforms. They make software even if they do not own the platform it runs on. MS sees software as a way to get things done. Sometimes in the opensource world people see it as a lifestyle decision. Those can coexist, because they are not against each other. They can complement each other.
It brings the Xerox PARC and ETHZ workstations REPLs into Windows.
Basically everything in the OS is available for scripting, regardless if it is a DLL, COM, .NET library.
And the shell is a proper programming language with modules support and uses structure data as default.
This means you can easily make use of any OS feature or even automate existing GUI applications via COM/OLE, or their own libraries.
And there is an OS provided IDE as well, with integrated debugger.
So overall one gets a little closer to what the Lisp Machines used to be, just with a mix of .NET and native libraries.
Yes this would be possible in UNIX, but given the fragmentation and POSIX culture, it will never be adopted at scale for it to work the same way as Powershell does on Windows.
> no one noted that PS is literally taking 'the best of Unix shells and then some', putting this on steroids which vastly simplifies all DevOPs and does so in a fairly structured-OO-fancy.
This is a big thing on Windows, but not so much on Linux, where you have a number of languages available - you don't need to write all your scripts in Bash - a lot of my company's automation is written in Python, which is vastly superior as a programming language - and you don't need to limit yourself to what's built into the shell - there are dozens of small utilities that operate on streams that make your life easier. The self-contained approach of a shell-to-end-all-shells makes sense in the Windows environment (where "curl" is not an executable) and absolutely doesn't anywhere else.
> Microsoft knows how to build tools that untechnical people can use
They have a pretty hit and miss history there. They got a few things (mostly) right and leveraged them from there. Every attempt they made to replace the hierarchical file system as a way to store files on your computer failed comically, almost as comically as Microsoft Bob or Microsoft Network.
> They are the best at this; that's why they have the desktop market.
One could say they did that by suffocating the competition with legally dubious tactics until they effectively had a monopoly on corporate desktops, which gave them the push they needed to leverage it into a de-facto monopoly on all things x86. Note that for anything that's not an x86 box they have approximately zero market share.
> Microsoft isn't backed into a corner: you're resting on your laurels. They're about to Embrace everything about Linux that's awesome.
I agree with you on that - they aren't going the way of the dinosaur quietly. They'll do whatever they can to gain relevance and force other players out of the market so they can enjoy a de-facto monopoly like they did before.
Just to throw my 2 cents in I appreciate having the choice between 10 mediocre programs (3 of which are actually quite passable!) vs. being tied into the one all-inclusive solution with maybe a few knobs to twist and that's it. That's what drove me away from Windows.
I guess it depends on what you're looking for but I'm happy with what I've got. But I meant more basic things like window managers and desktop environments. Systems like Debian just allow you to build things the way you want using the components you want.
These may be anti-features, but it is good in a couple of respects. One is the acknowledgement by Microsoft of the role of open source software in the industry, and the other is to facilitate the development of software in mixed environments.
I seriously doubt this poses a serious risk to open source software. Open source developers are not going to be any more likely to adopt closed components, particularly from a company that has bred animosity towards open source in the past.
They are building an OpenGL-to-DX12 stack using mesa, the open source OpenGL implementation. As Microsoft finds bugs or compatibility issues with GL apps (since many rely on behavior specific to the Nvidia driver), I'm sure they'll contribute fixes to upstream mesa.
That is not true. They've been working on a new OpenCL compiler. You can see commits from Jesse Natalie in here, they're one of the D3D12 engineers at MS working on mesa and contributing code. This is fully free-standing and is not related to hypervisor support at all.
56 comments
[ 2.8 ms ] story [ 149 ms ] threadThat being said, just using the established standards instead of jumping through hoops to support their own standards on the linux platform would be nicer.
Also, why should "just use Vulkan and be done with"? Vulkan is just another standard, being open doesn't mean it's better, or more suited to their needs (they have a platform to consider, they're not about cross-platformness).
It was not that long ago that some important websites, such as bank or government, required IE.
Microsoft embraced the browser market, extended it (activex along with some genuine innovatives such as ajax) and then extinguished it by letting IE languish.
The technological progress recovered thanks to efforts by Mozilla, KDE, Google and Apple, but who knows how our world might have looked like if Microsoft had not been successful in EEE'ing the web.
Agreed.
> KDE.
Agreed.
> Google and Apple.
Out of the frying pan and into the fire :-)
That a company wants its own API to move freely and faster is often described as evil when it is merely sensible for them. It used to cause lock-in, but nowadays there are enough tech stack that isolate you from the underlying API to make it irrelevant.
Do note that until, oh let's arbitrarily say 10 years ago, DirectX was ahead feature-wise to OpenGL and OpenGL was moving at turtle pace.
If features are what they need, Khronos accepts any company as a member.
Isn't the people kidding themselves that ones that consider it a "strange" or "troubling" reason that a company has a product and wants to sell that product?
The whole point of having an OS is that it's different than another OS. If all OSes just used the same APIs (filesystems, graphics, sound, etc) we'd just have one OS.
That's something shared by unices and Linux follows course, but it's not the idea behind (or the ideal of) other OSes.
And I don't want a world where there's a single set of APIs for all OSes, and all OSes give the same core functionality in the same implementation (e.g. Vulcan + OpenAL + POSIX + ...).
Having all OSes be that (e.g. all use Vulcan), would be the same situation as everybody using DirectX (innovation wise), the only exception being that Vulcan is free/open.
But I don't want openess about all, I also want variety and different innovations, and platforms offering unique stuff...
The moat APIs created by OS vendors are mostly in their interest. Does anyone but Apple want an API like Metal? Developers don't. User see no benefit. Only Apple benefits.
I'm not saying there should be only one globally used API for every task, but praising APIs that exist only to be moats to increase corporate profits is another.
About innovation, everyone can join Khronos (for free) and contribute to their API of choice. You can add whichever extension you want to these APIs, and if they are found useful they are included in the main standard.
Write once, add code paths and debug everywhere.
MS seems to accept Linux on servers, but allowing Linux on desktop machines might actually end up eating a significant chunk of the Windows market share.
I can see this hurting traditional Linux graphics systems and development tooling, but I think the main dynamic driving this is not proprietary-vs-open, it's Microsoft's ability to coordinate large numbers of developers, because they have a massively more united org than random hobbyists.
If you combined all of the efforts of all of the people working on Linux tools for the past 20 years and got them working on the same thing, it would probably be an amazing stack, and Microsoft would probably just support it. Instead, the open source efforts have been scattered among a lot of different ideas, which means there hasn't been a single windowing toolkit, IDE, or whatever for people to rally around and all contribute to. And as a result, Microsoft can show up, get a few hundred people pulling in the same direction, and have the market-leading product not through any dirty tricks, but just by putting in more coordinated effort than anyone else.
Some would say that's the whole point. Not which company wins, not even which standard wins, but that openness wins.
Of course the fragmentation strategy can be successful against such a push. It's bascially the oldest trick in the book. That doesn't mean it will win in the long run.
As one of the people using this wonderful free technology, I would like to actively state that I will fight MS and any other Tech provider remotely involved in destroying my most productive way of working, and trying to supplant me back into a machine that sells only advertising. I didn't pay for a machine to sell me advertising.
"Oh you can disable ads". Why should I need to?
On that note: >"If you combined all of the efforts of all of the people working on Linux tools for the past 20 years and got them working on the same thing,"
Why don't all car manufacturers focus on the same thing?
Why is there more than one company for anything then?
Shouldn't the government just run everything then?
Who needs competition and a free market?
But, really, the reason we all know deep down inside is:
Because if we did that we would end up with Microsoft, a company that builds AI to find novel ways of forcing you to interact with advertising, somewhat akin to a Black Mirror episode.
I am getting going with WPF. (But that was then followed by maybe Silverlight? Then HTML with bindings?). Now we have been told that UWP is the big future (basically Windows Phone framework?). Gah! XAML? I mean, we went from a drag and drop unified and simple and extendable dev experience that was actually fast to develop into this GUI nightmare - all produced by ONE company with total command and control over their developers.
It tells you something that google web browser is almost a more stable and targetable platform than the native Windows platform (chromium / electron). I mean, that is desparation right there. At least someone was smart enough at microsoft to just give up on IE even on their own platform!
If QT had a bit of a simpler onboarding flow or linux was more unified I think there actually is an opportunity to actually be a good standard for line of business apps that want snappy responsiveness etc. But I just can't believe how badly Microsoft has screwed up their GUI story for the developers they claim to care so much about.
If Qt had a good bridge to C#, they could probably get a lot of marketshare on .NET while this confusion lasts.
My thoughts exactly on QT! A good bridge to C# and a good "get a button on a page that triggers "onClick" quickstart workflow" and they'd be in a great position.
There is a lot of confusion on their site between QT creator, Design Studio, bindings, etc etc - so simplifying all that would be great.
They could target C# and (maybe) python (since it already is developed) for the windows story.
Naturally the reception has been less than stellar and they are finally acknowledging that waiting isn't not an option and something is being discussed, however don't expect any improvements in 2020.
Instead of trying to chase every random idea out there if they'd just gone deep on Win32 (now effectively x-platform) I think they could have gone a LOT further / faster. The new setups are also super complex and feel a lot more brittle by the time you build out all the toolchain.
Maybe my memory is going, but powering up VS and doing stuff was quick on windows in the past, now it's GB's of junk to just say hello world.
That beat Microsoft dead in the server market. In academic and scientific computing. How about the embedded market?
From my perspective the random hobbyists have Microsoft backed into a corner, with only their hold on a narrowing desktop market share remaining.
How many 0-days has Microsoft left hanging open for the better part of a decade while trying to figure out how to defeat open source software?
I think that if Microsoft focused on being the best of something they'd not have a problem right now. I think they focused on being the only of something, trying to make sure no one else could enter the market. I think now they're trying to use money to make themselves an asset in that market.
Microsoft knows how to build tools that untechnical people can use. They are the best at this; that's why they have the desktop market. If Microsoft can make user centric tools that have at their backend Linux tech, then they will have the best of both worlds.
Any idiot can click around Excel or Active Directory and get something good enough. That's what Microsoft is good at facilitating. If Microsoft can make the rest of the Linux stack as easy to use as visual studio code, then why should a random busy sysadmin or webdev bother with buggy Ubuntu? Windows 10 will have everything they need, with more convenience.
Microsoft isn't backed into a corner: you're resting on your laurels. They're about to Embrace everything about Linux that's awesome. Get ready for what comes after.
no one noted that PS is literally taking 'the best of Unix shells and then some', putting this on steroids which vastly simplifies all DevOPs and does so in a fairly structured-OO-fancy. Even even the worst PS1 program is practically more comprehensible than arbitrary /etc/init.d script. And it pumps objects, not streams that you need to through Regexes against to parse.
It's been very clear that MS is very well into the idea of embrace opensource, because there is value to it, which even blind opensource advocates can not properly evaluate and then put to work.
The non-developer crowd blindly believes that open source is about free software and daring David-vs-Goliath, but open software actually has cost, and this cost can be quite high. at the end - someone pays the bill.
For example - number of big organizations put money into Postgre and it's why it's still there. Put money in RedHat, do put money and effort for linux kernel, and I really hope Mozilla will transform soon to actually be able to sell some stuff. Opensource is key asset in this case but likely valued are the communities around it.
By no means is open software built by enthusiasts, the most fundamental parts opensource software are built by top-notch hard-core developers unmatched in their coding skills.
To put it to someone who has not used PS it is like taking the entirety of the C/C++ runtime and whatever lib is in your libs folder available to use without writing a bunch of wrapper bits of code to use it. Then still being able to use the existing set of wrapper bits.
MS has lost the server space, and a good chunk of the developer space on desktop to opensource and macos. To expect them to sit back and not do something would be astonishing. Of course they are going to make software for those platforms. They make software even if they do not own the platform it runs on. MS sees software as a way to get things done. Sometimes in the opensource world people see it as a lifestyle decision. Those can coexist, because they are not against each other. They can complement each other.
Windows users seem to be fond of its syntax, which is understandable considering how starved of languages they'd been for the past 40 years.
Besides, everything that can be used with bash can be used with PowerShell. Opposite is not true.
Better. Much much better.
Basically everything in the OS is available for scripting, regardless if it is a DLL, COM, .NET library.
And the shell is a proper programming language with modules support and uses structure data as default.
This means you can easily make use of any OS feature or even automate existing GUI applications via COM/OLE, or their own libraries.
And there is an OS provided IDE as well, with integrated debugger.
So overall one gets a little closer to what the Lisp Machines used to be, just with a mix of .NET and native libraries.
Yes this would be possible in UNIX, but given the fragmentation and POSIX culture, it will never be adopted at scale for it to work the same way as Powershell does on Windows.
This is a big thing on Windows, but not so much on Linux, where you have a number of languages available - you don't need to write all your scripts in Bash - a lot of my company's automation is written in Python, which is vastly superior as a programming language - and you don't need to limit yourself to what's built into the shell - there are dozens of small utilities that operate on streams that make your life easier. The self-contained approach of a shell-to-end-all-shells makes sense in the Windows environment (where "curl" is not an executable) and absolutely doesn't anywhere else.
They have a pretty hit and miss history there. They got a few things (mostly) right and leveraged them from there. Every attempt they made to replace the hierarchical file system as a way to store files on your computer failed comically, almost as comically as Microsoft Bob or Microsoft Network.
> They are the best at this; that's why they have the desktop market.
One could say they did that by suffocating the competition with legally dubious tactics until they effectively had a monopoly on corporate desktops, which gave them the push they needed to leverage it into a de-facto monopoly on all things x86. Note that for anything that's not an x86 box they have approximately zero market share.
> Microsoft isn't backed into a corner: you're resting on your laurels. They're about to Embrace everything about Linux that's awesome.
I agree with you on that - they aren't going the way of the dinosaur quietly. They'll do whatever they can to gain relevance and force other players out of the market so they can enjoy a de-facto monopoly like they did before.
I seriously doubt this poses a serious risk to open source software. Open source developers are not going to be any more likely to adopt closed components, particularly from a company that has bred animosity towards open source in the past.
https://gitlab.freedesktop.org/kusma/mesa/-/commits/msclc-d3...
Good for organizers. Dev conferences in Poland are not exactly a gold mine.