I'm Gonna Try Zed Now (RIP VSCode)

158,260
0
Published 2024-02-13
Huge shoutout to the Zed team for their hard work on these changes, genuinely hyped about what y'all have here. I'm committed, gonna give Zed a real shot now

Blog post: zed.dev/blog/120fps

Check out my Twitch, Twitter, Discord more at t3.gg/

S/O Ph4se0n3 for the awesome edit 🙏

All Comments (21)
  • @ScottMaday
    User: "it doesn't work on my machine" Most developers: "not sure how to reproduce this so oh well" Zed: knocks on door
  • @Apoque
    Right now this makes me upset with Apple for making Metal instead of using Vulkan (or sticking with OpenGL) which were both cross-platform APIs
  • @bungbloopity
    I like Zed, and I really wanna use it as my daily, but without an extension system I just can't switch from VSCode.
  • @HiImKyle
    "vScODe KilLeR", i know its clickbait to call it that but it really isnt a vscode killer is it. its a mac only editor.. you can't kill competition when you dont compete at the same level
  • @Timely-ud4rm
    The millisecond ZED is made for linux and if it's made for my distro which is fedora I would start using it right away. It looks amazing and the fact they care so much about fixing there app even going to your house to fix it really shows how much they care.
  • @germandavid2520
    11:20 is a closure, the JavaScript equivalent would be something like this: handle.update(cx, (_, cx) => cx.present()).log_err();
  • @iamwillshepherd
    Awesome to see Nathan finally put out his text editor 🔥 . I remember talking to him about this and other stuff he wanted to do back in the day. I wonder if we’ll see some CRDTs powering collaboration coming from them soon 🤔
  • @sarjannarwan6896
    11:21, makes complete sense when you use rust. &mut cx (pass a mutable pointer cx), |_, cx| cx.present() is just a closure (like a lambda). Probably seems counter intuitive because you don't use rust syntax but if you do rust it is.
  • @smithastley1616
    Really want them to add more Vi keybindings. Some commonly used commands don't work. Also a debug mode.
  • @ahmadaccino
    tried it again and it runs so much smoother on the pro-motion. thanks theo
  • @DaxSudo
    This is a good freakin solution, what fun blog post and hella nerdy I love it.
  • @nixigaj11
    Will try it once they add Wayland support.
  • @DamonMedekMusic
    I really appreciate any company going the extra mile to build something with user experience in mind. Anybody can build a product, to make the product useful and user friendly takes a whole other level of dedication. Great job Zed! I'll still be using vscode for github co-pilot, and also theres a setting I like in vsCode to always keep my cursor in the center of my screen so I never need to scroll.
  • @Speykious
    Supporting both X11 and Wayland on Linux is just a matter of using the winit crate, Which already works very well on both platforms. Once you have the initial window initialization code, the rendering is mostly a Linux-wide problem that can be done either in OpenGL or Vulkan.
  • @d3stinYwOw
    As of Zed, their work on Linux support goes really great. Initial supporting bits are there. Check their repo, you would be shook :D
  • @alexh2665
    now I wanna try zed. I just wonder how it will run on my M3pro if he washing issues at first on M2
  • @m4rt_
    11:20 this: |a, b| a + b is a closure in Rust. the _ means that it doesn't care what the argument's value is. What you were seeing was them passing a value, then a closure to the update function. I personally would do this: handle .update(&mut cx, |_, cx| cx.present()) .log_err(); so that it would be slightly more readable, though it still requires some understanding of the syntax.
  • @TimBell87
    RIP VSCode? I don't think so, not when I have to shell out for a Mac just to use the competition.