Zed is a modern open-source code editor, built from the ground up in Rust with a GPU-accelerated renderer.

  • AVincentInSpace@pawb.social
    link
    fedilink
    English
    arrow-up
    20
    ·
    7 days ago

    I still do not understand why Zed makes such a big deal about being GPU accelerated when you’ll be hard pressed to find a single text editor nowadays that isn’t.

    • Bilb!@lem.monster
      link
      fedilink
      English
      arrow-up
      2
      ·
      6 days ago

      Yeah, I don’t see why I should care about that. Gimme some crazy graphical effects, particles and shaders!

  • jaxxed@lemmy.world
    link
    fedilink
    arrow-up
    10
    ·
    7 days ago

    Zed seems cool, but not much better than other options. I am still kind of thrown off by the immediate GH/CoPilot integration. Am I the an old man left in the caves of feeling that I don’t need the AI help?

  • Nora@lemmy.ml
    link
    fedilink
    arrow-up
    7
    ·
    7 days ago

    I tried saving to a file that required root and it didn’t give any prompt to enter the password. On VSCodium normally if you are trying to write to a file that requires sudo then it prompts you.

    Is there a way to save to root files with Zed?

    • THCDenton@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      7 days ago

      Sounds pretty cool. Sometimes ill do a quick series of edits in vim and it fuckin chugs. I’m definitly gonna try it

    • The Cuuuuube@beehaw.org
      link
      fedilink
      English
      arrow-up
      3
      ·
      6 days ago

      Pretty common feature. Sublime, Lapce, VS Code, certain Emacs distributions, certain NeoVim GUIs… We live in a world where a lot of people have GPUs and CPUs aren’t getting faster so if you want to get more work done (ie, running LSPs, tree sitter, completion engines, snippet engines, debuggers etc) you need to offload some of that work somewhere

    • kazaika@lemmy.world
      link
      fedilink
      arrow-up
      27
      ·
      8 days ago

      I mean its already in the nix repos as well as homebrew which means its essentially taken care of

        • pukeko@lemm.ee
          link
          fedilink
          English
          arrow-up
          5
          ·
          8 days ago

          It appears to be a couple of versions behind … and have some issues with dynamically linked libraries that hinder LSPs. Neither of these is Zed’s fault. I’m sure the packaged version will be up to date momentarily (given the interest in Zed, sooner rather than later). Not sure how easy the LSP thing will be to fix, though there are some workarounds in the github issue.

          • priapus@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            5
            ·
            8 days ago

            yeah the editor is being updated way too fast for nix to keep up. I’m sure it’ll be easier once it has its stable release. I see the have a nix flake in the repo, it would be great if they added a package to the outputs instead of just a devshell, nix users could easily build it from master or whichever tag they want.

            There are solutions in this issue to the LSP issue. The editor would need to be built in an fhs-env, or they will need to find a way to make it uses binaries installed with nix instead of the ones it downloads itself. VSCode had a similar issue, so there is a version of the package that let’s you install extensions through nix, and another that uses an fhs-env that allows extensions to work out of the box.

    • WFH@lemm.ee
      link
      fedilink
      English
      arrow-up
      17
      ·
      8 days ago

      A curl piped into a shell or some unofficial packages from various distros.

      At this point I don’t get why these projects are not Flatpak-first.

      • skilltheamps@feddit.org
        link
        fedilink
        arrow-up
        11
        ·
        8 days ago

        Security wise it doesn’t matter, you run the code they wrote in any case. So either trust them or don’t. Where it matters is making a mess on your computer and possibly leaving cruft behind when uninstalling. But packages are in the works, Arch even has it since before linux support was announced officially.

    • Telorand@reddthat.com
      link
      fedilink
      arrow-up
      7
      ·
      edit-2
      8 days ago

      That was my first thought as well, but I will say that uBlue distros had a signing issue preventing updates recently, due to an oversight with how they rotated their image signing keys, and the easiest (maybe only?) solution was to pipe a curl command to sh. Even though uBlue is trustworthy, they still recommended inspecting the script, which was only a few lines of code.

      In this case, though, I dunno why they don’t just package it as a flatpak or appimage or put it up on cargo.

      Edit: nvm, they have some package manager options.

    • TunaCowboy@lemmy.world
      link
      fedilink
      arrow-up
      6
      ·
      8 days ago

      It is worrisome that all the smug elitists are too incompetent to just leave off the pipe and review from stdout, or redirect to a file for further analysis.

      Same people will turn around and full throat the aur screaming ‘btw’ to anyone who dares look in their direction.

      • skilltheamps@feddit.org
        link
        fedilink
        arrow-up
        11
        ·
        7 days ago

        By that logic you have to review the Zed source code as well. Either you trust Zed devs or you don’t - decide! If you suspect their install script does something fishy, they could do it just as well as part of the editor. If you run their editor you execute their code, if you run the install script you execute their code - it’s the same thing.

        Aur is worse because there usually somebody else writes the PKGBUILD, and then you have to either decide whether to trust that person as well, or be confident enough for vetting their work yourself.