timmfin
One small pet peeve, I do wish more of the functionality in the menu bar (mac?) was available in the command menu (cmd+shift+p). I still fairly frequently try cmd+shift+p "Spel..." to try and turn on Spell check mode, but then realize I need to hit my mac shortcut to search the menu bar (cmd+shift+/) and then type "Spel..."
Though if the Mantiz Venus starts arriving before my order is shipped, I may need to switch.
Ps: If anyone else is interested in doing an e-GPU with their mac, https://egpu.io/setup-guide-external-graphics-card-mac/ is a great place to start.
Community.
Yes, there will be a CoffeeScript community that lingers on, but as things are looking now it won't be near as vibrant as it once was. Not only are there (seemingly) less people using CoffeeScript, but major related projects—such as CoffeeScriptRedux—are closing up shop (see this comment: https://github.com/michaelficarra/CoffeeScriptRedux/issues/3... ).
On the other hand, ES6 (and transpilers like Babel and Tracuer) are very popular right now. Some of that is hype & fad, but a lot of it is legitimate. In particular, I think that changes like the new module syntax are going to dramatically change Javascript development (even if we all transpile, speaking a unified module language is a huge improvement).
So, while I think it is totally reasonable to continue using CoffeeScript (and part of me really wants to!), it is hard to ignore/shun the community and momentum being ES6. For a while I was optimistically thinking that someone would eventually release CoffeeScript 2 (or even better, CoffeeScript6) that intentionally broke backwards compatibility to merge with ES6 semantics (classes, modules, etc). But now I'm thinking that is less and less likely (IMHO, CoffeeScriptRedux seemed like the best chance for that to happen).
I don't know if I'm ready to completely give up hope yet, but I think the article misses the point, community—and the (potential?) lack thereof—is one of, if not the most important thing to consider regarding your choice of language.
The point is that we'd rather gather feedback and hear from the community before we assume that everything we've done internally is exactly what other people and companies need. And sure, it would be awesome if we had a super polished version ready for anyone to use, but we kind of want to gauge interest before plowing ahead on v2 in isolation.
ps: About the forks, I'd love to get them merged upstream, but I have the feeling that they diverge more than the owners would like. But yes, we need to have that conversation (and suggestions are welcome, I'm pretty new to the ruby community).
If you are willing to accept some excuses (one can hope?), our dev blog is running the yet-to-be-released version of HubSpot's new blogging tool and is very much a work in progress. Also, the pages served by that blog (and our CMS) are not related to the tool this post is talking about.
But nonetheless, we need to make it faster. Thanks for the feedback.
1) Add all of the menu commands to the list of commands that show up when you press cmd-shift-p. It is very weird that some of the named commands (like convert to spaces) are available via cmd-shift-p, but others (like switch to 1 column view) are not.
2) I prefer the way textmate does multiple selection, where you can press a single key to toggle between regular selection mode and block selection mode.
Using cmd-shift-up/down in sublime text is very unpredictable. It works fine in the case you have several consecutive lines with no extra newlines in-between, but that is about it.
Though cmd-d to multi-select the next same word is pretty awesome.
3) Easier navigation between tabs in differnt split columns. I never remember the keys to switch between columns and I feel the existing normal tab management keys could do the job with a couple of tweaks.
For example, cmd-t is awesome, but I wish it was smart enough to automatically switch to an existing tab instead of opening a new tab with the same file in it.
Also, make cmd-shift-{ and cmd-shift-} move across all tabs and not just the tabs inside the currently selected column.
4) And lastly, the find in project results desperately need syntax coloring. It is so hard to scan a giant blob of plain white text.
Ackmate style file types would be nice too, but that isn't to big of a deal.
Again, awesome stuff. I can't wait to try out the vim bindings and I hope he keeps up the good work!
But I'm glad to see more options available. I've been advocating web-based chat in my offices for quite a while now, and am happy that a few decent choices have finally started to pop up in the past couple years.
Also, I'd recommend eclipse users (that are vim fans) to try out viplugin (http://www.viplugin.com/viplugin/). It is far from supporting all of vim's commands, but it has enough for me to feel comfortable.