It depends on the situation. I had all of mine out this past weekend (in the US) and, because they were fully grown in, all they had to do was some local anaesthetic (about 8 shots around various parts of the mouth), wait 15 minutes, and loosen/pull them all. Total procedure was less than 30 minute and no painkillers prescribed after the fact.
I guess that depends on how users go about finding projects on github to file issues. If, for example, the user has an issue with this NixOS package (or debian package/any other repackaged example), and they start by just searching "python ambee github" or "Home Assistant ambee github" (seems like a reasonable first attempt to me) they will likely find the upstream near the top of the results.
Now, some users will perform due diligence and maybe find the NixOS issue referenced in OP and look elsewhere, but many will find the project and immediately file an issue there in the upstream, leading to the author's main concern of "I don't have time to support NixOS issues".
I read an opinion piece[0] recently that suggested one of the (many) reasons that No Man's Sky was so poorly received at launch was due to the fact games have commonly been boiled down to constant action and "gotta beat the game" mentality, and that players don't know how to just explore and enjoy games as an open-ended single player experience.
As someone who plays almost exclusively single player games across a vast numbers of genres, I enjoyed No Man's Sky's "exploring and discovering the unknown" game play at launch and have ever since, as they add more and more content.
> They will start looking for a new gig immediately
The response to this should be: "Good for them! They should look for somewhere that will pay them what they think they are worth."
I believe that is the whole point behind sharing salaries, to help level the playing field and help people who got low-balled on their offer to realize this.
The way the greater Flint area's zip codes and address system works out had some other interesting impacts, as well, from a business perspective. After the crisis became more public, we started seeing businesses who were in Flint (greater Flint area, Flint mailing address), but not the City of Flint (the affected area), putting up signs and trying to make very obvious that they didn't have Flint water.
The City of Flint's water system is isolated from the rest of the county, which falls under the Genesee County Drain Commission's jurisdiction and is connected to the Detroit water system. It is still difficult to get some people to understand that they are different things (have had to explain to family many times that while we live in "Flint", we are not on Flint water). It would be interesting to see a study done on the effect this had on businesses both within the city and in the greater Flint area.
> However, I'm not a software developer, so rhat could also have something to do with it
Definitely has something to do with it. I'm a software engineer in the Detroit area and the last time I switched jobs (4ish years ago), it took less than 2 weeks from the time I updated and posted my resume to signing an offer letter. With the number of calls and emails I get daily for different positions in the area, I have a feeling it would go just as quickly the next time I decide to make a move.
Windows Containers only went GA fairly recently with Windows Server 2016, so it is unlikely that many are using them yet. I have yet to see any CI services that mention any plans to support windows containers or acknowledge their existence.
Docker for Windows, linked above, and Windows Container Service[0] are two separate things. Docker for Windows runs a linux VM in Hyper-V and allows you to run linux based docker containers. Windows Container Service allows you to run windows based container images (using Hyper-V as a backend) and can use either Docker or Powershell Container Commandlets as a frontend for interacting with those containers.
So, yes Microsoft did implement containers in the Windows kernel, but that isn't what OP is about.
Docker images still aren't generally available, but you can now run Windows Container Images based on the NanoServer docker image (and WindowsServerCore image if you replace nanoserver with windowsservercore in their image URL in the docs below) on Windows 10 (insiders build)[0].