Looks like Emas used to rule the roost but then died away. What really piques my interest is why those of us in Wyoming (and the Dakota’s and Alaska) and apparently love Vim:
https://trends.google.com/trends/explore?q=%22textmate%22,%2...
I'd even go to an extent and say vim trends show supply of intermediate level programmers. Emacs trends show supply of expert programmers. The fact that those trends are in a downward direction tells a story in itself.
https://trends.google.com/trends/explore?date=all&geo=US&q=%...
I don't search 'vscode [something]' nearly as much. Most of the configuration options are explained in the interface (both the visual one and `settings.json`). I can find plugins right from the editor and that usually also includes essential information about working with the plugin.
I still use barebones vim for commit messages, and I still find myself looking for how to trigger the spelling suggestions. I never seem to recall the `z=` when I need it.
Just because something is less user-friendly and requires more knowledge or looking for help, it doesn't mean it's more popular.
The Stack Overflow developer survey is probably a more representative sample: https://insights.stackoverflow.com/survey/2019#technology-_-....
See for example: https://trends.google.com/trends/explore?date=all&geo=US&q=%...
Sure, much of the API and all the plugin stuff is in Python, but the core is all native C++ AFAIK.
Having said that, if they had known all the modern alternatives were going to be even less “native” amd run in a browser engine, they'd probably have been less nitpicky.
It may not be heavy on archaic Mac features such as AppleScript integration, but I hope we can all agree to ignore those technologies.
TextMate just brings memories of the 10.4 Tiger days.
I personally liked ST2 but I know that some people held their nose.
Also, I'm not convinced we should ignore those "archaic" technologies, at least in the abstract. Applications can provide "dictionaries" of commands that, when implemented well, provide GUI applications with the kind of "snap together for amazing effect" you get with shell scripts and a host of well-written CLI tools. You arguably can't script the AppleScript-intensive BBEdit to the same level that you could, say, Emacs or Vim, but imagine the possibilities of a suite of apps from different makers that all had complete scripting dictionaries that could all be woven together with a deep system-wide scripting language.
I actually think it's a shame that AppleScript has been kicked to the curb. I don't think we have a "modern" replacement yet -- certainly not in the Apple ecosystem, and I'm not sure anywhere else. (Shortcuts on iOS is trying, but it's not on the Mac yet, and it gets pretty clunky if you start doing overly complicated automation bits with it.)
Unfortunately, the language itself is a horrible abomination from the wild 1990s days of Mac OS... sorry, now macOS... and writing absolutely anything in it is painful.
I feel like Apple introduced Automator to overcome the pain of AppleScript, but it never really caught on (I don't even know if Automator is still on macOS.... yep it is, still with the cute Aquaesque icon)
Nowadays everything is Electron anyway and those are not that well AppleScript-able, but what to do, that's life
In fact, there are several production-tested Apple event bridges that totally wipe the floor with Apple’s failed attempts, but caveat emptor as I don’t do support:
http://appscript.sourceforge.net https://www.npmjs.com/package/nodeautomation https://hhas.bitbucket.io/welcome.html
We’ll see what happens when Shortcuts lands in 10.16, but I’d say the chances of Apple event automation having a long and healthy life ahead are 50/50, at best.
I think the main developer of AppleScript left Apple last year.
I think I read something on these lines on HN, I may be remembering things slightly wrong
iOS Workflow/Shortcuts is what Automator should have been in a lot of ways. If Automator was superseded by a macOS version of Shortcuts, I'd actually love it, as long as it didn't lose any of Automator's functionality. (All they'd really need to do is add Shortcuts that run AppleScripts and shell scripts, I think, and be able to use automator actions exposed by applications.)
https://twitter.com/stroughtonsmith/status/11359563313603461...
Compare the file browsers and find dialogs and the difference is night and day.
The only fight it can't win over VSCode is the extensions and ecosystem.
Maybe you don't care about any of these but don't tell me you don't really lose anything.
If I wasn’t writing so much Python, I’d say I have a type.
Panic seems prepared to take that bet, with their development of Nova [1], a replacement for Coda.
(Wait, maybe I'm misreading your comment. Are you trying to say "Sublime is free, so Nova will have to be way better to compete with Sublime" or "Sublime wasn't good enough to justify its price, so Nova will have to be way better than that to justify its price"?)
People invest a lot of time into their existing text editors. For many people (myself included) a potential replacement would have to be more than a little better, because otherwise it's not worth the somewhat large cost (in terms of time spent on setup+mastery) of switching.
They just have too many products than what they can focus on...
That one feature makes such a difference to me as I switch between big project trees that I can't do without it.
I'd happily pay Panic for Nova if they add that back in.
(Ironically, as I get more deeply into Vim, I've found the :find and :buffer commands to be faster and just as useful as the CtrlP plugin, even if they're not quite as forgivingly fuzzy.)
Coda is more like VS Code and Sublime Text in some ways, but it definitely has Dreamweaver's "one stop shop for big web sites" thing going. (BBEdit also has that to a large degree, despite being even more of a pure HTML/text editor.) The biggest liability Coda has is that it feels designed for a time when we were primarily building sites out of hand-coded HTML; like BBEdit, it really isn't optimized for working on MVC-based apps, whether server-side or front-end.
It is native, cross platform, and not based on Electron. It also uses Vim as the core editing engine.
It isn’t native in this context; As a sibling comment mentioned, OniVim2 uses revery[0], which uses it’s own widgets (not native ones) like flutter[1].
Quoting from my old comment[2]:
> We really should be trying to use the native GUI toolkit (or cross-platform native UI libraries like libui), not using Flutter-esque libraries that draws everything from scratch.
> Coherent UI is a very important point to users IMO. Users can assume that some special feature from App X will also work on App Y.
[0] https://github.com/revery-ui/revery
[1] https://github.com/revery-ui/revery/blob/master/README.md#de...
Personally, I'm not looking to increase the ways that I'm locked into my current operating system, so all else equal, I'd favor an editor that runs everywhere.
(and also FWIW, of all text editors personally i use Notepad++ on Windows and Geany on Linux - though as i really dislike Gtk3 and Geany switched to that, i'm looking for some alternative that uses a more snappy and lightweight toolkit - for now the Debian version i use is still on Gtk2 but that is just a matter of time to be replaced)
Though i also believe that the functionality some people want from their applications is only available on (what i see as) applications with inferior UIs and they'd rather get used to these UIs than not have the functionality - that is, their vote is for the functionality, not for the UI.
Haven't noticed any performance problems with VS Code, since I started using it everyday maybe 3 years ago. I switched from Intellij based editors to VS Code and before that I used vim for a decade.
Especially on MACs were RAM is priced at a premium.
On Windows I developed a small program that sums the ram usage of my browsers and Electron apps I use. Between Firefox, Chromium and VSCode it's frequently around 4 GB of ram ! That's insane just to basically browse text.
Visual Studio, Sublime Text, TextMate, BBEdit, SlickEdit, Notepad++, XCode, Vim, Emacs, heck, one could add IntelliJ into the mix...
https://trends.google.com/trends/explore?date=all&geo=US&q=%...
I really built a habit of vanilla vim usage, and to this day I have yet to find a "modern" text editor that really supports everything that vim has to offer i.e. "vim mode" being more than binding the arrow keys to hjkl and providing modes.
https://trends.google.com/trends/explore?date=all&geo=US&q=%...
(and if you keep it to search terms but swap "visual studio code" for "vscode" you see a simialar rise)
Half-joking, but I think it is actually over-estimating the vim user base because there are so many things to search when learning to use vim, whereas the others are much closer to a traditional word processors.
Apart from that, Emacs usage mostly correlates how much of text heavy tasks a programmer is doing. Most people tend to write tons of shell/perl/python scripts and take a lot of time recreate the magic of emacs outside it, Sadly most of it is also throw away effort with a lots of manual effort in between. Sometimes its entirely manual effort because eventually you need to learn Perl regexes, or sed or awk really well, and that's another black hole in itself. To me that's kind of a gap in developer training itself. If you are wasting man-hours to weeks doing what should be done in man-minutes you probably have a huge gap in the way you are used to thinking about how your work in general.
Growth of Python is a big problem for programming community at large. It's a tool largely designed for beginners and people refuse to move beyond that. What's worse they also carry that kind of thinking to any tool they want to use.
Developers are generally bad at automating our own work. We wish to liberate accountants and ware house workers from drudgery. But rarely do we look at our own very work the very same way.
Using git with vim also seems a popular search combo.
Personally I am amazed that the younger generation are keen to learn vim. I don't see why as I have gone the other way to only use phpStorm for editing in earnest. For me using vim for code instead of phpStorm is a bit like handwriting instead of typing, a definite loss of formatting and neatness.
The reason I find modern interest in vim so amusing is that there is no compelling excuse to use it. In the olden days when you had to queue to use a terminal in a computer room to enter code you had handwritten on paper there were no 'nano' or other editors, you had to learn and use vi.
I don't believe vi is quicker than a full size IDE but I still use vi, find and grep because I don't fully trust these new IDE tools and I am fairly dyed in the wool as a command line user.
The tools I don't fully understand are the textmate, sublime, notepad++ and other middling editors that don't offer the brilliance of vim or the possibilities of a phpStorm grade editor.
Obviously its php specific features aren't relevant here since we're discussing editors (or development environments) in general.
Personally I find that most IDEs are far too language specific, and I can't possibly invest the time to learn an IDE per language when there's so many languages I regularly need to edit (and probably yet more in the future).
VSCode isn't half bad, as it has plugins for just about everything, but it's still a juggernaut in terms of software size. None of the jetbrains product I've used had decent plugins for all the languages I need.
And of course none of these work over a purely terminal ssh connection, which is a bit of a deal breaker for me.
Definitely not trying to convince you to use vim over your favourit IDE, I'm just currious what your top 10 missing features are.
https://trends.google.com/trends/explore?date=today%205-y&ge...
That's an interesting comparison. I completely agree that VSCode is the rage right now. Sublime was big 2014-2016. I'm surprised atom isn't as popular (I suspect its because of the awful loading time)
https://trends.google.com/trends/explore?date=all&geo=US&q=%...
Also "vs code" trends higher than "visual studio code", so take all of these results with a pinch of salt.
But apparently VS Code is becoming extremely popular. I wonder if its literally just because of GitLens (still missing from other text editors).
Disclaimer: RubyMine / IntelliJ for life.
I use Atom for my quickie projects here and there, but you really can't beat an IDE. (IMO)
CPU use is negligible and I have plenty of RAM.