Shared medium will always have congestion. It will never get better. Technology can get faster, but congestion is forever.

This does not surprise me, as the courts are flagrantly biased toward women in these matters. Almost without exception, they come out ahead in every measurable metric.

"as the courts are flagrantly biased toward women in these matters"

As in most matters. There are many studies about lesser sentences for women vs men who commit the same crimes.

This is not always exactly true if you dig into the details - for example, something like 20% of fathers get custody - but it's something like 90% of fathers who try to get custody get some.

How many don't even try though because them assume it is hopeless. Some custody includes things like 1 weekend a month - if that is all you get it wasn't really worth the bother.

“Some”?

Anything less than fifty percent is state sponsored kidnapping.

Because that cost can be less than dealing with upstream.

When I want to contribute to an open source project, I throw together some trivial but useful patches and see how the project responds.

Many projects behave this way, particularly those with corporate overlords. At best, it will take weeks to get a simple patch reviewed. By then, I have moved on, at least with my intention to send anything upstream. I commend the author for giving them a whole year, but I have found that is best a recipe for disappointment.

Maintainers: how you react to patches and PRs significantly influence whether or not you get skilled contributors. When I was maintaining such projects, I always tried to reply within 24 hours to new contributors.

It would be interesting to see how quickly the retention rate drops off as the time to review/accept patches goes up. I imagine it looks like an exponential drop off.

This is probably the best approach.

I submitted a patch to Go once, and never got anything resembling a response. Told me that Go is more or less completely inaccessible; I should treat it as a Google product rather than a FOSS project I can contribute to. The Go standard library documentation bug I submitted a fix to still exists to this day.

This is the way. I disagree with your 24-hour timeline -- give it a week -- but whether and how they respond tells you a lot. Being welcoming to new contributors is crucial for the health of a project.

One time I was interested in contributing to an important part of some project, a part where they were nowhere and in dire need of help. As a first try I submitted a small patch correcting the README's build instructions, which were obviously wrong in one place. I got a lot of attitude and hostility, and they refused to accept the fix. Yeah, bye.

Absolutely. I look at the commit and PR history. Are the maintainers responsive and welcoming?

Have you found this actually works? I wouldn't be surprised if many projects happily accept trivial PRs (because they're easy to deal with) but then ignore or naysay anything more substantial.

The point is only 50% to see if they respond, it's also to start establishing yourself as a known entity to them.

They will ignore a big patch from a rando and obviously process a big patch from themselves.

You can become somehwere in between and no longer be a rando, but have to start from the rando end.

How is that any different than, say, all of human history?

It's not different per se, it's just being made much more difficult i.e. if you had to look for one pearl through a pile of 200 barnacles, how you have to scan through 3000.

At my last job, I found Toradex boards well-supported by Yocto. YMMV

Hm, if I may ask, what were they used for in your last job. To me they seem more entreprise focused than indie focused from a quick glance at their website.

Have you done orienting in the past?

One of the big tricks is to realize that magnetic north (where your compass points) is usually not the same as geographic north (where maps are drawn). The adjustment is local; here, I think magnetic north is 7 degrees off from north.

In the US, the USGS topographic maps contain the required adjustment for the covered area. Not sure about Italy.

I don't think that's it. For me sometimes my phone compass is (roughly) right, but sometimes points in a completely wrong direction, for example 90 degrees off. It calibrates after a while when I start walking but I guess this is what OP had in mind, not a few degree difference.

iPhones can regain the compass fix if you move the phone along a figure eight path while holding it flat and level. Worked pretty well for me in the past.

I'm going to take this as the HN effect, if something isn't doing 500% a year its dead.

Wow. I didn’t know Linux cost that much! /s

Cost isn't only money. In the case of linux it is time to learn to use it (which is a sunk cost on windows: already paid it). Then you need to download and install it - again windows comes by default so a sunk cost.

> In the case of linux it is time to learn to use it

How much time do you need to take to learn "click on the swirly orange thing for Internet"? It looks just the same as it does in every other OS.

> (which is a sunk cost on windows: already paid it)

This is actually something I'm coping with at the moment, because I have to learn how to use Windows and it's the most backwards thing ever to use.

If somebody else admins your system. However if not there is a lot to learn. At least every distribution I've used needs manual updates from time to time. (though admittedly most people would replace the computer before I've seen anything hard happen)

Why would it need someone else to "admin" it?

Who currently "admins" your Windows system?