Setting up Eclipse for CIQ Development....

jim_m_58 said:

CIQ for Eclipse hasn't been maintained for years

If that's what you meant, that's what you should've said, especially when the topic is "Setting up Eclipse for CIQ Development". In the context of this thread, Eclipse clearly means the Eclipse IDE, and not the Connect IQ Eclipse plugin.

Same as if I say "VS Code", I mean the VS Code editor, and not the VS Code CIQ extension.

It also makes little sense in the context of your original statement: "eclipse has not been maintained for years, and Garmin hasn't supported it for almost as long"

Let's replace "eclipse" with "CIQ for Eclipse":

"CIQ for Eclipse has not been maintained for years, and Garmin hasn't supported it for almost as long"

Taken at face value, this statement would imply that it was possible for Garmin to support CIQ for Eclipse without maintaining it, and that they did so for a short period of time? What would that kind of "support" look like? Usually "support" and "maintenance" are used synonymously, in the context of software.

The fact that you mentioned Eclipse not being maintained first, then mentioned Garmin support afterwards kind of suggests that Garmin support for Eclipse is separate from Eclipse maintenance in that sentence, which also suggests you meant the Eclipse IDE and not the CIQ plugin.

You could just admit you were wrong.

jim_m_58 said:

I still think VSC sucks. I only use it for CIQ.   I have more trouble with it than anything else on my system.  But it's the only game in town for ciq.  

You could edit your code in Eclipse and build from VS Code, the command line, and/or your own custom scripts. We've had posters who use linux and edit Monkey C code using vim. I know, you're going to say that the command line is a relic of the 70s. That may be true, but it's enjoyed a renaissance since the 2010s, and it isn't going anywhere (for devs.) The worst IT person I've worked with did everything exclusively in the UI and had no idea how to use scripts. Certain tasks which should've taken 30 minutes (with zero supervision) ended up taking 2 days (with constant babysitting.)

I think you'd be very hard pressed to convince anyone who was starting development today (having zero exposure to any IDE or text editor) that Eclipse is better than VS Code. But that's just my opinion. And in most professional circles, Eclipse is seen as a joke, and nobody uses it unless they have to.

But at least you're consistent in your opinions. I almost thought you might've changed your mind over the years.

I actually once thought Eclipse was ok (years ago when I used it for work), even though I had to wrestle with various problems on the daily (I often switched to other editors just to do certain simple tasks which were too slow in Eclipse.) Now I'll use anything besides Eclipse (VS Code, Intellij, Visual Studio, Sublime Text, notepad++, nano or vim.)