How is a MacOS only editor without extensions going to gain enough traction to be widely adopted?
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.
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/
Super cool, just installed this, and eager to spend a workday with it now, thanks!
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.
I’ve been using it exclusively with Wayland for about a year now and I’ve yet to have any issues. YMMV however.
You’re already on a superior editor friend. Don’t fall for the propaganda of lesser tools (that of course being anything not neovim)
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…
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.
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).
For jvm stuff definitley yes. For other things I often prefer VS Code.
Vscodium gang?
Represent! (It’s vscode with all telemetry and crap removed, all your vscode extensions still work fine)
“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.
Church of Emacs vs. Cult of vi is the only true rivalry. Enlightenment will only be found taking one of these paths.
I recently learned there are people that think emacs and vi are bloated. They like acme or sam or something. Iceberg is so deep.
Ed users have not found the internet yet, otherwise they’d be in the war too
When you think of a bloated text editor, you would not expect VI to be that. If anything, it’s closer to the opposite.
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?
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
edas text editors, such as it being arcane and unintuitive.viwill at least helpfully point out:exit is not an editor command. Instead,edwill not-so-helpfully point out?.
