[sdiy] Best Web site AI code generation ?? CODEX ?
Roman Sowa
modular at go2.pl
Mon Jul 27 13:24:11 CEST 2026
In the era of everyone using AI for everything, I will continue to be
Sarah Connor.
Roman
W dniu 2026-07-27 o 09:57, francesco mulassano via Synth-diy pisze:
> Hi, senior developer here.
>
> I'm a full-stack web developer working mainly with the TALL stack
> (Tailwind, Laravel, Livewire, Alpine), FilamentPHP, and a bit of React.
>
> I'm also the lead developer of Cosmolab (https://cosmolab.faselunare.com
> <https://cosmolab.faselunare.com>), where I primarily work in C++
> developing embedded audio applications such as synthesizers, effects,
> MIDI tools, and Eurorack modules.
>
> At the moment I'm using Cursor in Auto mode (€20/month) plus usage-based
> tokens, which usually costs me somewhere between €100 and €300 per
> month. It works extremely well, but I'd like to try Qwen or Kimi to see
> if I can achieve similar results while reducing costs.
>
> I've also spent some time trying GitHub Copilot. I quickly burned
> through all of the free credits just trying to get it to understand one
> of my Laravel web projects, but I never managed to reach the same level
> of context awareness that Cursor provides. It simply couldn't build a
> solid understanding of the codebase.
>
> For Cosmolab, everything is extensively documented for both humans and
> AI. I have around ten well-structured C++ example projects that cover
> virtually every feature of the board. When these examples and the
> documentation are included in the workspace, Cursor understands my
> prompts very well and is able to generate fully functional synthesizers,
> effects, MIDI applications, and other embedded audio projects with very
> little guidance.
>
> I'm curious to know whether Qwen or Kimi can provide a similar level of
> understanding and code generation for this kind of workflow. Has anyone
> here successfully replaced Cursor with either of them for
> medium-to-large codebases?
>
>
>
>
>
>
> Il giorno lun 27 lug 2026 alle ore 01:27 Jean-Pierre Desrochers via
> Synth-diy <synth-diy at synth-diy.org <mailto:synth-diy at synth-diy.org>> ha
> scritto:
>
> In fact I’d ask the AI to do a ‘Wordpress’ web site structure of
> what I need..____
>
> Easier to debug or add things afterward..____
>
> Good idea ?____
>
> __ __
>
> On Sun, 26 Jul 2026 at 14:56, Jean-Pierre Desrochers via Synth-diy
> <synth-diy at synth-diy.org <mailto:synth-diy at synth-diy.org>> wrote:____
>
> Best Web site AI code generation ??
>
> I heard about CODEX ?
> Is-it ?
>
>
> ________________________________________________________
> This is the Synth-diy mailing list
> Submit email to: Synth-diy at synth-diy.org
> <mailto:Synth-diy at synth-diy.org>
> View archive at: https://synth-diy.org/pipermail/synth-diy/
> <https://synth-diy.org/pipermail/synth-diy/>
> Check your settings at:
> https://synth-diy.org/mailman/listinfo/synth-diy
> <https://synth-diy.org/mailman/listinfo/synth-diy>
> Selling or trading? Use marketplace at synth-diy.org
> <mailto:marketplace at synth-diy.org>____
>
> ________________________________________________________
> This is the Synth-diy mailing list
> Submit email to: Synth-diy at synth-diy.org
> <mailto:Synth-diy at synth-diy.org>
> View archive at: https://synth-diy.org/pipermail/synth-diy/
> <https://synth-diy.org/pipermail/synth-diy/>
> Check your settings at:
> https://synth-diy.org/mailman/listinfo/synth-diy
> <https://synth-diy.org/mailman/listinfo/synth-diy>
> Selling or trading? Use marketplace at synth-diy.org
> <mailto:marketplace at synth-diy.org>
>
>
> ________________________________________________________
> This is the Synth-diy mailing list
> Submit email to: Synth-diy at synth-diy.org
> View archive at: https://synth-diy.org/pipermail/synth-diy/
> Check your settings at: https://synth-diy.org/mailman/listinfo/synth-diy
> Selling or trading? Use marketplace at synth-diy.org
More information about the Synth-diy
mailing list