Re: Merlin

I'm not sure I 100% agree with that because it disregards the probability (given IBM's development lead times) that IBM was moving towards Merlin with its VS Code associations long before Code for I became a thing.

Code for I overcomes the one huge barrier that RDi has always faced - the cost. Not just the cost but the confusing packaging options, the time lag for enhancements in part caused by being stuck on an ancient version of Eclipse, etc.


Jon Paris
Jon.Paris@xxxxxxxxxxxxxx

On Mar 27, 2025, at 7:36 AM, Rob Berendt <robertowenberendt@xxxxxxxxx> wrote:

I agree with John Yeung.

On Wed, Mar 26, 2025 at 10:25 PM John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

On Wed, Mar 26, 2025 at 4:52 PM Justin Taylor <jtaylor.0ab@xxxxxxxxx>
wrote:

I know of no explicit statement. That's just my reading of the tea
leaves. They're favoring code4i. It's like a plant, what you feed

grows.

I am not so sure it's "favoring" Code for i; rather it's more like
"jumping on the bandwagon". VS Code has become the most popular IDE
for any programming language, for any platform. This would have
happened regardless of whether IBM worked for or against that outcome.
The Code for i extension was developed independently by Liam, and it
was only after it gained traction organically that IBM saw the writing
on the wall and decided to hire him.

IBM isn't feeding VS Code so much as it's hanging on for dear life as
VS Code charges ahead, with or without IBM.

John Y.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.