MacOS Better ip info in terminal One particular painful point, coming from linux, was the ip command in the Terminal. The Default MacOS ifconfig command is very - well let’s say “old fashioned” :) Coming from Linux you mostly use ip for everyting ip a to display your interfaces ip r your routes, and so on. Luckily you can install the iproute2 Package on MacOS which give you the ip command. ...
Switching to MacOS after decades on Windows and Linux felt strange in many places. Things work somehow, but not quite how you expect. One of the first oddities I ran into was the keyboard mapping. Not Talking about CTRL-ALT-META-CMD stuff, this is a whole “getting used to” learning curve on it’s own. But if you’re using a regular “IBM PC” layout which is mostly identical on Windows and Linux Desktop, on macOS some keys act… unpredictable. Specifically, Home and End keys don’t do what you would expect them to do. Instead of jumping to the start or end of a line, they scroll entire documents or behave differently depending on the app. In editors like VS Code? No problem, they work fine. But TextEdit, Office or some others and suddenly they behave totally different. ...
One particular painful experience I had under MacOS was that it seems not to be possible with on-board settings to configure which program / action should be used on execution of a Link. Similar as you would choose a default Browser or Email app, this is needed for far more than just the browser. e.g.: open mailto:// links with outlook open ssh:// links with kitty-term open ftp:// with transmission and so on… ...