It's good advice for JavaScript because JavaScript really fucked this up. But it's a bit confused to say "don't use functions as callbacks unless they were designed for it".
The problem isn't really even directly related to callbacks.
A better way to state it would be "don't pass extra arguments to functions that don't use use them".
I think this actually happens when you do a speed test. Bittorrent being throttled? Hmm let me just run a speed te.. oh it's working now is it?
I mean, you can use tabs consistently within a project. The only thing I'm aware of that actually bans tabs is YAML and... well, you can go a long way by always doing the opposite of what YAML does.
That's definitely better, but still not as good as Windows. If you click on an area that isn't a drag source it should be raised on button down. I presume it doesn't do that?
So, Windows has fully optimal behaviour here:
If you click on an area of the window that cannot be dragged from, it raises it on mouse-down.
If you click on an area of the window that can be dragged on, it doesn't raise if you start a drag, otherwise it raises it on mouse-up.
That's the desired behaviour. I agree people didn't really explain that clearly.
I haven't looked into it for over 20 years but as I recall it is impossible to do this with X11. I have no idea if Wayland added some kind of support for this, but I would be quite surprised given how long it took them to do screenshots.
Part of the difficulty is that you need to somehow query an app on mouse-down if it might start a drag. I have no idea how Windows does that... but... they solved it decades ago.
I wonder if they'll ever fix this 24 year old bug...
https://bugs.kde.org/show_bug.cgi?id=36065
(Note they closed it but it doesn't sound like they actually did fix it.)
That said, consistency trumps philosophy.
If only we had collectively agreed on a number of spaces! Sadly it seems split fairly evenly between 2 and 4 so we don't even get consistency.
IMO it's because open source developers commonly use editors that have poor support for tabs, like Vim and Emacs.
Tabs are definitely better but to use them properly you do really need a "visualise whitespace" option enables. Emacs does it like this and Vim like this. Both awful.
Possibly also a bit because tabs for indentation, alignment for spaces is just too complex for most developers. Hell most can barely even get spaces right. I work in a couple of languages without an autoformatter (e.g. SystemVerilog) and some of our files are a joke. A mixture of 2 and 3 space indentations, sometimes on the same line!
That's sounds very unusual. Presumably you've got some interviews? I would ask some of them for some honest feedback because it sounds like you're doing something wrong. Also try talking to recruiters...
Also maybe do some networking if you're that experienced? Ask old colleagues?
Honestly I don't need to know anything about it at all except that it's a payment system designed by GNU to know that it stands zero chance of success.
GNU are uber-geeks that do not comprehend usability at all. They think everyone is happy to go to key exchange parties and run their own servers and so on. There's absolutely no chance this is understandable by normal people.
Impressive. I would imagine it is very difficult to get native performance without ISA extensions like Apple had to do for TSO and other awkward x86isms.
I would guess someone will make a RISC-V extension for that stuff eventually, though I haven't seen anyone propose one yet.
Don't be an idiot.