sublime_text

> How large are the compiled binaries? > The executable itself is 2.2M [...] Bundle 95MB [...] > https://www.reddit.com/r/golang/comments/53tw4p/a/d7x2a91 People feared when many former Node.JS developers migrated to Go because they would probably migrate the same principles from the JavaScript community (NPM and the dependency hell). Now people will fear the migration of Electron-like applications to the Go ecosystem. I am glad that more and more web developer are stepping forward and contributing their skills to create desktop applications, but I still cannot wrap my head around the idea that embedding a giant non-efficient webview in every project is a good idea. At this point, a computer with +16GB RAM will feel like using one with only ~6GB because of the amount of Chromium instances open in the background. Someone reported yesterday

100% CPU since Build 3124 [0]. [0] https://github.com/SublimeTextIssues/Core/issues/1387

> With these latest changes, Sublime Text 3 is almost > ready to graduate out of beta, and into a 3.0 version. Wow, Finally! I have been using ST3 for several years (wow, years) and always wondered what is keeping the developer from labeling that version as stable. From all the issues reported here [1] I have never encountered one while using the editor for pretty much all my work. Those $70 are definitely worth every penny. Sometimes I cringe from videos featuring ST while using a non-registered license, this week it happened with a course from Google engineers via Udacity, Google engineers!!! As if they don't have miserable $70 to buy a license, I assumed they were in a rush and didn't have time to set the license which I hope they bought. Anyway, thanks for all the hard work Jon, and recently Will. [1] https://github.com/SublimeTextIss

I was trying to choose a Mac text editor recently; got it down to Atom and Sublime, and then discovered that both of them do code folding wrong. They think it's based on indentation, not syntax, so if you try to fold something like: if (something) { some code //commented-out code more code } It folds everything from the opening bracket to the comment, then stops. Both editors have had issues filed over this bug for years, which have been ignored. (https://github.com/atom/atom/issues/3442, https://github.com/SublimeTextIssues/Core/issues/101) I eventually decided to go with Atom; it's open-source, so I can at least aspire to fix the damn thing myself when I get annoyed enough.

Full disclosure: I'm the CEO & co-founder of Floobits, which makes pair programming plugins for lots of editors. I completely agree with you about the plugin APIs. Writing a collaborative editing plugin for Sublime Text was a slog. Not only were we limited by the plugin API, but we ran into show-stopper bugs.[1] SSL didn't work on some platforms.[2] ST2 shipped with a broken select() module broke on Windows. In contrast, Atom provided almost everything we wanted. And while we ran into more bugs, they were annoyances, not show-stoppers.[3] 1. https://news.floobits.com/2015/08/17/sublime-text-plugin-api... 2. https://github.com/SublimeTextIssues/Core/issues/177 3. https://news.floobits.com/2015/10/14/developing-atom-plugins...