Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight
 
PerlMonks  

Komodo seems unpopular here

by Scarborough (Hermit)
on Mar 08, 2005 at 13:51 UTC ( #437549=perlmeditation: print w/replies, xml ) Need Help??

I have followed with interest the voteing on which debug methods we monks favour, and I have been surprised to see how unpopular or little used Komodo is. I find it a great tool for ediring and debugging, but now suspect there might be somthing better out there.
I'd be interested to find out what other monks use to construct and edit there code and why?

Replies are listed 'Best First'.
Re: Komodo seems unpopular here
by hardburn (Abbot) on Mar 08, 2005 at 14:08 UTC

    A commercial license costs $245. For that much, I could upgrade my system to some shiny new PCI-X hardware. Use whatever you like, but to me, it's just not worth it.

    "There is no shame in being self-taught, only in not trying to learn in the first place." -- Atrus, Myst: The Book of D'ni.

      I think you may have it here. I am lucky enough to have it paid for at work. At home I use good old Textpad for editing and my code peppered with prints but I might try Tie::Watch in the future.
      student liscence is $24
Re: Komodo seems unpopular here
by merlyn (Sage) on Mar 08, 2005 at 15:10 UTC
      Never write more than five lines of code without running the program.
      I'm going to blame this one on a massive head cold, but I just made a large set of local changes to a framework I work on without running the test suite. Now I'm off to bang my head against my desk for a couple of hours, after which my brain should be ready to start eyeballing diff files to see where the stupid mistakes leaked in.

      -- Douglas Hunter
Re: Komodo seems unpopular here
by neniro (Priest) on Mar 08, 2005 at 14:07 UTC
    vim is my favorite editor at the moment. I have line numbering, the darkblue-colorscheme and some small helpers for editing html or xml-documents in my .vimrc.
    set nu! colo darkblue inoremap ,,, <esc>diwi<<esc>pa><cr></<esc>pa><esc>kA inoremap ___ <esc>diwi<<esc>pa /><esc>h
    vim is not an ide comparable to VisualStudio or Eclipse, but I like it small and simple.
Re: Komodo seems unpopular here
by Anonymous Monk on Mar 08, 2005 at 15:25 UTC
    I use the same debugging and developing tools I use with Perl as I use with shell, awk, C, C++, Java, Python, SQL, HTML, Pascal, Ruby, FORTRAN, and whatever else I've coded in, as well: vi (or a vi-clone like vim, nvi, elvis) and print or assert statements. That method has worked for me for the past 25 years, everywhere. Be it Solaris, SunOS, AIX, SCO, HP-UX, BSD, Linux, Cygwin, and some (Unix) platforms I can't remember - basically, any platform I've used since 1980. Any platform I bother to sit down at has vi. Even when installed freshly out of the box.

    I don't see a reason to switch away from a solution that's cross-platform, cross-language, works everywhere (well, everywhere in my world), is free (as in beer, often also in speech), has worked for the past 25 years (well, longer, but that was before my time), and will most likely work for at least till my retirement, and probably continue to work long after that as well.

    But if Komodo works for you, go for it.

      While I don't have nearly the breadth of experience as the Anonymonk, this is also my preferred solution. It Just Works and usually isn't difficult at all.
      I have not been a user as long (of Perl or, to be honest, computers :), but I have also placed most of my development into the hands of vi.

      I mostly like the convenience of (on my Linux computer at least, the one I have for DOS is just because I have the tendency to want to use UNIX commands when I switch over) being able to write my code, then suspend vi, test the code (at the risk of sounding like a newcomer for something so simple) with warnings and strict to catch problems, then I can just bring unsuspend vi to make corrections.
      Your a man how knows what he likes. Good on you!!!
Re: Komodo seems unpopular here
by maa (Pilgrim) on Mar 08, 2005 at 14:01 UTC

    I actually use Komodo for editing but I still rely mainly on print for debugging purposes.

    Combining print with extracting each "complex" bit of code/subroutine into a separate small script for testing has always worked well for me - I also found debugging slow and clunky in komodo.

    --
    Mark

Re: Komodo seems unpopular here
by bilfurd (Hermit) on Mar 09, 2005 at 04:14 UTC
    When coding on Windows systems I either use Crimson. It fits the way I think about projects and code. A few of the other proggers in my shop have started using it, too.

    For those with the need, Programmers Notepad offers similar functionality (for the same price -- $0) as well as hex editing.

    When on my Linux boxen, I use Kate. Long story short, I did not know what a decent text editor was until I started using Linux (I used to create websites using Windows Notepad...). I started playing around with Kate's functionality and immediately started looking for comparable Windows editors. If you use Kate, Crimson should feel natural.

    The trick is finding the tools that work best for you. I tend to use IDE's (MS Studio .NET for C#, or even Macromedia's Ultradev for HTML) for creating the UI, then polishing off the code using Crimson/Kate. My partner uses Studio from start to finish. As long as the we're developing code that works on schedule, we're both right.

    If Komodo is working for you, then all is groovy.

