"For the most part, there's nothing here that couldn't be done with BBEdit or even with Emacs or vi. jEdit packages the capabilities much more nicely and makes it easy to call often-used functionality using the plug-ins. Where I saw NetBeans as overkill, others may see jEdit as underkill for an IDE or overkill for a text editor. I find it Mac friendly and easy to use."
@dimsumthinking , writing about the jEdit editor on MacDevCenter, April 16th, 2002
https://web.archive.org/web/20071210070613/http://oreilly.com/pub/a/mac/2002/04/16/osx_java.html?page=2
=> More informations about this toot | More toots from akosma@mastodon.online
@dimsumthinking quotation found by pure chance on Wikipedia :)
https://en.wikipedia.org/wiki/JEdit
=> More informations about this toot | More toots from akosma@mastodon.online
@akosma haha. jEdit is how I started doing serious development.
Imagine how surprised I was to see its author two decades later as a Swift core contributor.
https://factorcode.org/slava/
=> More informations about this toot | More toots from pilif@mastodon.social
@pilif wow, I knew the author's name sounded familiar!
Never clicked with jEdit I must say, I liked EditPlus too much at the time :)
=> More informations about this toot | More toots from akosma@mastodon.online
@akosma I was already going back and forth between Linux and Windows at the time and I was way too much of an open source hard-liner to ever consider a non-free windows-only editor.
I still prefer open solutions, but I'm willing to compromise (stares at PhpStorm and Visual Studio Code)
=> More informations about this toot | More toots from pilif@mastodon.social This content has been proxied by September (3851b).Proxy Information
text/gemini