Programming

17533 readers

251 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago

MODERATORS

snowe

Ategon

[email protected]

The New Code Editor Zed has a Strong Start, and is now Open Source (frontendmasters.com)

submitted 9 months ago by [email protected] to c/programming

9 comments fedilink hide all child comments

Zed, a code editors from the creators of Atom, has gone open source and seems to have a bright future awaiting.

top 9 comments

sorted by: hot top controversial new old

[–] [email protected] 10 points 9 months ago (2 children)

This is a nice editor. I don’t like the comparisons to Atom since some of us remember that as “the really bloated and slow predecessor to VS Code”. Whereas Zed is quite small and fast. Opening a shell panel is instant and makes VS Code feel slow.

Its strength is multi-user (their term: multiplayer) shared editing spaces. It also has quite good AI integration and supports Github Copilot too.

I am a little concerned that they started off commercial and then went open source. Open source is great! But this path sometimes means that the original developers no longer have the time/money/interest to keep developing it. I hope that’s not the case here because they’ve got the start of something good.

[–] [email protected] 5 points 9 months ago (1 children)

I am a little concerned that they started off commercial and then went open source. Open source is great! But this path sometimes means that the original developers no longer have the time/money/interest to keep developing it. I hope that’s not the case here because they’ve got the start of something good.

Developing a proprietary code editor is a blunder. The big players in the space are Vim, Emacs and VSCode, all of which are open source, so you can't outcompete those unless you go open source yourself. Being customisable and source-hackable is the key in making your product being liked by developers, obviously.

My bet is they simply realised the mistake and decided to fix it.

[–] [email protected] 5 points 9 months ago (1 children)

Is it a blunder? Tell that to Apple, Jetbrains, or Microsoft, each of whom have proprietary code editors that net billions of dollars of revenue.

It’s true, VS Code is open source, but it is developed almost entirely by Microsoft, by a large team of paid full-time programmers, designers, and PMs. It may be the most-used text editor in the world, but it isn’t developed by a team of volunteers who materialized around it because it was open source.

Instead, consider that making something open source is often just a marketing strategy — or a soft way to sunset a project.

[–] [email protected] 2 points 9 months ago

Is it a blunder? Tell that to Apple, Jetbrains, or Microsoft, each of whom have proprietary code editors that net billions of dollars of revenue.

I expected you to say that! The only mentioned company that has a proprietary code editor is Jetbrains with their Fleet. Visual Studio, XCode, most jetbrains products are IDEs.

IDEs are big, bloated products that don't need hackability because they already come prepackaged with everything. Code editors are different. Developers also like stuff being open source so they can put their trust into it — if everything goes to hell, somebody could fork it, which would save you from the need to find another properietary editor and change your workflow.

Ultimately, who develops OSS doesn't matter anymore. Even the Linux kernel, the thing that comes to mind to most people when they think of "open source", is developed by a lot of people working for corporations, on paid positions specifically to develop the kernel.

Instead, consider that making something open source is often just a marketing strategy — or a soft way to sunset a project.

I can't disagree with that, but my point is that if being an open source code editor is so important, then there is a bigger probability that the team behind Zed are fixing the mistake, rather then sunsetting the software.

[–] davawen 5 points 9 months ago

For the last point, they mentionned from the very start they wanted to go open source

[–] [email protected] 8 points 9 months ago (1 children)

i use macOS but don't use any software that isn't also available for linux (which Zed isn't)

[–] [email protected] 1 points 9 months ago (2 children)

Isn't one of the main macOS benefits the software?

[–] [email protected] 5 points 9 months ago

i just don't like feeling locked in at all.

[–] JDubbleu 2 points 9 months ago

Not OP, but my main preference for MacOS comes from the UI/UX of an absolute rock solid OS on top of a unix-like shell. I regularly go months without rebooting my machine with 0 issues like software hanging on wake.

I know there are a lot of exclusive creative apps, but all I really use my MacBook for is code, typical browser stuff, music, slicer/web interface for my 3D printer, and to interact with my home server. I'm not an open-source/Linux purist by any means, but pretty much all the software I use is widely available on all platforms. It probably helps that I bought a MacBook after growing up with Windows/Linux, so I came into it with a set of software I was familiar with that already existed on other platforms.