Same concept, I guess. I'm a platform engineer / SRE, and blue/green is a more common way of describing that way of deploying applications so I didn't even consider it could have a different name on the OS layer.
As a trackpoint user, I am glad it's off by default.
Because of scrolling on Thinkpad keyboards (using the middle click), I had to turn that feature of every time, especially while working on longer documents I would otherwise accidentally paste stuff at random places.
From where I sit I have 5 Thinkpads set up within reach, and I have a few more in other rooms. They are by far my preferred laptop.
Most run Ubuntu as their default OS, most have the trackpad disabled because I usually use the trackpoint for everything, and on all of them I use middle-click to paste extensively.
I'm guessing you have touchpad corners enabled. Usually by default lower-right is 2nd mouse button and upper-right is 3rd mouse button (middle click).
I only use the touchpad, but knowing where it is I can avoid it and almost never trigger it accidentally. It can also be disabled without affecting two-finger and three-finger tap, which I do use.
To you it is, plenty of people -including myself- don’t find it so. And considering the ratio of MacOS+Windows desktop users to those of ‘nix (an increasing number of which are new converts), middle clickers are a minority here.
But hey! At least they are only flipping defaults, not removing the feature outright, like they did type-ahead search. [Insert angry rant here]
That is gnome's standard play: move a feature to a preference (“you can just turn it back on”), remove the preference from the control panel (“you can still turn it back on using ‹whatever conf backend they're using this year›”), and then finally remove the feature (“you could only turn it on by using an unsupported mechanism, and ‹conf backend they used last year› is deprecated anyway”).
I agree with the point about this being configurable.
About your first point, however, keep in mind that "middle click insert" has been the default behavior in X since the 1980s, long before Windows or current generation MacOS's were around. To me, this is such a basic functionality, I would compare it something as fundamental as CTRL-X/C/V for cut/copy/paste on Windows.
I was never a fan of it. I always turned it off. And now it also freed up middle click for auto scrolling which is actually great, especially when the scrollwheel is somewhat broken.
As someone that habitually highlights what they are reading it was generally beyond useless for me. It was actively making me mad when I accidenatally pasted some non-sense because I just highlighted a paragraph before and accidentally inserted it into something.
> only made because the same feature does not exist in MacOS.
Or in anything that's not X?
Speaking personally for me only, I don't think it's a great thing. The <however many> clipboards on Linux is... not really a great thing. I for one never know which of the buffers contain what. And this is compounded by the fact that selection may or may not overwrite what's in one of the buffers, and middle click may or may not paste whatever was in that buffer. Additionally compounded by how inconsistent the behavior is across apps.
I, for one, use the different clipboards concurrently all the time, with "highlight & middle-click" probably being the one I use most often. It's the most convenient for me most of the time:
- only two interactions (one drag & one click)
- completely mouse-based (no keyboard interaction necessary)
If you have anything else branching/referencing a commit after the reword commit that isn't part of the branch you are rebasing you now have all those references still pointing to the old commit and need to go through every one of them to fix them.
Which is a reminder that maybe `--update-refs` should be the default for `git rebase -i`. It's great that it is now going to be the default for both `git replay` and `git history`, and I know why git is conservative in updating defaults, but at some point there's a benefit to updating the defaults. (I'd also argue that `-i` itself should have long been the default for `git rebase`. Also, while we are at it, probably `--autosquash` should be default.)
I wish that git would auto check for a `.githooks` directory in the repo root and prompt on first clone if the `core.hooksPath` should be changed for this repositry and when pulling any tracked file in hooksPath causes a warning (though this still leaves out the case that some hook just invokes a script in the repo outside the dir).
There is a reason that pilots get basically told the ins and outs of a specific plane. Imagine the outrage if people need to do month long training for a specific car just to be able to drive it (and not just a general "here is how cars roughly work and the laws of the road").
The worst part is that Windows does ship cURL as a binary at `C:\Windows\System32\curl.exe` (may be dependent on some optional feature, dunno). Nowadays it does invoke this for me on my system, but I don't remember if I did something for this to be the case.
I am p sure Showdown only still exists because it would crater their official VGC league if they'd shut it down. And with Champions out now it is slightly more likely they would go after it, but they know that it isn't possible to iterate and test teams as fast in it as it is in Showdown (and I doubt they plan on changing that considering the limitations seem very intentional).
They all started out as mods to games. DotA specifically was a Warcraft 3 mod and ended up making Blizzard change their stance on such things because they lost such a massive IP to a different company. PUBG started as an Arma 2 mod and TF was a Quake mod. All the mendioned games effectively have their origins in mods for other games and likely wouldn't exist (at least in the form they are today) if that weren't for that, is what they presumably were indicating.
It was a "hit game" while it was still a mod. They were able to find investment to graduate to a standalone game because they already had a player base in the tens of thousands.
> Republicans may not like porn, but they put the onus where it belongs, on the operator, not on the OS.
While that might be true, I can't agree with the implication that this is better in any way. Having the onus on the operator forces you to have to send some form of verification out to all such operators you want to visit and they have repeatedly shown they are NOT capable of securely and privately handling that information.
First time I heard someone call it blue-green OS updates instead of A/B OS updates.
reply