Live data from Hacker News

There are many things you can say about Emacs...

pyside.blogspot.com

31–36 of 36 posts

Re: There are many things you can say about Emacs...

#31
post #7
post #3

I 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?

I used Eclipse nearly every business day for about 18 months.

Search didn't fully work; accordingly, search and replace didn't fully work.

Workspaces would randomly get corrupted, and code would "build" that really shouldn't build (i.e., code with syntax errors would claim to have built). Sometimes deleting every object and make file cleaned things up, but sometimes it didn't, and I would just have to make an entirely new workspace. (Possibly a bug in our makefile system rather than Eclipse proper.)

Buttons along the lines of "Check here if you never want to see this again" didn't actually work.

Depending on the workspace, I would have to log myself into Subversion over and over and over; generally multiple times for commit/update/whatever. (Possibly a bug in Subclipse rather than Eclipse proper.)

An older version of Eclipse (3.1.1, if I recall correctly) got so corrupted on my machine that I could literally launch if, then just sit there for a minute or two, and Eclipse would die. I wouldn't even have to use it; it'd just die.

In short, I have not had pleasurable experiences with Eclipse. I strongly suspect that my experiences were not the norm, since Eclipse is so popular, but whatever the cause of this badness -- the fault of Eclipse proper or not -- I prefer going back to Emacs. :-)

Honestly, if I hadn't had such weird experiences with Eclipse, I probably would like it. It seems to be a very nice system (or at least it ought to be, when it works right). You can even set it up with Emacs keybindings, which help ease the transition somewhat.

Re: There are many things you can say about Emacs...

#32
anyone here used scite, i've tried so many editors on windows and i've found scite to be the best of them all

it's starts up quickly, i've added it to the windows shortcut context menu, and scite have this option that allow you to open all new file in the same instance on new tabs

it have really good folding, and it have a simple and nice perl integration by default!

i don't know much about scripting scite, i know it uses lua, but i am sure if it gets more popular, one will find nice languages mode for it

on windows scite is king!

Re: There are many things you can say about Emacs...

#34
post #20

Earlier quoted context omitted.

Long post ahead. It's not really that hard...maybe Emacs isn't for you, but I was in your place just six months ago, when I started my CS studies and heard that Emacs could make your life easier. I am still a newbie, but I have started loving the editor. Here's how to learn. You need a good cheat sheet, printed and preferably taped to your monitor. You don't need the most arcane keymappings, but you'll need document…

Well, thanks it's sort of nice to get all those advice. Just... I'm not exactly a newbie. Like mentioned above I already have worked a decade with VS (and started programming more than 20 years ago). And I'm used to those keybindings very much by now and not only have no problem with them, but I actually do like them. Really. Not the least because nearly identical bindings work in nearly every single modern applicati…

I have used Emacs every day since 1991, have never run Windows or Mac and hardly ever use Windows or Mac, and even I agree with you about the keybinding. You should refuse to learn a new set of keybindings because the set you already know is the set that well over 90% of the world and 90% of the world's desktop applications use. (I have not used this CUA mode of Emacs that other commenters mention.)

Re: There are many things you can say about Emacs...

#35
post #31
post #7

Earlier quoted context omitted.

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?

I used Eclipse nearly every business day for about 18 months. Search didn't fully work; accordingly, search and replace didn't fully work. Workspaces would randomly get corrupted, and code would "build" that really shouldn't build (i.e., code with syntax errors would claim to have built). Sometimes deleting every object and make file cleaned things up, but sometimes it didn't, and I would just have to make an entirel…

I've never had any of the issues you describe.

Re: There are many things you can say about Emacs...

#36
post #10
post #7

Earlier quoted context omitted.

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…

My God. I never noticed that, but you're absolutely right. I'm a vi guy myself, but all the other, more _visually_ oriented developers in the office don't read code from top to bottom. They scan the methods in the structure tab on eclipse. I always wondered why their eyes would constantly drift off the editor...
Post reply on HN