• 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.

    • the framework is actually pretty cool, it uses SDFs to render ui (which is definitely not the most efficient solution but it’s really, really cool (it means they can use the same system to render shapes, text, and literally everything else which can be described by a signed distance formula)

  • John fucking Carmack codes in Microsoft Visual Studio, and that’s the guy who wrote Doom, the single most important piece of software in history of Man and I’m not even exaggerating.

      • Probably the reason Vs Code has so many extensions, is that they can easily (low barrier of entry) be created in JavaScript. This is mainly due to the fact that VS Code is an electron application, itself written in JavaScript.

        It sucks for zed, because these extensions allow users to customize their workflows to their needs which decreases their liklihood to switch to a different editer. I think the message of the post is that VS Code’s large and mature extension ecosystem will somewhat impede users migrating to zed.

        The irony in this is that the people behind zed and atom were the ones who initially created electron for atom.

  • I liked Atom, performance was tolerable on my overpowered machine, but MS killing it just sent me back to Vim and modernizing my plugins.

    Zed positives: Metal rendering. I use a Mac, so one platform’s fine. But negatives: Rust, so I can’t/won’t touch any internals, and I loathe the Rustacean propaganda wing. No extensions yet. Config is another stupid json file.

    You know what’s great about vimrc? It’s easy to put in a few config commands, and then you realize you’re working in the scripting language. You don’t have to switch to a whole new file format. Thanks, Bram.

      • I often had to poke around inside Atom to see what it was really doing, what some bug was, and to figure out how to write or configure extensions. I don’t as often do that with Vim, but it’s pretty clean C.

        Do you not look inside the overly complex tools you use, especially beta ones? The whole appeal of “open source”/“free software” etc. is you can read the code. But if it’s in something you can’t stand, that’s a disadvantage.

  •  Gargari   ( @Gargari@lemmy.ml ) 
    link
    fedilink
    English
    34 months ago

    For the most part it’s a business for them, and that’s what matters, they target Mac users because they are more likely to pay. If you need speed and customization there is neovim and Helix (Rust based). From users to users, no business interests here. Or VSCode just works for almost everyone.