Skip to main content

IDE: NetBeans after Six Months

I've been using NetBeans for six months. I thought I'd whip out a quick post to tell you how it's gone. My earlier post is here.

I found a bunch more things I like. I finally figured out how to open files quickly. In the Projects window on the top left, click on the name of the project. Now, typing one letter at a time, you can get autocomplete. It took me a little while to figure out how it works, but now I can open files more quickly than I can visually parse things.

I also figured out that if I maximize the editor, and I shrink the size of the whole window, I can get the editor to fit in smaller places without taking up the whole desktop. That's helpful when I'm copying code I'm reading from a PDF to NetBeans even though I only have a 13" MacBook screen. (I like to manually copy code samples when I'm reading a book in PDF form because it helps me to learn the code better. I'm stuck with a tiny screen because I do a lot of my work at Starbucks.)

I still love jVi. It's not perfect, but it's pretty good.

I love the way NetBeans automatically fills in closing ", ], }, end, etc. for Ruby. This really speeds me up.

I don't like the fact that jVi can't wrap my comments and docstrings using gq} as well as Vim can.

I like having NetBeans launch my Ruby web server. It's one less window I don't need to worry about.

However, I still prefer to execute most things like rake tasks and ruby script/generate in the shell.

The coding hints aren't perfect. They're sometimes wrong, but that's not the end of the world. They're still a net positive.

I love using the find window when doing grep hunts. Since the window is open, it's easy for me to go down the list carefully making changes where necessary.

I'm happy with the plugin system. I didn't need to read any documentation, yet I've installed plugins for PHP, Ruby on Rails, jVi, etc.

In general, NetBeans is way easier to get up to speed with than Eclipse, which is the thing I like most about it.


Anonymous said…
you can use netbeans for python too.
Anonymous said…
> I finally figured out how to open files quickly

I am sure you will be faster with ALT+SHIFT+O
Anonymous said…
forgot a good link
jjinux said…
> you can use netbeans for python too.

Exactly, and I do.

> I am sure you will be faster with ALT+SHIFT+O

Hmm, that doesn't do anything on my Mac :-/


Cool. There's also a reference card that you can open in the help menu. That's how I finally figured out how to use Cntl-Tab and Cntl-Shift-Tab to switch between tabs. However, I wish it supported Cmd-Shift-{ and Cmd-Shift-} like a lot of other Apple apps.
Anonymous said…
Ah, okay your are on mac.

If this does not help:

or this:

you can try to go to Tools->Option->Keymap->go to file

and change the shortcut.

To switch between documents I favour CTRL+PageUp or CTRL+PageDown (I don't know for mac :-()
jjinux said…
Ah, Cntl-Shift-o, that's awesome! It matches ":e **/filename.txt" in Vim. I only mention Cmd-Shift-{ and Cmd-Shift-} because it works in, Firefox, MacVim, and Aquamacs.
jjinux said…

Wow, that's totally awesome, and totally overwhelming. I wonder how many of those work since I'm already using jVi.
jjinux said…
Note to self:

Don't install NetBeans from Ubuntu's packages. It's just not that great. Instead:

apt-get install sun-java6-bin sun-java6-jdk
update-alternatives --config java

Download NetBeans directly from the website and install that.

See also:

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p