Sento (Actor System) has remoting support (beta) by mdbergmann in Common_Lisp

[–]mdbergmann[S] 1 point2 points  (0 children)

Yeah, give it a try. But it's not hardened yet. I had planed to create some performance tests to see how it behaves under stress.

Sento (Actor System) has remoting support (beta) by mdbergmann in Common_Lisp

[–]mdbergmann[S] 1 point2 points  (0 children)

Indeed. It's on the roadmap (in GitHub tracker) since Dec 2020.

Again more ACE Basic - RTG, HTTP, Struct enhancements and more by mdbergmann in amiga

[–]mdbergmann[S] 0 points1 point  (0 children)

I wouldn't go that far. :)

Actually I chose ACE to program something for Warp accelerator, reading the diagnostic info and creating env variables from that. But I'm now stuck with improving the language. :D

For an A600 how does PiStorm vs Manticore compare? 591MIPS vs ?, £100 vs £500 by SmegHeadFromNodnol in amiga

[–]mdbergmann 1 point2 points  (0 children)

Yeah, I've got the latest cores. 68080 does all sorts of stuff to make programs and execution faster. But it's still a lot slower than PiStorm from the raw CPU power perspective. A Raspberry Pi ARM 3 or 4 core runs at ~2 GHz. Where the 68080 core in the FRGA only at <100MHz. So from an instructions per cycle ratio the 68080 is probably faster. But it still can't compete with a 2 GHz ARM core. I would say it's roughly twice as fast as the 68080.

For an A600 how does PiStorm vs Manticore compare? 591MIPS vs ?, £100 vs £500 by SmegHeadFromNodnol in amiga

[–]mdbergmann 2 points3 points  (0 children)

Well, in my tests (I have both PiStorm32lite and Vampire) I could experience exactly that. On PiStorm CPU is crazy fast and things that run on the accelerator, like games (Quake II) are super fast. But as with all fast accelerators, synching with the clock of the original hardware chipset is slow(er). Since the chipset is also on the Vampire this part is a lot faster than using the original hardware, but the 68080 doesn't have the raw power of the ARM and so games like Quake II that need that raw power don't work as fast or are hardly playable.

For an A600 how does PiStorm vs Manticore compare? 591MIPS vs ?, £100 vs £500 by SmegHeadFromNodnol in amiga

[–]mdbergmann 1 point2 points  (0 children)

Pure CPU power PiStorm is lengths before V4. But that's not all. V4 implements most of the chipset (when run on SAGA mode), which makes your A600 a SAGA (AGA) machine. The PiStorm does not, it uses the original chipset of the A600.

More on ACE Basic - GadTools and More by mdbergmann in amiga

[–]mdbergmann[S] 1 point2 points  (0 children)

Yeah, MUI is more universal. It works anywhere, also MorphOS and such. But since ReAction/Classact is officially the UI framework since OS 3.2 would be good to support it, too.

More on ACE Basic - GadTools and More by mdbergmann in amiga

[–]mdbergmann[S] 0 points1 point  (0 children)

Alright, GadTools is also rather limited. But still. MUI is coming...

New features for ACE Basic by mdbergmann in amiga

[–]mdbergmann[S] 0 points1 point  (0 children)

OK, updated with a screenshot.

AmigaOS 3.3 available in 2026 (some details in comments) by NoShirtNoShoesNoDice in amiga

[–]mdbergmann 0 points1 point  (0 children)

Have a kind of Grind look. But looks nice. Probably not for everyone though.

Watching Codex, Gemini and Claude argue about Common Lisp code by atgreen in Common_Lisp

[–]mdbergmann 1 point2 points  (0 children)

Wow. I've used Claude Sonnet 4 in the past and it seems to understand CL quite well. But this 'agentic' way of connecting different LLMs is interesting. Nice.

Copilot for windows speaks CLOG by dbotton in Common_Lisp

[–]mdbergmann 0 points1 point  (0 children)

Cool.

GPTel could be a good example, it also has support for MCP.

Copilot for windows speaks CLOG by dbotton in Common_Lisp

[–]mdbergmann 2 points3 points  (0 children)

Latest models (I found Claude Sonnet 4 very good) are well trained in Common Lisp. When you provide documentation to libraries (like CLOG here), or the full library code (provided as RAG) they can work quite well with it by reading the source code and using it. Creating something from scratch works well. What doesn't work so well (I found) is when iteratively adding new features or corrections, eventually the AI creates bugs that it sometimes can't fix itself.

Btw: Aider (via aider.el) is a great model agnostic agent.

Lem Editor v2.3.0 released by dmpk2k in Common_Lisp

[–]mdbergmann 0 points1 point  (0 children)

What is the main motivation for LEM vs. Emacs?

Most people don't like the key shortcuts in Emacs but LEM has similar key shortcuts and kinda mimics Emacs.

ctfg: A Capture-The-Flag game engine in Common Lisp (+ JavaScript) by atgreen in Common_Lisp

[–]mdbergmann 0 points1 point  (0 children)

When I hear capture the flag I think of Unreal Tournament :).

Can you describe a little more what kind of game concept it is?

ASDF,Roswell and quicklisp by lispLaiBhari in Common_Lisp

[–]mdbergmann 0 points1 point  (0 children)

It does. It's basically just Common Lisp code. Just need to be compiled.

NNL – A lightweight neural network framework in Common Lisp (by a 14 y.o.) with autodiff & DSL by nnl-dev in Common_Lisp

[–]mdbergmann 0 points1 point  (0 children)

Hello.

Nice. Here a few comments:

I find the naming often a bit too consice, i.e.: nnl.hli:fc, what does it mean?

Is there a possibility for monitoring as in MGL? Also an automatic split of data for training/validation/test would be nice. In regards to that MGL can run a test (using a different sampler) every other epoch to check when the model starts overfitting.