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.
How would they even know to ask upstream for support, rather than the fork? If you use package bar and have a problem, you would have to do a lot of digging to even find original progject foo and ask them for help (which wouldn't even make sense since it's a separate thing)
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".
Ah I think you might be right with this case where someone will just google that. I am not doing that but prefer to go to the package manager list find there there the project URL.
I was thinking that people will do the same or else how will they know if the github repository returned from search results is truly the one installed?
I am not using NixOS but in general every package manager links to the project homepage let’s say (or name of the project which for example in a GitHub fork is clearly different than the original) which in this case would be the fork.
So for example if this will be the case with a package I use I will report the bug to the fork because the package manager showed me their link.
I will not search for name-like projects or the original one and report there if a fork was distributed to me.
This is why I am confused why a fork is not solving the burden of possible bug reports. Also the fork assumes its own maintenance this is the purpose of the fork.
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.
I’m pretty sure the bigger issue was that it was a very weak simulation, with relatively little interaction. Exploring a simulation/procedural generation is not about getting to view the infinite permutations that randomness gives us — it’s to explore the rules that create the simulation, and then to manipulate those rules.
The reason sim city and dwarf fortress are intersting, and NMS and Spore were not, is because the simulation is sufficiently expanded as to be worth manipulating (while of course not being so expanded to hinder understanding your manipulations; this is the craft); whereas NMS and Spore had very trivial rules: they didn’t really have any. Which is also why when Dwarf Fortress breaks down, its interesting, while in NMS, it’s pathetic.
Note that I’m only referring to NMS on release; though I doubt the simulation has been developed since (I’d bet that the game has since gotten prettier worlds, but not more interesting ones)
Tldr; it was poor simulation/generation game, regardless of whether the current market has ADD
> 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.
