During my classes I always need to get into this explanation of why there is no really good open source IDE for Perl. I always go by explaining that most of the Perl developers either use some version of vi or emacs but every time there are students who insist on that they need an IDE.
Actually as I am thinking about this more, I don't really know if there is no good IDE for Perl as I personally don't feel I need anything more than what I am currently using: gvim + command UNIX line tools including ack and lots of unit tests.
Thinking it even more there are a few places where I could improve my own development environment. One of them is that I constantly need to look up things in tons of pod files and I think I am typing perldoc and the names of the module just too many times.
Anyway, that's my environment and the problem is with people who are either starting out on perl or have only a few years experience. They need much more hand holding from the tools.
When I am at clients, I see many developers insisting on using a real IDE. These are either people with only a few years experience or people who switched from languages where you live in your IDE such as Java or C++. They are also mostly people with Windows only background. Some of these people use Eclipse with Epic, others use Komodo yet other use some text editor with syntax highlighting but complain about the lack of debugger.
In the classes I always explain the advantage of vi/emacs and knowing the built-in debugger of Perl by the fact that in just too many cases we are required to work on remote Unix systems with nothing on them.
Of course if I have an IDE that can run on my desktop but edit files on a remote machine (via ftp or scp) and then can execute that code on the remote machine (via telnet or ssh) but show the debugging information on my IDE. That could be cool.
I see people using Komodo for remote editing at one of the clients and while I am sure there are advantages we suffer a lot as saving the files take time and we often switch to another console and start running the program before it is fully saved. This leads to all kinds of nasty error message that often confuse us.
Anyway, for people with hardly any experience in Perl having all the information in the IDE (e.g. what parameters a function can get) will often out weight the inconvenience of having to wait for the ftp to complete.
In addition there should be many more people using Perl on Windows. Part of the reason that there are not so many might be the fact that both the environment and even the Perl documentation expects some Unix experience.
So I decided I try to further investigate the issue, first by trying to find out what kind of editors and IDEs are out there and what am I missing - if anything - by using vi instead of some real IDE. In addition I'd like to know what others use for their Perl development? Finally to see what improvement do we need and how to reach that?
There are plenty of good free text editors for Windows, they do quite a good job in syntax highlighting, some of them can even be configured to launch your script from within the editor but none of them is and IDE.
After some search I found that there is an entry in the Perl FAQ that comes with your standard perl installation but one that you can also read here: IDE or Windows Perl Editor Unfortunately Notepad++, the editor I use sometimes on Windows isn't mentioned there.
Then I looked at PerlMonks and I found several nodes about the topic. Both new and old. Here are a few links. Following them will lead for the other nodes.
In addition there was an article on perl.com a few years ago with the title Perl Needs Better Tools
There is also a page on the Perl Foundation wiki describing some of the editors. I added some links there but that page still lack any substantial information.
So based on all the discussions I tried to list what do people need from their IDE?
Beginners (especially in classes) need these:
When writing applications (the first few years) people also need these:
And the more advanced stuff is here:
So what tools are out there?
Before finding all the above links I turned to Google. There were some interesting results most notably the big difference in numbers when one is searching for perl editor ( 2,940,000 hits ) or for perl ide ( 307,000 hits ).
So if I am already there I decided to run the same search for other languages:
Number of hits on Google for XYZ editor and XYZ IDE:
You do whatever you want with this data.
Anyway why am I writing all this?
I don't worry too much about people using Linux or Unix directly. There are Perl beginners there too but they are much more used to rough edges and using several tools at the same time.
What I am interested in is having a great and free version of Perl width loads of tools for the Windows developers. Strawberry Perl for Windows is quite promising but I think it would be great if it came with a built in editor. Especially when the Perl-on-a-stick project is done we'll be able to have a working perl installation on a disk-on-key so we can just plug it in a computer and start using our Perl scripts or give a demo. It would be great to have an editor there too.
So a month or so ago I thought I'll write one. I know it must be lots of work but it might be quite rewarding. I started to write in Gtk2-Perl and within a few days I had a working version. Then I found out that Nadim has also started to write on in Gtk2. I tried to play around with that one but then I talked with Adam Kennedy, the maintainer of Strawberry Perl. He suggested to include Kephra with Strawberry or Chocolate Perl. It was written in Wx-Perl.
While I like Gtk2 better than WxWidgets it is mostly because I had bad experience with WxWidgets. It was hard to install and I have not found any documentation for it. Nevertheless I have to admit that probably an application written in Wx-Perl will have better chances on Windows than one written in Gtk2-Perl as the former looks smoother on Windows.
I am still at odds whether I should invest any more energy in it, given that there are plenty of editors out there and given that it is not likely that I personally will need it. Anyway it can be a good way to learn Wx-Perl and I have a few ideas on how to make it more useful for windows developers.
Comments byClaudio Ramirez
See more comments on use.perl.org Published on 2008-05-22 by Gabor Szabo blog comments powered by Disqus