I’m trying out Obsidian for taking notes, and this made me laugh.

    • bioemerl@kbin.social
      link
      fedilink
      arrow-up
      17
      arrow-down
      2
      ·
      9 months ago

      Vim really is an IDE, not a text editor. It’s usable as an editor but overkill.

      Nano serves a difference purpose. It’s like telling someone on a bike that a mustang is better.

      • Kogasa@programming.dev
        link
        fedilink
        arrow-up
        19
        arrow-down
        3
        ·
        9 months ago

        Vim is absolutely not an IDE. It has no integrations with any language. It’s just a powerful text editor. You can add language plugins and configure it to be an IDE.

        • Bo7a@lemmy.ca
          link
          fedilink
          arrow-up
          8
          arrow-down
          3
          ·
          9 months ago

          No offense intended here - But why is this being upvoted?

          vim absolutely is an IDE if that is how you want to use it. Syntax highlighting, linter, language specific autocomplete, integrated sed/regex. And much, much more.

            • bioemerl@kbin.social
              link
              fedilink
              arrow-up
              9
              arrow-down
              1
              ·
              9 months ago

              “You see here my car has positions for all the parts of a boat so it’s easily made into a boat and it’s already waterproof but it’s just a normal car”

            • naught@sh.itjust.works
              link
              fedilink
              arrow-up
              7
              ·
              edit-2
              9 months ago

              I don’t know that’s a fair anology. Vim does what a IDE can do without almost any setup with LazyVim and Lunar Vim and a bunch other prebaked setups. Instead of writing your vscode config in JSON or using a GUI, you can use lua. It’s more like turning car into a track car or something where you’re already a mechanic

          • Kogasa@programming.dev
            link
            fedilink
            arrow-up
            7
            ·
            9 months ago

            Syntax highlighting, linting, and language specific autocomplete are features supported by plugins and scripts. Plain, simple vim is a powerful extensible text editor. The extensibility makes it easy to turn into an IDE.

              • Kogasa@programming.dev
                link
                fedilink
                arrow-up
                5
                ·
                9 months ago

                Yeah, there is a generic syntax highlighting scheme. I had forgotten because it’s not very good for some languages, I’d replaced it with a LSP-based implementation years ago.

        • Frank Müller@mastodon.social
          link
          fedilink
          arrow-up
          1
          arrow-down
          2
          ·
          9 months ago

          @kogasa Hehe, shit, so long done something wrong as I use #vim as an IDE. Okay, some own helpers, some plugins, the direct integration for #golang via LSP and since some time also ChatGPT and Copilot. But hey, it’s no IDE. 🤪

          • Kogasa@programming.dev
            link
            fedilink
            arrow-up
            3
            ·
            9 months ago

            Like I said, Vim can be made into an IDE by adding and configuring plugins. Basic barebones vim is designed to be a powerful, extensible text editor, not an IDE.

              • Kogasa@programming.dev
                link
                fedilink
                arrow-up
                5
                ·
                9 months ago

                I’m not a text editor. But anyway, would you call a shell script that invokes python.exe $1 a Python IDE? Why would you? Vim isn’t designed to facilitate the use of vimscript, vimscript is just an extensibility feature of Vim.

                • bioemerl@kbin.social
                  link
                  fedilink
                  arrow-up
                  3
                  arrow-down
                  1
                  ·
                  9 months ago

                  Vim isn’t designed to facilitate the use of vimscript, vimscript is just an extensibility feature of Vim.

                  Vim is designed to edit code, by the people who were doing it back in the 70s and all of its features are there to enable better, faster, and more efficient editing.

                  It has scripts for the sake of those scripts enabling integrated developer features. Because they’re part of vim they’re in the environment and the program is used predominantly for development.

                  • Kogasa@programming.dev
                    link
                    fedilink
                    arrow-up
                    2
                    arrow-down
                    1
                    ·
                    edit-2
                    9 months ago

                    Vim is designed to edit code

                    To edit text files. It doesn’t matter if it’s code, configuration files, or plaintext. There are no interpreters, no compilers, no debuggers, nothing designed to support any particular framework or language or workflow. All of that is possible to add through the extensibility features.

                    Vim is a highly configurable text editor built to make creating and changing any kind of text very efficient.

                    Vim is an advanced text editor that seeks to provide the power of the de-facto Unix editor ‘Vi’, with a more complete feature set.

                    Vim is a highly configurable text editor built to enable efficient text editing.

                    https://vim.org/

                    Vim is a text editor which includes almost all the commands from the Unix program “Vi” and a lot of new ones. It is very useful for editing programs and other plain text.

                    https://vimhelp.org/intro.txt.html#intro.txt

                    It has scripts for the sake of those scripts enabling integrated developer features.

                    Those features aren’t enabled nor integrated. They’re added to Vim at its extensibility points. Baseline vim doesn’t have them.

      • Slotos@feddit.nl
        link
        fedilink
        arrow-up
        12
        ·
        9 months ago

        Nano is for those that occasionally edit text files from a terminal.

        Vim is for those who make a living out of it.

        • Captain Aggravated@sh.itjust.works
          link
          fedilink
          arrow-up
          2
          ·
          9 months ago

          There’s a guy on Youtube who does programming language tutorials/demonstrations. Like he starts out with C++ and in one hour you’re at object inheritance, crash courses I guess is the term for them.

          He did one video that was as much a Vim tutorial as a tutorial for this language. “Press 3k, then enter, then i, and type “std::out(“whatever C syntax is”)” and then hit escape and…”

          For teaching something like a little bit of Python or a little bit of Bash or whatever, I’d rather use Nano, because you can learn how to use it in seconds. Vim is an amazing tool but lord don’t try to cram a Vim tutorial into another already technical tutorial.

      • timbuck2themoon@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        8
        ·
        9 months ago

        If you edit files a lot vim is worth its weight in gold. Nano makes me want to kill myself as everything takes so much longer.

        Nano is perfectly sufficient for a very rare edit.

        • bioemerl@kbin.social
          link
          fedilink
          arrow-up
          7
          arrow-down
          1
          ·
          9 months ago

          Vim absolutely chews through anything you throw at it. Lots of times we need data formated or lots of SQL queries and I’m the go to guy because I understand vim macros.

          Especially if you have any form of RSI.

          I wonder if it would be possible to make a user accessable way to expose similar power to the common user.

        • bioemerl@kbin.social
          link
          fedilink
          arrow-up
          2
          arrow-down
          1
          ·
          9 months ago

          Not really, or that doesn’t feel right to my. Word and notepad basically still do the same thing except for that word lets you add style.

          Like a manual vs an automatic car, maybe?

          • frezik@midwest.social
            link
            fedilink
            arrow-up
            5
            ·
            edit-2
            9 months ago

            Word is a WYSIWYG editor. We don’t talk about it much these days because it’s just how things are done, but it took a long time for the industry to come up with a way to display text on screen with rich formatting and have it come out the same way in print. There was a lot of buzz around it in the late 80s and early 90s.

            Word solves a completely different problem than an IDE. Notepad is a raw, minimal tool that could be built on for either WYSIWYG or an IDE.

    • uzay@infosec.pub
      link
      fedilink
      arrow-up
      5
      ·
      9 months ago

      It just makes a lot of stuff way easier once you know how to use it. Switching out a word for another: two button-presses, duplicating a line: three presses, deleting 500 consecutive lines: five presses

          • nickwitha_k (he/him)@lemmy.sdf.org
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            9 months ago

            How do we work this? Do we alternate between trying to ruin people’s lives with elisp and chasing the perfect .vimrc or lua - config? Maybe grab some bytes from /dev/urandom and send them to the editor whose first letter comes up first? What about holidays?

      • penquin@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        9 months ago

        But you can do all that with nano and it is straight forward and you don’t need to memorize any key combinations. I mean, I get it and no judgement here. I just use nano because it’s easy and quick.

        • prismaTK [any,use name]@hexbear.net
          link
          fedilink
          English
          arrow-up
          4
          ·
          9 months ago

          I think if you just need to edit a config file once in a while, nano is great, but if you’re writing substantial amounts of code, you’ll find vim a lot more capable.

          As long as you’re not a filthy emacs user, we can get along

          • penquin@lemm.ee
            link
            fedilink
            arrow-up
            1
            ·
            9 months ago

            I write my code in an actual IDE. And I use nano for only, like you said, config files and those little things. And I have never used emacs and I don’t even know how it looks like. I’m dead serious, I don’t even know what emacs is or what it does. lmao

            • nickwitha_k (he/him)@lemmy.sdf.org
              link
              fedilink
              arrow-up
              2
              ·
              9 months ago

              Emacs is basically a lisp interpreter packaged with a suite of “example” utilities, like a text editor. It’s one of the two historical editors used as terminal IDEs, along with vim. Emacs tends to take a more batteries, kitchen sink, web browser, games, IRC client, etc-included approach. It can seriously be closer to an OS in functionality.

        • r1veRRR@feddit.de
          link
          fedilink
          arrow-up
          1
          ·
          9 months ago

          You can also copy paste by manually copying text by hand, would call that a valid alternative to Ctrl-C/V?

    • r1veRRR@feddit.de
      link
      fedilink
      arrow-up
      2
      ·
      9 months ago

      I don’t understand the need for Ctrl-C/V, when manually copying the text exists. I know it’s snarky, but that’s the level of difference we’re talking about here. Or imagine, to delete a line, someone Right Arrows 50 times, then backspaces 50 times, instead of using the shortcut.