121–130 of 150 posts
Now that's a landing page. It had just enough information on the first page, and easily led into the more detailed info in the sidebar navigation. If I was on a Mac and was remotely interested in trying a new editor, I might well have stuck my address in there. As it was, it still drew me in enough to poke around. Well done.
Anyone who thinks this is cool should check out Sublime Text 2. It has all these features and much more (json config files? oh yes). Also, it's cross-platform; learn once, use everywhere.
Do you often switch from linux to windows for your coding environment?
Why would I want another editor?
Anyone who thinks this is cool should check out Sublime Text 2. It has all these features and much more (json config files? oh yes). Also, it's cross-platform; learn once, use everywhere.
Do you often switch from linux to windows for your coding environment?
Now that's a landing page. It had just enough information on the first page, and easily led into the more detailed info in the sidebar navigation. If I was on a Mac and was remotely interested in trying a new editor, I might well have stuck my address in there. As it was, it still drew me in enough to poke around. Well done.
On the other hand the clear list of features made me realize it offers nothing I don't already have or want.
So if the features don't appeal to you, it's good in the long run for the creator to not have you as a beta user.
[1] the counter argument is that any publicity is good publicity :)
"Who doesn't like tabs?" In text editors? Me. I don't like thinking about which individual files are open. Any file under the root of my project (i.e. the editor's current working directory) is fair game for an open buffer. I treat open file as "go to class".
Honestly, that line betrays my own apathy towards the feature. I hardly ever use them. They probably should be dead.
However! There is currently a plan (with associated scary-looking diagrams) to change how tabs behave[1].
Essentially, you'd be able to use a tab for each logical grouping of open files.
For example, in a django project, you might create a tab for each separate app you're working on. Or maybe a tab for your views, and another for your templates.
I understand that, even with that change, tabs won't fit many people's workflow. So they will always remain out of the way, unless you actually create more than one.
[1]: https://github.com/fileability/chocolat-public/issues/159
With the amount of muscle memory and (deeply personalized) customization that goes in to getting comfortable with an editor, it seems like the hardest place to attract users, and since vim and emacs have already done everything worth doing in an editor (except flashy buttons I guess), it seems like the hardest place to innovate. textmate, bbedit, kod, coda, sublime text, and now this What is interesting about this sp…
I don't choose vim or emacs for the same reason I don't choose Linux. The appeal of OS X is that it's a pleasant place to spend time, full of well crafted GUIs specifically for it, while retaining a good amount of Unix power.
The number of good, actively developed text editors on the Mac is actually remarkably small.
There's TextMate 2, which has become a synonym for vapourware. Kod's future seems uncertain now that Rasmus got his job. Coda and Espresso are good in their niches (of web development) but they're not general purpose editors.
So we're just left with BBEdit and Sublime. I think there's room for one more :)
Anyone who thinks this is cool should check out Sublime Text 2. It has all these features and much more (json config files? oh yes). Also, it's cross-platform; learn once, use everywhere.
> json config files? oh yes I find JSON makes for awful config files. For the sole reason that they can't be commented.