isilofi

The actual reason in almost all cases: non-techies are clueless about their slow and shitty WIFI. Picking empty or less busy channels, using 5GHz, using gasp cables, all black magic and never done.

Sometimes the upselling actually helps because the better plan comes with a maybe-better AP...

And for doing timing-based interferometry over a distance, the needed timing precision limits your resolution. 1km/c is in the order of 10^-6s (µs), "easy", 1cm/c is in the order of 10^-11s (ps) "possible", 1nm/c is at 10^-18s (as) "quite impossible".

And for the layman, a factor of 10^-6, or 6 orders of magnitude in time are like "a second to two weeks" and "two weeks to far back into the stone age".

The only safe measure is heat-treatment, but that is usually too expensive. In particular, it is more expensive than just using artificial fertilizer.

Price: The hotel website often is no cheaper than booking.com (I guess thanks to very one-sided contracts), and sometimes only gives you a better price if you join a "club" and give them permission to spam you, sell your data, etc.

Payments: booking.com is shady, but less shady and far less broken than a random hotel website where some credit cards might not be working, your CC data turns up in some data dump "found" somewhere, or payment is held by the CC company because you are the first person in months to directly pay to that hotel's website.

Language: booking.com offers an interface and descriptions at least in English. Many hotel websites are only in the local language plus maybe some awkward machine translation that leaves lots of important points to guesswork, especially in the payment flow.

Convenience: booking.com at least offers some kind of searchable database of hotels so I can easily compare them. The hotels themselves make this rather impossible.

I do make a point to try to book via a hotels website after having found it on booking.com. However, in more than half of the cases, for the aforementioned reasons, I end up going through booking.com after all. So while lazy users might be a large part of the reason for the existence of booking middlemen, the hotels do have to bear their fair share of blame here.

Github might be different, but not the rest of the world.

Camouflage is never panacea, but useful camouflage exists, even today. I've (almost) stepped on comrades in an exercise that were hidden well enough to not see them from 3m in broad daylight. But for things to work that well, you need to know what makes humans detect their prey. Movement is a dead giveaway, so as soon as you are running you are toast anyways, and only sheer luck might save you. Form and contour is another problem, something human-shaped and green will stand out, even among other green things. See something rectangular in the forest? Bomb it, rectangular trees are rare. Texture is another giveaway, things looking smooth, regular or out-of-place compared to nearby textures. That's why your camouflaged tank will look like a bush or pile of leaves when properly camouflaged.

All this means that of course you have to go beyond camouflage paint and camouflage clothes. Both are a start, and will help to a point, as a base layer, and for great viewing distances. But even before drones, proper camouflage also involves covering yourself and objects in leaves, branches, nets, parking below trees, etc.

Another interesting point about Ukraine war videos: What you also usually do not see are videos of camouflage being broken by thermal imaging. Both sides have thermal equipment, but I guess are reluctant to point their enemy at how much or how little of it they have, and how vulnerable or not vulnerable the others' camouflage techniques are to it.

Also, smaller drones have a limited reach. To get at the juicy targets (logistics, headquarters) way in the back, you need more expensive and rare long-range drones. So I guess the drone density will sharply drop off beyond the first lines of trenches.

Mobile phone signals can be pinpointed from further away, 10km is easily possible, and the cellular network means that you have a network of antennas in a tighter grid than that. And beyond switching off your phone, there is no camouflaging cell phone signals.

So even if you then employ the drones e.g. to aim and correct the artillery (300m precision from cellphone tower cross location isn't precise enough), cell phones will quickly tell you where to start looking with your drones.

But -Werror for a dev target that e.g. CI uses to compile-test pull requests on known toolchains and distros that you explicitly intend to support is useful. The alternative would be tons of effort to skip -Werror but still have CI flag that pull request that introduces new warnings. Just having the build fail because -Werror is far simpler and less fragile.

However, the xpra client is somewhat strange and inconsistent when it comes to CLI/UI behaviour.

Google will find some more. But I'm not fluent enough in italian to find the respective law.

So management wanted to have their cake and eat it, too. Everyone in an ever smaller, ever more unusable but supposedly cheaper office. Concentrate all the smaller offices in the suburbs into one huge big-city campus, making the commute a nightmare. But people have to be at their desks, or else. Remote was officially rolled back.

Unofficially, even middle management wised up and just ignored the back-to-office mandate, because they wouldn't know anyways who was in and who wasn't.

I'm coordinating with developers in Europe, South America and East Asia. The customers are all over, but mainly North American. I'm in Europe. I've seen some of the customers once or twice in person, I see many of my European colleagues at the yearly get-together. But all the contact and all the work is over email, phone and video conferences and the usual mix of other remote collaboration tools, ticket system, git, stuff like that. When I enter our local office, only one of the 50 people working there has anything to do with that I do. My manager is 800km away. Well, there's payroll over here, but the only time I'll need to "visit" them in person is when a paycheck is late ;).

Even before COVID, the world shifted towards remote, even when you HAD to come to the local office because of reasons. COVID just showed everyone what a charade it already has been for the last decade to force people into an office just to get on phone/email/git and work remotely from the office. COVID cut out the stupid useless "going to the office" step.

In the 2000s, it wasn't like that, teams were concentrated at some offices, offshoring wasn't that much of a thing yet. And for lots of things, travelling e.g. to meet a customer was accepted and normal, far more often than it is now. A new contract was a 2-week stay at the customers'. Back then, remote work actually was a privilege. But the world had changed long before COVID, slowly, then very quickly.

Otherwise, good luck getting Google to move in maybe a few years or so...

One could even imagine scenarios like an originally MIT-licensed software splitting into a commercial company offering commercial paid licenses, plus a community (or even the company itself) offering a GPL-licensed fork. Of course one could then still maintain an additional MIT-licensed fork, but if the rest of the community is happy with GPL and all the development just happens there, your MIT fork will "starve"...

Yes, but there are two sides to "resonableness": The "what" side and the "who" side. "What" is the thing that should be resonable. But the overall resonableness just as much depends on the question: "for whom is this reasonable?". While a consumer cannot possibly be expected to really read all the ToS everywhere, a business maybe can be expected to do so. Especially for things that are very critical and integral to the business, like the license of that one framework you are building all your software upon. So I do think requiring a business to read and understand the Unity ToS is totally resonable.