![]() I did it when my knowledge about Linux wasn't that great too. I did install Arch two times on a macbook and I never had any problem. That's what I try to offer with the book: flexibility. Regarding the number of posts of people trying to install Arch Linux on a macbook: I think you would have the same number of post on Ubuntu forums if people tried to install Ubuntu on a macbook, but I would say nobody tries it because the install doesn't offer enough flexibility to do so. If your install for Ubuntu doesn't work, good luck to fix the problem. ![]() You could say the same for everything regarding computer: if macOS begins to crash, you need to solve the problem. To me it boils down to one thing: yes it is that simple if it works. Of course not, especially when these are not as common and u wish to perform a task with a low cognitive load, as in these cases using the mouse requires less mental effort than keybindings. However as one already said, every absolutist answer is dubious, and that doesnt mean using the mouse to setup a GUI or click on something in ur browser is a waste of time. These, and things like silence in a Library and mouseless development all point mostly to the same thing. The color does not demand his attention, the soundless machine doesnt interrupt him. Thats why Torvalds famously painted his walls pastel green and is very anal on having a soundless machine. This gives me more time to focus on the actual code and lets me concentrate through longer periods of time on said code. For me, keybindings do the same because Im faster and perform mechanical/mindless actions to move around the code/PC. So thinks like working with less interruptions or quiet places lead exactly to that, less mental context switches. This is not ideal since depending on your work and how complex ur code is, you may find it hard to place urself again mentally at where you were when you were thinking of item A, PRIOR to the context switch. That sometimes, again in my experience, leads me to more context switches.Ĭontext switches are when our brain is thinking about item A and then, for some reason, goes and thinks about item B (switches). Less thinking on keybindings/mouse clicks = more time thinking on code.įinally, the big one is, sometimes dragging ur mouse across the screen even though may seem fast and harmless requires, for me at least, a tiny bit of concentration and time to aim. Keybindings, when muscle learned do not require any thinking after some time. The central idea of these tools is to REDUCE COGNITIVE LOAD and/or REDUCE THE NUMBER OF CONTEXT SWITCHES during work. The effectivity is not due to the actual speed of typing in a keybinding in comparison to a mouse click. The same way keybinds in vim are effective once the muscle memory is there, so are keybindings to change desktops/show-windows/change-tabs/launch-apps and so on. The thing about mouseless development is not about being cool or just doing it for doing it sake of doing it. If you want to know why, I wrote a bit about it.
0 Comments
Leave a Reply. |