• Pfnic@feddit.ch
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    How is a MacOS only editor without extensions going to gain enough traction to be widely adopted?

    • th3raid0r@tucson.social
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      No kidding. One of the YouTubers I followed was really shilling Zed editor. He didn’t seem to mention that it was Mac only.

      Well, I guess it’s back to neovim on kiTTY terminal for me.

      Sometimes I swear Mac based developers think the world revolves around them.

      • NovaPrime@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        You’re already on a superior editor friend. Don’t fall for the propaganda of lesser tools (that of course being anything not neovim)

        • th3raid0r@tucson.social
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Eeeehhhh, I was kinda jealous of one of my coworkers Doom Emacs setup. He had automated like 80% of his own job with it. Still haven’t bothered to try to learn it myself. One of these days…

      • AVincentInSpace@pawb.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        1 year ago

        If you’re a fan of neovim I’d like to take this opportunity to give Neovide a shout. It’s essentially a purpose built terminal emulator that can only run Neovim and has some fun extensions with that in mind, like the ability to configure font, window size, fullscreen, window opacity etc. using Vim commands, implement sub-character scrolling, let Neovim floating windows have transparency, and have fun little animations when the cursor moves. It also has support for all the modern terminal emulation essentials like truecolor, ligatures, and emoji. https://neovide.dev/

        • th3raid0r@tucson.social
          link
          fedilink
          arrow-up
          0
          ·
          1 year ago

          I’ve tried it before, it’s fine but had issues running on wayland last I tried. Did they fix the wayland issues? Looking at the issue tracker it seems like there are still a few open Wayland issues.

          kiTTY by contrast has had Wayland support for about as long as I’ve used it.

          • AVincentInSpace@pawb.social
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            I’ve been using it exclusively with Wayland for about a year now and I’ve yet to have any issues. YMMV however.

    • xlash123@sh.itjust.works
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      They are tracking support for other OSes, and I took a look at the Linux roadmap, and they’ve made some good headway from the last time I looked. I would use it for its UI performance. I don’t like how everything these days use Electron. It also supports Language Server Protocol, so adding extensions for languages should be fairly simple for the community to do. The multiple collaboration seems cool too, although I think most devs would seldom use it.

      • Ethan@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        VSCode has tons of features that save a lot of time. Unless Zed manages to get close to feature parity, I don’t see how it can complete from a productivity point of view. VSCode’s UI performance isn’t stellar but it’s not nearly bad enough to counteract the productivity boost I get from its features.

  • toastal@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Church of Emacs vs. Cult of vi is the only true rivalry. Enlightenment will only be found taking one of these paths.

    • misty@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      1 year ago

      I recently learned there are people that think emacs and vi are bloated. They like acme or sam or something. Iceberg is so deep.

      • T156@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        When you think of a bloated text editor, you would not expect VI to be that. If anything, it’s closer to the opposite.

        • misty@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          1 year ago

          Check this out. It puts everything I thought that was, you know, more ethical to use to the harmful section and suggests some unknown and probably not very useful today stuff. Can someone explain if they have good points or not?

          • T156@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            1 year ago

            Unclear. They don’t give their reasoning beyond “complicated = bad”, and very specifically leave it up to the imagination of the reader.

            While they make some interesting points with regards to overcomplication and scope creep, there are also good reasons why we’re still not using programs like ed as text editors, such as it being arcane and unintuitive.

            vi will at least helpfully point out :exit is not an editor command. Instead, ed will not-so-helpfully point out ?.

  • algernon@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    The single best thing I like about Zed is how they unironically put up a video on their homepage where they take a perfectly fine function, and butcher it with irrelevant features using CoPilot, and in the process:

    • Make the function’s name not match what it is actually doing.
    • Hardcode three special cases for no good reason.
    • Write no tests at all.
    • Update the documentation, but make the short version of it misleading, suggesting it accepts all named colors, rather than just three. (The long description clarifies that, so it’s not completely bad.)
    • Show how engineering the prompt to do what they want takes more time than just writing the code in the first place.

    And that’s supposed to be a feature. I wonder how they’d feel if someone sent them a pull request done in a similar manner, resulting in similarly bad code.

    I think I’ll remain firmly in the “if FPS is an important metric in your editor, you’re doing something wrong” camp, and will also steer clear of anything that hypes up the plagiarism parrots as something that’d be a net win.

    • GeniusIsme@lemmy.world
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      1 year ago

      If FPS is NOT an important metric in text editing, you are doing something wrong. Otherwise, good points.

  • Korne127@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    It’s funny how many people online use VS Code. But I’ve heard that this might be a US thing. Here, everyone uses the JetBrain products (which are far superior imo).

    • Carighan Maconar@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      1 year ago

      To be fair, there’s a big difference.

      VS Code is a text editor / IDE. Compared to something like Notepad++, it’s super slow to open/load, its UI feels laggy at times, and it’s just overkill for opening a text file. Compared to specialized log viewers, it struggles with large files and is generally super slow.
      But compared to “full” IDEs like IntelliJ, it’s marginal in coding features, lacking important analysis and testing support, plus integrations with ~everything.

      If you find yourself in the middle, like many JS developers do, not actually needing the biggest IDE but also needing more than just a text editor, it’s a fine tool. As a Java Backend Dev, VS Code feels like a joke if applied to that, OTOH.

      • PHLAK@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        arrow-down
        1
        ·
        edit-2
        1 year ago

        “all your vscode extensions still work fine” is definitely not true. Sure a vast majority of them probably do, but certainly not all of them.

        I still prefer it over full VS Code though.