Why would a front-end developer on OS X use any editor besides BBEdit?
1–10 of 13 posts
Re: Why would a front-end developer on OS X use any editor besides BBEdit?
#2If you try to do actual programming, instead of grepping and replacing, SublimeText (and Atom, though slower) are much more featured. From build systems integration, to "go to function" and myriads of plugins for linting, AST based auto-complete, etc etc.
Re: Why would a front-end developer on OS X use any editor besides BBEdit?
#3Re: Why would a front-end developer on OS X use any editor besides BBEdit?
#4Sooooo many reasons. Here are a few: * http://orgmode.org/ * http://www.gnus.org/ * http://www.emacswiki.org/emacs/JabberEl
Re: Why would a front-end developer on OS X use any editor besides BBEdit?
#5Because "grep and multi-file search/replace" is not exactly what a front-end developer does. If you try to do actual programming, instead of grepping and replacing, SublimeText (and Atom, though slower) are much more featured. From build systems integration, to "go to function" and myriads of plugins for linting, AST based auto-complete, etc etc.
however i guess for other, more complex situations, having more add-on options and such might be beneficial.
Re: Why would a front-end developer on OS X use any editor besides BBEdit?
#6"Thou shall not start an editor war, for they are without end, lacking all rigour and decorum."
Re: Why would a front-end developer on OS X use any editor besides BBEdit?
#7Re: Why would a front-end developer on OS X use any editor besides BBEdit?
#8Sooooo many reasons. Here are a few: * http://orgmode.org/ * http://www.gnus.org/ * http://www.emacswiki.org/emacs/JabberEl
those don't convince me, though maybe i'm not reading far enough in to see their significant use point. bbedit does what i need and does it well. i write css/html/javascript for dev work, and it works fine for keeping notes or whatever like that first link mentions.
Basically, the idea is that your editor becomes your entire world. News, email, chat, source control, code, running code ... everything merges into the one system, and efficiency gains in one area tend to be applicable to others.
All your keyboard accelerators, macros, etc. etc. are available to all functions. Want to kill to the end of the line? It's C-k ... in everything. In your editor, in your email client, in your scheduler ...
Re: Why would a front-end developer on OS X use any editor besides BBEdit?
#9Because front end is so much more than vanilla html css etc. You have Sass, handlebars, svg and more to deal with. If you only use the basics, maybe a simpler solution works for you. But calling the others into question just because they don't work for you is pedantic.
Re: Why would a front-end developer on OS X use any editor besides BBEdit?
#10Earlier quoted context omitted.
those don't convince me, though maybe i'm not reading far enough in to see their significant use point. bbedit does what i need and does it well. i write css/html/javascript for dev work, and it works fine for keeping notes or whatever like that first link mentions.
I have the nasty feeling I'm being trolled, but ... try watching these to get a feel of what a proper programmable editor is capable of: * https://vimeo.com/13158054 * https://vimeo.com/30721952 Basically, the idea is that your editor becomes your entire world. News, email, chat, source control, code, running code ... everything merges into the one system, and efficiency gains in one area tend to be applicable to oth…
personally i prefer not having to learn new keyboard shortcuts to style a todo list for example as that first video discusses. i just write it out, use an asterisk or some easy system to show points, outline levels or whatever. if it's important to get done that day i note that in plain text. this is faster and easier to remember than learning a whole system for todo lists and marking up the different items importance, etc.
i want my email client to be focused on email, and a scheduling or calendar program to be focused just on that. for me bbedit is a swiss army knife of text editors in that it does lots of things to text - grep, search over huge numbers of directories, whatever. but i don't want one environment for things beyond that. for me those do many things badly, instead of one thing well.