Re: Looks like time to integrate AI into the IDE, to stay relevant to future users

[Fabien Bodard <gambas.fr@xxxxxxxxx>]

I’m already using it more and more to review my code or to help me grasp
certain concepts. AI is also more diligent than I am when it comes to code
comments and documentation. With these latest advancements, one might even
wonder what role is left for the programmer. I’d say "conceptual architect"
would be a fitting description now...

Among these recent breakthroughs, AI can even perform reverse engineering
on almost anything—we’re seeing the emergence of embryonic clones of
Photoshop, Illustrator, Word, or Excel. From a societal perspective, it’s
unsettling, as it threatens to upend the balance of our society. When I
think about all the work that went into the Gambas project—and the sheer
fun it provided—the realization that something similar could soon be
created in a couple of minutes, rather than over the course of 30 years...
it’s disheartening, yet fascinating at the same time.

Back when we were young, we dreamed of this kind of progress—though we
never anticipated such an explosive emergence.

Gambas remains a fantastic "retro/modern" tool; Benoît could potentially
leverage AI to add those few missing pieces.

Unlike a year ago, my current perspective leans toward enabling users to
utilize the tools of their own era—though with a degree of caution.
Interfaces for LLMs are constantly evolving, whereas Gambas is built for
the long haul. I’m becoming increasingly interested in local LLMs... though
I’d need to upgrade my hardware to run them :/.

Best Regards,
Fabien

Le ven. 16 oct. 2026 à 14:10, martin <tercoide@xxxxxxxxxxx> a écrit :

> I agree 100% with this POV
>
> El 16/10/26 a las 7:31, André Loewen escribió:
> >
> > Never, ever mix a clearly designed and stable development (and
> > production) tool like Gambas with constantly changing AI approaches
> > and models.
> >
> > My experience:
> > Finding a bug in AI-generated code takes definitely longer than
> > writing the code yourself from scratch.
> > The opposite approach is much more efficient: handle the development
> > yourself, and use AI as a tool for troubleshooting and bug resolving.
> >
> > Or, use AI as a  'patient colleague' for drafting brief snippets,
> > brainstorming approaches, or doing (reverse) documentation, but keep
> > yourself firmly in the driver's seat for the architecture and core code.
> >
> > Best regards
> >
> > André
>
>
>

-- 
Fabien Bodard