There are many things you can say about Emacs...
pyside.blogspot.com
There are many things you can say about Emacs...
1–10 of 36 posts
Re: There are many things you can say about Emacs...
#2I have always been surprised why TextMate rather than Emacs has got all of the mindshare in Rails developer community.
'emacs-rails' mode had the same rails-specific navigation, snippet-expansion etc. features two years ago and has improved greatly since then. (See screencast: http://emacsonrails.drozdov.net for example)
I've tried to follow the crowd initially and to learn TextMate, but then... why learning new set of keystrokes? And why reimplementing a fraction of editing modes that emacs has available? When you can have... So I went back, but I am still puzzled by majority of Rails programmers choosing to support TextMate. Matz uses emacs after all...
Re: There are many things you can say about Emacs...
#3I think the first picture is pretty ugly, it looks too much like eclipse.
Re: There are many things you can say about Emacs...
#4Well, as he asks for my excuse, why I still not use it ...
I did grow up in the MS World where your fingers are trained to use and . And certainly all the other keybindings which you learn when programming with VS for a decade. I tried switching a few times, but having to press 3 keys at once is probably the main reason which keeps me still away from emacs.
Does anyone know of some emacs scripts which put all the keybindings from VS into emacs? Including stuff like blockselection with alt+mouse? Serious, I'm mostly working on Unix these days, but I still miss the VS editor :-(
Re: There are many things you can say about Emacs...
#5I have always been surprised why TextMate rather than Emacs has got all of the mindshare in Rails developer community. 'emacs-rails' mode had the same rails-specific navigation, snippet-expansion etc. features two years ago and has improved greatly since then. (See screencast: http://emacsonrails.drozdov.net for example) I've tried to follow the crowd initially and to learn TextMate, but then... why learning new set…
I think TextMate's Rails mode came before emacs-rails and inspired it. That's probably part of the reason. Another part is that TextMate behaves much more like a Mac app, and Rails was started by Mac users. So it's partly history, partly momentum.
I also tried TextMate, and do still use it for some things (I like the personal text wiki extension, which I hacked a bit to use MediaWiki syntax), but found myself programming back in Emacs in short order. TextMate's extension mechanism is incredibly obtuse compared to elisp (the Lisp-intolerant claim this is a strength, but just try making sense of how to customize a non-trivial TextMate mode and see how far you get). Running external scripts just to do basic things seems pretty inefficient to me. Also, its UI needs lots and lots of work. The inability to simultaneously look at two buffers in one project is a deal killer for me. I'm sure it'll improve in the next version.
Back on topic: native Unicode in Emacs 23 sounds great. So now, after only a few months of running the released version of 22, I guess I'll be back to running Emacs out of CVS. :)
Re: There are many things you can say about Emacs...
#6I have always been surprised why TextMate rather than Emacs has got all of the mindshare in Rails developer community. 'emacs-rails' mode had the same rails-specific navigation, snippet-expansion etc. features two years ago and has improved greatly since then. (See screencast: http://emacsonrails.drozdov.net for example) I've tried to follow the crowd initially and to learn TextMate, but then... why learning new set…
"I am still puzzled by majority of Rails programmers choosing to support TextMate. " -- mainly b/c most of them are noobs. (seriously). A huge amount of Rails dev. are young, and just started programming, and to them emacs is just arcane old stuff, while textmate is much more accessible, and I actually agree with that.
Just trying to download emacs is a pain, hidden in between ugly pages, while look textmate's webpage is much more shiny, and accessible. Plus people nowdays hate to have to jump thru config loops, and learn arcane old keyboard shortcuts just to get started.
So, darwinian process is going on, and the new, simple, and nimble, is replacing the old and arcane.
Re: There are many things you can say about Emacs...
#7I think the first picture is pretty ugly, it looks too much like eclipse.
and what's wrong with eclipse? It does it's job well. It is an IDE not just a editor, and so far has been pretty popular for good reasons. I know it is trendy to bash java, but really what's wrong with eclipse?
Re: There are many things you can say about Emacs...
#8I have always been surprised why TextMate rather than Emacs has got all of the mindshare in Rails developer community. 'emacs-rails' mode had the same rails-specific navigation, snippet-expansion etc. features two years ago and has improved greatly since then. (See screencast: http://emacsonrails.drozdov.net for example) I've tried to follow the crowd initially and to learn TextMate, but then... why learning new set…
"I am still puzzled by majority of Rails programmers choosing to support TextMate. " -- mainly b/c most of them are noobs. (seriously). A huge amount of Rails dev. are young, and just started programming, and to them emacs is just arcane old stuff, while textmate is much more accessible, and I actually agree with that. Just trying to download emacs is a pain, hidden in between ugly pages, while look textmate's webpag…
DHH used TextMate in the famous "build a blog in 5 minutes" video that was many people's first introduction to Rails. I'm guessing it was also many people's first introduction to an editor that had real power.
Re: There are many things you can say about Emacs...
#9I think the first picture is pretty ugly, it looks too much like eclipse.
and what's wrong with eclipse? It does it's job well. It is an IDE not just a editor, and so far has been pretty popular for good reasons. I know it is trendy to bash java, but really what's wrong with eclipse?
It's not Emacs. If that isn't enough, it's also not Vim.
Re: There are many things you can say about Emacs...
#10I think the first picture is pretty ugly, it looks too much like eclipse.
and what's wrong with eclipse? It does it's job well. It is an IDE not just a editor, and so far has been pretty popular for good reasons. I know it is trendy to bash java, but really what's wrong with eclipse?
For many folks, myself included, the spirit of emacs is to avoid the mouse. That particular screen looks like it was designed to be used with a mouse.
I agree that eclipse is a useful tool, but I don't think it has much in common with emacs. It feels strange saying this about editors, but they embody completely different notions of how programming is done.
For example, when I pull up a file in emacs, I intend to read the code. Eclipse users tend to load the file and then examine the structure tab, looking directly at the method definitions. I've seen eclipse users ignore my comments because of this structure pane (and not reading the code file top to bottom). These editors definitely put us on different wave lengths :)