webdsl

It doesn't (perhaps yet?) install the dependencies from the Makefile, but it runs a number of commands from the Makefile, eg, make test-leaks: https://github.com/williamcotton/webdsl/blob/main/.github/wo...

Maybe be, after all - I dont write web servers (btw, the PQ and JQ libraries doesnt seem to use the arena allocator, which makes the whole proposition a bit dubious, but lets say that its me being picky). What I meant was, that IMO the code is not very robust when dealing with memory allocations: 1. The "string builder" for example silently ignores allocation failures and just happily returns - https://github.com/williamcotton/webdsl/blob/92762fb724a9035... 2. In what seems most of the places, the code simply doesnt check for allocation failures, which leads to overruns (just couple of examples): https://github.com/williamcotton/webdsl/blob/92762fb724a9035... https://github.com/williamcotton/webdsl/blob/92762fb724a9035...

Some free code review of the first file I clicked into - https://github.com/williamcotton/webdsl/blob/92762fb724a9035... among other places should probably be doing the conditional "lexer->line++"; thing. Quite a weird decision to force all code paths to manually do that whenever a newline char is encountered. Could've at least made a "advance_maybe_newline(lexer);" or so. But I guess LLMs give you copy-paste garbage. Even the article of this thread says: > Just because code looks good and runs without errors doesn’t mean it’s actually doing the right thing.

What do you mean by "harder stuff"? What about an experimental DSL written in C with a recursive descent parser and a web server runtime that includes Lua, jq, a Postgres connection pool, mustache templates, request-based memory arena, database migrations and much more? 11,000+ lines of code with ~90% written by Claude in Cursor Composer. https://github.com/williamcotton/webdsl Frankly us "fanbois" are just a little sick and tired of being told that we must be terrible developers working on simple toys if we find any value from these tools!

This is 11,682 lines of C (and not including some Lua and Python scripts) according to cloc: https://github.com/williamcotton/webdsl It's a pipeline-based DSL for building web apps with SQL, Lua, jq and mustache templates. I'd say it's like 90% Cursor Composer in Agent mode. This is probably more like a mid-sized project, right?

I vibe coded this entire DSL, changing syntax and grammar while following my whimsy: https://github.com/williamcotton/webdsl

Since July of last year, in reverse chronological order: WebDSL, fast C-based pipeline-driven DSL for building web apps with SQL, Lua and jq: https://github.com/williamcotton/webdsl Search Input Query, a search input query parser and React component: https://github.com/williamcotton/search-input-query Guish, a bi-directional CLI/GUI for constructing and executing Unix pipelines: https://github.com/williamcotton/guish

But why follow the wrong abstraction and why try to build something that you don't fundamentally understand? I've built some rather complex systems: Guish, a bi-directional CLI/GUI for constructing and executing Unix pipelines: https://github.com/williamcotton/guish WebDSL, fast C-based pipeline-driven DSL for building web apps with SQL, Lua and jq: https://github.com/williamcotton/webdsl Search Input Query, a search input query parser and React component: https://github.com/williamcotton/search-input-query

Guish, a bi-directional CLI/GUI for constructing and executing Unix pipelines: https://github.com/williamcotton/guish WebDSL, fast C-based pipeline-driven DSL for building web apps with SQL, Lua and jq: https://github.com/williamcotton/webdsl Search Input Query, a search input query parser and React component: https://github.com/williamcotton/search-input-query

Do your snippets write this kind of boilerplate? https://github.com/williamcotton/webdsl/commit/34862739f6fe9... I may have tweaked a couple of things in that (and refactored a hell of a lot since) but here's a Python script that I definitely did not write a single line of code: https://github.com/williamcotton/webdsl/blob/main/tools/gene... Embedding things into C is nothing new of course but I spent about 45 seconds getting the solution I needed: https://github.com/williamcotton/webdsl/blob/main/src/server... All of this is just boilerplate. I spent most of my mental energies with this project on the grammar, the memory architecture, and fitting all of the pieces together. Cursor and Claude did most of the typing. Keep in mind I'm iterating over the grammar and making rather large changes in the runtime all the while: https://github.com

I took this approach with this: https://github.com/williamcotton/webdsl I didn’t even put that much effort into defining the grammar, I just sort of let my fancy take flight. Which is a wild headspace to be in when writing a DSL in C with a web runtime with jq, Lua, GitHub OAuth and more all built in into the language itself. It took some guidance of course and I’m well versed enough in C to have orchestrated the memory arenas and overall architecture but I sure has hell didn’t actually type more than 5% of the code. Cursor Composer in agent mode with Claude Sonnet 3.5 has let me take on some very experimental endeavors.

WebDSL is an experimental domain-specific language and server implementation for building web applications. The language runtime includes an integrated PostgreSQL client, Lua and jq interpreters, mustache renderer, GitHub OAuth and more. It provides a mainly declarative way to define websites with pages and API endpoints. It aims to reduce boilerplate by having a very opinionated set of features curated especially for database driven web applications. For example, user login, authentication and sessions are all built directly into the language runtime.

https://github.com/williamcotton/webdsl Made almost entirely with Cursor and Claude 3.5 Sonnet. 11k lines of C and counting.