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
    19
    arrow-down
    1
    ·
    22 hours 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.

  • jaxxed@lemmy.world
    link
    fedilink
    arrow-up
    10
    arrow-down
    2
    ·
    21 hours 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
    ·
    1 day 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?

  • blackboxwarrior@lemmy.ml
    link
    fedilink
    arrow-up
    34
    arrow-down
    1
    ·
    2 days ago

    I am BEGGING for any editor other than VSCode to have decent remote development. I want to go open source but everything I’ve tried (remote-nvim, distant, tramp, vscodium, etc.) just doesn’t cut it.

    • ErnieBernie10@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      8 hours ago

      What I do is use distrobox or any devpod and install it in the container and launch from cli. Works perfectly for me.

      • The Cuuuuube@beehaw.org
        link
        fedilink
        English
        arrow-up
        0
        ·
        12 hours ago

        Pair programming over the net. The old school way is tmux and vim but to do that you and your partner need port 22 open and most enterprises are gonna be like “hell no you can’t let people connect to your company owned work laptop SSH into your machine”

    • finestnothing@lemmy.world
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      1 day ago

      Have you tried running doom emacs in tmux on the remote server and accessing it with ssh? Doom emacs is all the good of an emacs environment, all the good of vim keybinds, and they worked in a decent amount of optimizations so it only loads the necessary stuff on demand (mine has a startup time of just over 1 second, slower than vim but barely an inconvenience). Can write a quick script to ssh copy (or git pull) your current configs on the server so you only have to maintain one set of configs if you want

      scp ~/.config/doom/config.el username@server:~/.config/doom/config.el
      

      Run emacs in tmux if you want to keep the emacs session open across multiple ssh sessions

    • flux@lemmy.ml
      link
      fedilink
      English
      arrow-up
      11
      ·
      edit-2
      2 days ago

      Apparently Lapce has remote development as its core feature. But I only (re?)learned of it today…

      How didn’t tramp work out for you?

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

        It has Microsoft BLObs baked in as part of the build process. VS Codium is the FLOSS distribution of VS code’s open source code. Liveshare doesn’t appear in the package repo Codium uses (because of the Microsoft BLObs it contains as an extension). For work I manually download the live share extension VSX and load it into vscodium

    • SavvyWolf@pawb.social
      link
      fedilink
      English
      arrow-up
      36
      arrow-down
      1
      ·
      2 days ago

      So they’re doing the equivalent of VSCode(ium)'s extensions, but installing them automatically and not giving you the option to use alternatives?

      Blegh.

      • aaro@lemmy.world
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        2 days ago

        I think they auto install some binaries like nodejs that are required for baseline functionality, but have a popup window for additional language LSPs

        • hswolf@lemmy.world
          link
          fedilink
          arrow-up
          4
          ·
          2 days ago

          what if I wanted to use deno or bun? I don’t think that should be their decision to install “default” stuff that have alternatives

          I’m all for their improvement tho

          • aaro@lemmy.world
            link
            fedilink
            arrow-up
            7
            ·
            2 days ago

            I don’t see your point? Nodejs is installed in a custom directory and not added to PATH. It is used by Zed for providing npm support for extensions, and other things. I’m not a Zed developer so I don’t know exactly.

            It doesn’t prevent you from using deno or bun in any way.

            • hswolf@lemmy.world
              link
              fedilink
              arrow-up
              1
              ·
              17 hours ago

              I see, that’s greatif it is only locally installed and used, messing with PATH could, probably, break stuff like nvm or others

    • PushButton@lemmy.world
      link
      fedilink
      arrow-up
      12
      arrow-down
      9
      ·
      2 days ago

      Quoting the guy:

      “that rewriting those in Rust will take an eternity, so not sure what is actionable here, hence closing.”

      That’s Rust shining from all its glories here gentlemen…

      The best language, if there is nothing changing.

      That’s a thing to make a web server or a library that displays Fibonacci, that’s something else when there are humans with changing scopes…

      • boredsquirrel@slrpnk.net
        link
        fedilink
        arrow-up
        16
        arrow-down
        1
        ·
        2 days ago

        Its not Rusts fault, the devs are simply lazy and making insecure products, as they dont want to rewrite everything.

        • PushButton@lemmy.world
          link
          fedilink
          arrow-up
          10
          arrow-down
          2
          ·
          2 days ago

          That’s what I am saying.

          To quote you: “they don’t want to rewrite everything” …

          Writing Rust often implies major refactoring and it takes so much time to write that your requests go: “pewf” closed due to the amount of effort it takes.

          Anyway, been there, done that! Zig is probably the real future; it’s a joy to write, it compiles fast, clear to read, and safe.

          It has shared libraries and a proper integration with existing C/CPP code base.

          You should try it, that’s an amazing language with a real potential to replace the legacy.

            • PushButton@lemmy.world
              link
              fedilink
              arrow-up
              1
              ·
              20 hours ago

              Comptime replaces macros/reflection.

              It’s basically Zig code that runs at compile time in your code…

              No other “weird” language to learn; it’s zig all the way. What you would have written in macro is written in zig comptime.

              Even the build system is zig…

              Same for generics, it’s comptime…

        • PushButton@lemmy.world
          link
          fedilink
          arrow-up
          3
          arrow-down
          4
          ·
          2 days ago

          There are no patch, the issue has been closed as in rejected.

          There are a few tasks that are open that are loosely related, but let’s not mix things up.

          Moreover, I will take the words of the maintainers over a random potato on a forum.

          No offense…

            • PushButton@lemmy.world
              link
              fedilink
              arrow-up
              1
              arrow-down
              2
              ·
              1 day ago

              As I mentioned, a couple of tasks loosely related. The patch you are mentioning isn’t complete nor address the real problem.

              It is an ugly hack at best.

              Refrain from your urge to defend rust at all costs. You are sliding more and more toward the specifics of a project than the fact I stated about rust in general.

              If you still not get my initial point I’ve made, read this.

              That’s a long read explaining what I meant. My point was about Rust, not Zed or the developers of Zed in particular.

              And for the Zed editor, I wish them the best luck, it seems like a great project that people enjoy.

              Please feel free to comment and share your thoughts on the article above, my dear favorite nutritious veggie.

      • fxdave@lemmy.ml
        link
        fedilink
        arrow-up
        3
        arrow-down
        4
        ·
        edit-2
        20 hours ago

        I use rust only if we need performance, for small services. The industry does the same. People use node for backend but e.g. redis is in rust. It’s a good tool if you use it for the right stuff.

        EDIT: redis is not in rust, but e.g. aws writes many services in rust

  • bionicjoey@lemmy.ca
    link
    fedilink
    arrow-up
    188
    arrow-down
    3
    ·
    2 days ago

    Installer is piping curl into shell

    I thought we were past this as a society 😔

    • WFH@lemm.ee
      link
      fedilink
      English
      arrow-up
      15
      arrow-down
      1
      ·
      2 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.

      • ParetoOptimalDev@lemmy.today
        link
        fedilink
        arrow-up
        6
        arrow-down
        10
        ·
        2 days ago

        Flatpak is worse for debugging, development, and reproducibility.

        Its good for user friendly sandboxing, portability, and convenience.

        • eveninghere@beehaw.org
          link
          fedilink
          arrow-up
          1
          ·
          20 hours ago

          AFAIK it’s the copy cost for the memory. GPU makes sense only when the hardware allows this copy to go away. Generally, desktop PCs don’t have such specialized hardware.

          • Mia@lemmy.blahaj.zone
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            19 hours ago

            I don’t see why you’d have to copy all that much. Depending on the rendering architecture, once all the glyphs are there you’d only need to send the relevant text data to be rendered. I don’t see that being much of a problem even when using SDFs. It’s an extremely small amount of data by today’s standards and it can be updated on demand, but even if it couldn’t it would still be extremely fast to send over every frame. If games do it, so can text editors. Real time text rendering on the GPU is a fairly common practice nowadays, unfortunately not in most GUI applications…

            • eveninghere@beehaw.org
              link
              fedilink
              arrow-up
              1
              ·
              14 hours ago

              At this point I’m not expert enough to explain more details. You can check font renderers.

              Below is what’s in my mind but it’s just a guess.

              In typical PC architectures you have IO between the storage and the RAM, and then there’s the copying from the RAM to the VRAM, and editors maybe also want copying from the VRAM to RAM for decoration purposes etc.

              • Mia@lemmy.blahaj.zone
                link
                fedilink
                arrow-up
                1
                ·
                edit-2
                13 hours ago

                I am familiar with the current PC and GPU architectures.

                IO is a non issue. Even a massive file can be trivially memory mapped and parsed without much hassle, and in the case of a text editor you’d have to deal with IO only when opening or saving said file, not during rendering.

                As for the rendering side, again, the amount of memory you’d have to transfer between RAM and VRAM would be minimal. The issue is latency, not speed, but that can be mitigated though asynchonous transfer operations, so if done properly stutters are unlikely.

                Rendering monospaced fonts (with decorators and control characters) at thousands of frames a second nowadays is computationally trivial, take a look at refterm for an example. I suspect non-monospaced fonts would require more effort, but it’s doable.

                As I said at the beginning, it’s not impossible, just a pain. But so is font rendering in general honestly :/