this post was submitted on 06 Feb 2024
12 points (92.9% liked)
Programming
17326 readers
242 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
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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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.
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.
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.