• 7 Posts
  • 727 Comments
Joined 7 months ago
cake
Cake day: November 12th, 2024

help-circle

  • Hjkl are superior to arrow keys once you get used to them.

    I disagree with this point. I am able to use them quite functionally and I still want my arrow keys, because they are arrow keys. Also, you can use them without exiting INSERT mode.

    I do however, agree with your last point.[1]

    Oh, and I also don’t like the pseudo ergonomics of mechanical keyboards.
    All they do is make it harder to use with a more relaxed hand position.


    1. I agree with the fact that you disagree with me. Nothing else. ↩︎














  • One +ive for nano is that it has general commands listed down below, by default.
    So, as long as you understand ^ and M-, which you are expected to (idk why, ask sbd else), if you have been using Linux CLI, you will at least know how to exit.

    Oh, and I just realised: it also says “[ Welcome to nano. For basic help, type Ctrl+G. ]”, where it explains what ^ and M- are.

    So nano could be considered an accessibility program for people who are new to the GeNerally Used CLI, while vim is the thing you will configure for yourself when you know what you want.
    Oh and I am definitely configuring it. I hate the hjkl for movement. I have arrow keys and I am going to use them. And I am not buying your 60% mechanicals no matter how much you make sure that 100% keyboards are not available with good keys.


  • What makes stuff like the [X] button on the corner and Alt+F4 intuitive?
    Multiple years of having used MS Windows and similar looking software as a student.

    They got the marketing part right here, at least.

    But if we are being inclusive, nothing really is intuitive.


    I have seen BTech graduates struggle with installing software using the Wizard that is so omnipresent on Windows, so I don’t expect anything to be intuitive at this point.


  • Agree. If it’s not part of the IDE I am using, prefer a terminal window.
    Even if it is in the IDE, in most cases, use the terminal.
    Unless some functionality is adding value, like getting a git log for the current file, or in-place git blame, or even for a specific line, which would be considerably longer commands to type and IDEs tend to give output with colours and hyperlinks to corresponding commits, which make stuff faster rather than slower (unlike in case of simple commit/stage/push commands).



  • Well, considering that Kinematics 3D [1] uses Z-up and the main reason for Y-up being the 2D monitor having been the primary target for graphics output (where X and Y would have been taken and mapped first, requiring Z to be added when converting the paradigm to 3D) back when these things were started and us, slowly transitioning to having the same application being usable with both - AR/VR tech and monitors[2], we might as well all go with Z-up from the start.


    1. an academic subject, which should supposedly be your first introduction to a 3 dimensional coordinate system after the pre-introduction back in Kinematics 2D and pre-pre-introduction when learning the number line. i.e. If the academic curriculum was sensible ↩︎

    2. which would mean that in some cases, the user might be seeing some axes-gimbal, requiring a translation layer later anyway and in this case on the application developer’s side, which makes it a cognitive load ↩︎










OSZAR »