I wonder how much did Eclipse contribute to the bad reputation of Java...

@buherator
Eclipse, very non-native UIs that only kinda work, 90's OOP, and in my case - a Python tutorial I read as a kid that claimed Python is superior because it starts up slightly faster...

@tmr232 Yeah I get the latter reasons, but I just updated Eclipse (because I had to upgrade GhidraDev because it somehow couldn't be upgraded in the earlier version...) and having seen things like VSCode or IDEA I feel like walking into a torture chamber. And I practically grew up with Eclipse!

Edit: also important to note that I mostly think of e.g. Swing as an early attempt that didn't end up that good, while I think the IDE could you know, make some sense?

@buherator Yeah, Eclipse had literally decades to improve by now...

As for Ghidra development - why not use IDEA? It's been a few years since I did any of that, but I remember it working just fine for Ghidra plugins & scripts.

@tmr232 I'm in that rabbit hole now, but it's seems surprisingly hard to get the optimal combination of versions for each tool: I already worked around a bug in buildGhidraJar, downgraded Gradle, and now trying to make intellij-ghidra to work with the latest IDEA, but I feel that now it's time to read a book...

Generally, it seems that unofficial tooling just can't go in lockstep with Ghidra releases while I try to be on bleeding edge.

But I agree with you that IDEA will be the way forward, I probably just have to wait and/or debug a bit until the stir caused by 11.2 settles.

@buherator Truth be told, I'm in awe of the mess that is the Ghidra build scripts.
I mean, I don't blame them. Most projects of that age would be as messy. But still, it's a pain.

I kinda wanna get the Kotlin Jupyter kernel working in Ghidra again, but I know it will be hell. So... Yeah, no.

@tmr232 Same with the docs: sometimes it's like finding a forgotten library room behind a brick wall. Actually fascinating!