Ciro Santilli @cirosantilli 34

Once upon a time (early 2010's), Eclipse dominated the IDE landscape and all was good. NetBeans was around too. And Java was still unmarred by Google LLC v. Oracle America, Inc..

But then something happened.

For some reason, Eclipse started to decay.

And the project that had once been a vibrant community of awesomeness, started to become... a zombie of its former self.

Buggyness started increasing. And not even hard to fix bugs. One liners that affect every user immediately after startup.

Sometimes, to Eclipse's defense they weren't "bugs". Just features that it became evident with time every programmer expected from a modern IDE.

But somehow the Eclipse community had a deep problem. A cancer. It had completely lost touch with user experience.

Perhaps is was due to the increasing interest of the several corporations that had adopted Eclipse as the base IDE for the proprietary solutions?

Perhaps.

Many users stuck to the IDE.

Some heroic efforts were made as plugins that drastically improved certain defects. The Darkest Dark plugin comes to mind.

But all those efforts required configuration. A setup time that most users simply don't have. The core devteam had become dumb and dead, unable to incorporate such changes.

This greatly opened up the space for other competing IDEs to come along. The "semi feature complete but at least easy to use and not so buggy" Visual Studio Code and the proprietary JetBrains IDEs being some of the most notable ones.

Using Eclipse as of the early 2020's is such a mixed experience. If you spend enough time to configure out the key buggyness, there are moments where you can feel "OMG, this feature is amazing".

But the effort is just too great, and soon another bug or obvious missing feature hits you and brings you back to reality.

Every young person uses VS Code now. Eclipse is dead, and there is no way back, usage will just continue dropping.

RIP, Eclipse. It wasn't meant to be.

Bibliography:

github.com/foambubble/foam impressive.

Open source Roam Research clone.

Markdown based, Visual Studio Code based.

Template project: github.com/foambubble/foam-template.

Publishing possible but not mandatory focus, main focus is self notes. Publishing guide at: foambubble.github.io/foam/user/recipes/recipes.html#publish Related: jackiexiao.github.io/foam/reference/publishing-pages/.

They seem to use graphs more than trees which will complicate publication.

TODO are IDs might be correctly implemented and independent from source file location? Are there any examples? github.com/foambubble/foam/issues/512

A CLI tool at: github.com/foambubble/foam-cli

Ciro Santilli's joke version of the Chinese Four Treasures of the Study!In the past, Ciro used to use file managers, which would be the fourth tresure. But he stopped doing so for years due to his cd alias... so it became three. He actually had exactly three windows open when he was checking if there was anything else he could not open hand of.