@stephenll, thanks for sharing. As already stated by someone else (@deathaxe I think) on some other post around the forum, I think Sublime Text should focus more in being extensible by its users with the Core API/Packages, other than getting out of the box with tons of builtin features. But above of all, it should never do (drugs) crash/segmentation fault. By having very nice and bug free API for Packages Developers, Sublime Text would definitely benefit more because its dedicated Package Developers would definitely feel more confident and enthusiastic about maintaining and writing new extensions for Sublime Text, instead of abandoning Sublime Text and going away for some other editor where they can do better whatever they feel like. Sublime Text dedicated Package Developers usually are always around the Forum or GitHub issue trackers helping others in fixing their problems with Sublime Text through awesome and well written Sublime Text Extensions. But most times, Packages Developers and specially new Package Developers just give up from Sublime Text and go for some other editor because they cannot stand Sublime Text API bugs limiting their creativity. But they might as well go forth and back because they cannot find another editor to stand their high imagination and creativity, and then, they become old Package Developers for Sublime Text.
There is a main difference between using a proprietary software and building it by your own. With proprietary software you can just ask, until magically they get it done for you, their client. With open source software, you can ask, until someone get it done, or you can do it by yourself.
A more serious example would be the latest development build of Sublime Text which started crashing on my computer. I can only ask for them to fix, but they can keep ignoring me for ever and never fix it because it could only affect me or a very small ground of users, but none of their other million of users. Then, how I am supposed to work with some software which can keep crashing unnoticed? This is what really gets me pissed because after spend years building extensions and settings for Sublime Text, then, just some day, for an unknown reason, I may have to stick with some old and bugged (API bugged) version of Sublime Text for ever and there is nothing I can do about it, other can may be becoming multibillionaire and trying to gently put some billions under their assets/pockets, hopefully motivating they enough to fix the crashing and API issues I am specifically having. Or unless Sublimehq hires me, but even if so, it does not mean they would let free free to fix wherever I would like to and I can just end up writing new features they would like instead of fixing bugs.
I also got to the point where I cannot improve further some of extensions/packages for Sublime Text because of bugs or limitations on the Core C++ API. Then, all I can do is wait for some future version of Sublime Text to fix the API bug or limitation. But, even if some new version fixes the API bug, how it would go about the crashing issues I am having? It may still be crashing for ever, and again I got nothing to do about it, other than ask for them to fix it and stick with an old version of Sublime Text, which does not crash. However, old versions of Sublime Text are more API bugged than the latest version. Yes, miraculously sometimes they randomly seem to be fixing some old API bug. My guess, is that when they were writing a new feature, and they noticed the bug was disturbing their new feature, then they decided to fix the bug, otherwise their thousands of new users would notice the bug and start flaming hundreds of posts like
"-It is not working, help!", which is not good for sales, as they would probably not buy a license.
If I have been using VSCode from the beginning, instead of keep waiting for them to fix the crashes, the API bug or remove some API limitation, I could just it it by myself. Then, instead of spending my weekends and nights resting from my daily job, I could just spend they fixing VSCode crashes and API issues. At least, I would have an option to do something other than wait. This situation focus on how much easier is to develop Packages for Sublime Text, other than Extensions for VSCode. As you may already notice, with Sublime Text I can get much more time resting from my daily job, because I only need to wait for Sublime Text team to do something about its C++ Core API bugs and crashes/segmentation faults, while developing for VSCode, I would have no excuse to sit my ass on some corner and keep complaining about my issues not being resolved.
However, even If I had started using VSCode from the beginning, I am not sure I could get where I am here today with Sublime Text, because I do not know what kind of problems I would have to fix on VSCode. I guess I will get to know more when got the time and I start fixing the problems I already got on my todo list.
Also, I think another point should be considered. Even if VSCode is open source today, it does not mean Microsoft will keep it as open source tomorrow. Some unnoticed day, they can just came out and say that further developments of VSCode are now proprietary, i.e., VSCode will now become closed source (new versions of it), or they could stop developing it because they do not get more money to fund the project. Meaning, that further developments of the latest version available for VSCode are only now maintained by community, i.e., you and me in our free time on night and weekends. Then, instead of resting from our paying job, we can get to work even more and completely for free! Isn't this awesome?
Currently, major contributions for VSCode seems to be from Microsoft employers (as they work full time on it). It also seems that community volunteers are well engaged as described on the following on issue. Then, I think even if Microsoft bails out from developing new open source versions of VSCode, community volunteers could keep it running smoothly. It is very important to remember that, me, only by myself, I am nothing. Only a collaborative effort from a group of people can get somewhere for some big project as a full featured text editor. Meaning that, whatever I ever had built for Sublime Text, would definitely not be possible without the help of Sublimehq (for creating Sublime Text, as we know today) and several highly active community members/contributors and countless others which are anymore part of the Sublime Text community, because they already moved on from Sublime Text to some other editor as VSCode or a JetBrains IDE or they are well satisfied with Sublime Text as it currently is and just do not do any more contributions for it.
Then, just tell your users to build it from source. Recently, to build VSCode become simpler. Originally when I started with VSCode a year and half ago, took me 2 days until get it done right.
What seems to be the problem is that, you cannot distribute the main URL channel for the
"Visual Studio Code Marketplace", as described and still pending some resolution on the following issue:
I am not sure whether I can or cannot distribute binaries of VSCode. I think you could be slightly mistaken, I am not a Copyright Lawyer, but if I understand it correctly, in fact the binaries compiled and distributed by Microsoft website for VSCode are proprietary, but you should be able to build it by yourself at your home and share with others who trust you (your binaries files). At least, accordingly to VSCode license, it states:
After almost forgetting about it, there is also LimeText:
I love the Sublime Text editor. I have created several plugins to make it even better. One thing that scares me though is that it is not open sourced and the pace of nightly releases have recently been anything but nightly, even now that version 3 is out in Beta.
There was a period of about 6 months after the Sublime Text 2 "stable" version was released where pretty much nothing at all was communicated to the users about what to expect in the future, nor was there much support offered in the forums. People including myself were wondering if the product was dead and I personally wondered what would happen to all the bugs, crashes and annoyances that still existed in ST2. This lack of communication is a dealbreaker to me and I decided that I will not spend any more money on that product because of it.
As none of the other text editors I've tried come close to the love I had for Sublime Text, I decided I had to create my own.
Sadly, it seems the project had dried out of contributors and no new updates have been coming recently:
I would say the LimeText project is just missing me, as I am not over there writing and doing contributions for it. That is definitely an open source project, but has no one more working much for it recently. Whether I should start focusing my time on VSCode or LimeText is an interesting question. Let me see where I am going to end up few years from now. Hopefully, Sublime Text will be able to fix all its crashing issues and eventually its Core API for plugin development (i.e., for developers use, may be me, may be you reading it) gets improved and fixed.
This is the other side of "Open Source" projects, specially big project as a full featured text editor as LimeText. While VSCode and Sublime Text have teams of programmers working on it full time, open source projects usually do not get this privilege often as VSCode does. Because everybody has to pay their bills, and they cannot work full time on something for free or no food. Sometimes, open source projects get lucky as VSCode and have some big money supporting them financially, or some full pensioned programmers start working on it because they think it is to much fun. Most successful open source projects, are usually small enough projects and one or few guys can maintain it on their free time/weekends. Other times, even if they are big projects, they can have so much contributors from everywhere on the world, and everybody small contribution sum up to a big thing. Following this line of though, I will probably end up working more with VSCode development other than LimeText.
After looking over old posts on the forum, I found the following posts to be interesting to read:
I am going to revert back to Sublime Text stable build 3176 for few months to confirm whether it is crashing or not. After confirming it, I will go back to the latest development build available.
I just researched this topic on Google and found this awesome post by @leedohm:
The term “IDE” comes from Integrated Development Environment. It is intended as a set of tools that all work together: text editor, compiler, build or make integration, debugging, etc. Virtually all IDEs are tied specifically to a language or framework or tightly collected set of languages or frameworks. Some examples: Visual Studio for .NET and other Microsoft languages, RubyMine for Ruby, IntelliJ for Java, XCode for Apple technologies.
An editor is simply that, a tool that is designed to edit text. Typically they are optimized for programming languages though many programmer’s text editors are branching out and adding features for non-programming text like Markdown or Org Mode. The key here is that text editors are designed to work with whatever language or framework you choose.
The tradeoff here is that while you can generally get off the ground faster if you’re working within the realm of a given IDE, over the long term you spend a bunch of time retraining yourself when you inevitably change from one language or toolchain to the next. If you use an editor, you can continue to use the same workflows that you always have. Tools that you’ve built into your editor can be carried over to the next language and framework. Your editor becomes more powerful and more customized to how you want to work not just over years but potentially decades. Just ask people who use vim or Emacs … both of which have been available for over 25 years!
So, if you want something that you can just jump into and be productive right away in a specific technology, perhaps an IDE is what you’re looking for. If you want a tool that you can shape and customize into exactly what you want out of it even if it costs you some time up front configuring things, then an editor is probably more your speed
https://discuss.atom.io/t/eclipse-ide/32613 eclipse vs atom IDE. what are the differences?
This cited post by @leedohm wonderfully put into words and explains the difference and why I love and use Sublime Text instead of IDEs, but also explains why Sublime Text gets on my nerves when I constantly hit its limitations or problems directly coming from the C++ Core code, which is currently out of my control.
I think I am actually just sad because I love Sublime Text so much, and there is nothing I can do to fix new crashing bugs or a few bad old API bugs which are just getting older each day, instead of being fixed.