Slashdot Mirror


Jedit, Jext & J: Java-based Editors Compared

An anonymous reader writes "There are times when I want a lean, mean editor and times when I enjoy a good, bloated editor packed with wizards. We compare the programming editors Jext and J to Jedit and offer a revised opinion of the best Java for Linux."

2 of 97 comments (clear)

  1. i am not compelled by amorico · · Score: 5, Insightful

    Summary:
    J: interesting and--Oh look! shiny php object!
    Jext: tricky installation, but nothing interesting in the five seconds I spent reviewing it.
    jEdit: reviewer liked this one the most, but was biased from the beginning.

    Whatever. Why waste the time to even write a review if you are not even going to take the time to go into depth? The reviewer complains about bloated IDEs like eclipse or netbeans and then does not even point out why ANY of the reviewed editors are a compelling choice over an IDE. Eclipse and Netbeans make enterprise deployment, unit testing, and building a lot easier because they were created with that in mind. They only implement editing functions to the extent that they support iterative development cycles and integration with software engineering tools. Do the editors support automatic code copmletion based on classpath and in-scope variables? If I wanted souped up text editor I would use emacs or vi, whiach are FAR better than this j* stuff. An editor is great when you are developing alone, but when you are part of a team of developers, things like CVS integration, code style enforcement, and automation of repetitive build tasks are essential. How do any of these editors fare in that respect? You'll never find out in this review.

    -a

    --
    "The plural of anecdote is not data." -- Roger Brinner
  2. Re:Text editors by KnightStalker · · Score: 3, Insightful

    Hm. You can draw pretty lines in UML all day long, but at some point the behavior that UML is representing has to get turned into ones and zeros that your processor can execute. Even if you have large libraries of predefined modules, you still will not have any sort of flexibility -- unless you whittle those libraries down to the level of source code.

    And I think I'd rather use a text editor to type "for(int i=0; i<10; i++) { ... }" than drag a "Loop" module into my diagram and fill out a dialog box.

    --
    * And remember, it's spelled N-e-t-s-c-a-p-e, but it's pronounced "Mozilla."