Re: Komodo seems unpopular here
by leriksen (Curate) on Mar 08, 2005 at 23:22 UTC
    xemacs and run the code with 'mode-compile'. The one true way on the one true editor. (emacs doesnt have this function, which is the only reason I chose xemacs over emacs)

    I dont use print, I use Log::Log4perl - that way my trace code builds up during development, but cost me next to nothing in production (as long as you use it as advised in the L::L4p doco).
    If I have a problem in production, I bump the log level up and watch the trace code scoll by, no restart required. Once I have enough trace output captured, I bump the log level down and watch the script become quiescent again.

    Debugging => perl -d:ptkdb script.pl .... - almost all the power of the Komodo IDE (that said, the Komodo debugger UI has a few features I believe are well worth paying for...)

    ...it is better to be approximately right than precisely wrong. - Warren Buffet

      emacs doesnt have {mode compile}, which is the only reason I chose xemacs over emacs
      Funny, my GNU Emacs version 22.0.50 (compiled nightly from the CVS HEAD for my OSX Carbon environment) seems to have M-x compilation-mode. Is that what you're referencing?

      -- Randal L. Schwartz, Perl hacker
      Be sure to read my standard disclaimer if this is a reply.

        That's probably exactly the same as xemacs M-x mode-compile

        code forks are such joy...

        update 17:36 9 March 2005

        Its seems to be slightly different - in xemacs, mode-compile does whatever seems appropriate for the buffer - for C code it tries to make, for a shell script it tries to run it in a shell, for perl it runs the perl code - it tries really hard to 'do the right thing' for whatever the major mode of the buffer happens to be.

        compilation-mode in emacs seems to change the major mode of the buffer, and M-x compile then does whatever you decide (for perl its probably no more than 'perl script.pl')

        I'm not an (x)emacs guru, so I suppose nearly everything I just said can be contradicted, but, that said, I like the semi-smart addaptive behaviour of mode-compile.

        ...it is better to be approximately right than precisely wrong. - Warren Buffet

Re: Komodo seems unpopular here
by pingo (Hermit) on Mar 08, 2005 at 15:53 UTC
    I use Emacs, simply because it is installed on most servers and I like X forwarding. :-)

    Other than that, Eclipse with EPIC seems really nice.
Re: Komodo seems unpopular here
by FitTrend (Pilgrim) on Mar 08, 2005 at 16:10 UTC

    I primarily write code on Windows. Therefore I use a package called Textpad. I've been using it for several years.

    I like it because it allows multiple documents opened at the same time, allows me to execute and create macros, and I've set it up to compile my perl files into EXEs with some of its built in functionality. Plus it has syntax highlighting (a must to find those rogue brackets and quotes).

      > I primarily write code on Windows.
      > Therefore I use a package called Textpad. 
      
      The only thing I don't get about that is the "therefore". When I used to code on Windows, I used GNU-Emacs for Windows.
Re: Komodo seems unpopular here
by Jaap (Curate) on Mar 09, 2005 at 10:38 UTC
    I use Komodo when on Windows (30% of the time). The only thing i'd like the kind folks at ActiveState to add is the Eclipse way of auto-completion. That would make it even cooler.
Re: Komodo seems unpopular here
by CountZero (Bishop) on Mar 08, 2005 at 22:44 UTC
    I use Komodo!

    CountZero

    "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: perlmeditation [id://437549]
Approved by Corion
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others lurking in the Monastery: (8)
As of 2021-04-22 15:14 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?