Slashdot Mirror


GNOME's Text Editor gedit 'No Longer Maintained', Needs New Developers (gnome.org)

AmiMoJo brings news about gedit, the default text editor for GNOME: In a post to the gedit mailing list, Sébastien Wilmet states that gedit is no longer maintained and asks "any developer interested to take over the maintenance of gedit?" Just in case you were considering it, he warns "BTW while the gedit core is written in C (with a bit of Objective-C for Mac OS X support), some plugins are written in Vala or Python. If you take over gedit maintenance, you'll need to deal with four programming languages (without counting the build system). The Python code is not compiled, so when doing refactorings in gedit core, good luck to port all the plugins (the Python code is also less "greppable" than C). At least with Vala there is a compiler, even if I would not recommend Vala."
Sébastien's comments were surrounded by a <rant-on-languages> tag, but they're still crying out for some serious discussion. Any Slashdot readers want to share their own insights on Python, some fond thoughts on gedit, or suggestions for maintaining a great piece of open source software?

8 of 239 comments (clear)

  1. Who uses it anyway? by TeknoHog · · Score: 5, Funny

    I don't gedit.

    --
    Escher was the first MC and Giger invented the HR department.
  2. Re:get rid of that crap by arglebargle_xiv · · Score: 5, Insightful

    If I took over this project I'd rip all that shit out and simply use Lua for everything. Developers are so stupid.

    And now you have five programming languages in gedit.

  3. Patience is a virtue by timlewis_atlanta · · Score: 5, Funny

    Just wait for systemd-geditd

  4. We all saw it coming... by Anonymous Coward · · Score: 5, Informative

    A Slashdot commenter predicted the demise of gedit almost three years ago. The core of this argument was the following:

    Hipsters are killing open source projects left and right with their fucking awful UI changes.

    Just look at what happened to gedit. It's a text editor that comes with GNOME.

    Gedit used to look like this: https://upload.wikimedia.org/wikipedia/commons/d/df/Gedit2261.png

    It had a clean, usable, consistent UI. The major functionality was easily available, and the UI was extremely intuitive and efficient to use.

    The hipsters can't stand for usable software, of course. It needed to be "improved"!

    This is what gedit looks like more recently: https://upload.wikimedia.org/wikipedia/commons/e/ef/Gedit_3.11.92.png

    I'm not joking. That's really what it looks like. Using it is even worse than it looks.

    Gedit's UI today is fucking awful.

    1. Re:We all saw it coming... by JustNiz · · Score: 5, Informative

      Totally agree, I absolutely hated that switch. It was so obviously bad that for the longest time I honestly thought it must be a bug or something.

      Anyway, I just use Pluma instead. Its basically a branch of Gedit that kept the old interface.

      https://en.wikipedia.org/wiki/...

  5. Re:Open Source problem by arglebargle_xiv · · Score: 5, Insightful

    Exactly. I can keep on using Microsoft Office Accounting, Encarta, MapPoint, Windows Movie Maker, Windows Messenger, Microsoft Expression Design, FrontPage, Picture It!, Microsoft Money, and many other professional grade tools secure in the knowledge that with a huge commercial software company behind them, they'll still be actively developed and supported for many years to come.

  6. Re:Pluma by Misagon · · Score: 5, Informative

    For me, "Pluma" is the real gedit anyway.
    One of the first things when I upgraded from GNOME 2.0 to Mate was to add an alias. Too bad that it uses GTK+ 3.0 now though, with the crap scrollbar and the annoying smooth scrolling that can't be turned off.

    Pluma is still actively maintained, as is the core of both forks: GtkSourceView.
    The rest of GNOME 3's "gedit" is specific to GNOME 3. Let it die!

    --
    "We mustn't be caught by surprise by our own advancing technology" -- Aldous Huxley
  7. It's not Microsoft or SCO who hurt Linux. by Anonymous Coward · · Score: 5, Insightful

    Long time Slashdot readers will know how it was always Microsoft, and then later on SCO, who were accused of causing harm to Linux distributions, and open source software in general.

    Yet it's now becoming more and more apparent that it's not outside influences that are most harmful to Linux and open source, but rather it's the open source projects that destroy themselves by making idiotic and unwanted changes, which in turn causes the best users to flee to alternatives.

    This gedit nonsense is just a small part of the GNOME project destroying itself through the disastrous GNOME 3 released. GNOME 3 is a complete regression compared to the GNOME 2 user experience, forcing its best users and developers to seek alternatives. It wasn't Microsoft that made this happen. It wasn't SCO that made this happen. It was the GNOME project itself!

    Firefox is another example. Years of unwanted changes forced on its users by the Firefox developers have caused these users to flee to Chrome and other browsers. Now Firefox has only about 5% of the browser market. That puts it well below Chrome, well below Safari, and well below UC Browser for Android. Even Opera Mini, at 3.26%, has about as many users as Firefox 54's 3.75%! Now Firefox has become an irrelevant, fourth- or fifth-tier browser that's ignored by users and web developers alike. It wasn't Microsoft that made this happen. It wasn't SCO that made this happen. It was the Firefox project itself!

    The Linux distros that have forced systemd on their users is another example. Debian was once known as a solid, robust, trustworthy Linux distro. But it has lost that reputation now that it has switched to systemd. Lots of users have reported problems with systemd, as seen by the bug reports and mailing list postings begging for help with problems affecting systemd. Many of these Linux users have had to switch to FreeBSD, macOS, or even Windows in order to get a reliable OS. It wasn't Microsoft that made this happen. It wasn't SCO that made this happen. It was these Linux distros themselves!

    The worst enemy of open source projects isn't Microsoft or SCO. The worst enemy of open source projects are their own leadership and developers!