On Sun, 5 Jan 2025, Michael Fuchs via lazarus wrote:
Am 04.01.25 um 16:02 schrieb Michael Van Canneyt via lazarus:
I've added an AI assistant (AIssist) to the Lazarus codebase.
Check out components/aissist.
But why?
2 reasons:
- Because it was requested by a user.
- Lazarus is perceived as a tool from the 90-ies (last century).
Showing that one can integrate an AI can help to counter that perception.
There was also no pressing reason to create the "IDE scout" plugin, but it
was made with the same goal: show that Lazarus is not "outdated" and can do
the same things a 'modern' (whatever that is) IDE can do.
Both are plugins, no need to use it if you don't want/like/trust it.
All this is meant to provide a start for a CoPilot-kind of functionality,
as well as a possibility to generate e.g. fpdoc documentation for code.
Great, we have a pile of rubbish generated and then we have documentation.
THAT will help.
Personally, I would not let the AI generate code - every serious question I
asked
till now generated rubbish answers on all AIs I tried online,
but for generating textual descriptions (aka "docs") of existing code,
it does a reasonable job.
I'm very critical of AI as a code generating tool:
we're hopefully all aware that currently an AI cannot "reason".
Therefore I consider AI a serious misnomer.
But as a replacement/enhancement of google search or a documentation tool it
can make sense.
You might even try to use it to generate icons. I am horrible at creating icons,
and so I did some experiments, what came out was better than what I came up
with...
Like most tools, you must use it correctly. I can hammer in a nail with a
screwdriver, but that doesn't mean it is a good idea. Same with "AI"...
Michael.
--
_______________________________________________
lazarus mailing list
[email protected]
https://lists.lazarus-ide.org/listinfo/lazarus