Fully featured LSP (take a look at the GIFs in the repo), step debugger, BDD-testing framework built into the language and runtime itself (novel!), asynchronous/join in pipelines (novel!), middleware for postgres, jq, javascript, lua, graphql (with data loaders), etc. It does quite a bit. Take a look at my GitHub timeline for an idea of how long this took to build.
It is 100% an experiment in language and framework design. Why would I otherwise spend years of my life handcrafting something where I just want to see how my harebrained ideas play out when actualized?
I would absolutely love to talk about the language itself rather than how it was made but here we are.
And I wrote my own blog in my own DSL. Tell me that's not just good old fashioned fun.
I saw this DSL on HN yesterday, and this syntax is total garbage. It’s some stupid mixture of different PLs. Are you seriously OK with this so that you keep posting it here? I don’t even want to look through source code knowing what garbage it is at the surface level.
describe "hello, world"
it "calls the route"
let world = "world"
when calling GET /hello/{{world}}
then status is 200
and selector `p` text equals "hello, {{world}}"
What don't you like about it? I think it's interesting
> Why would I otherwise spend years of my life handcrafting something where I just want to see how my harebrained ideas play out when actualized?
If you're sure that's all you wanted out of it. If this were more a path-vs-destination kind of project for you, you might have gotten deep insights about programming language design and implementation over those years which the efficient route deprives you of.
I did miss the sarcasm you pointed out in the separate mail to me (I should have paid more attention to the word "otherwise", I guess). I did not mean to lecture at you at all. I thought it was something you built very quickly with LLMs, but clearly this was a passion project, whether or not you used LLMs.
It's OK, I was being overly sensitive based on the other comment in this thread. In fact, I do value the journey over the destination and it is helpful to be reminded of this. I've updated the project's README to make this explicit!
https://github.com/williamcotton/webpipe
https://github.com/williamcotton/webpipe-lsp
Fully featured LSP (take a look at the GIFs in the repo), step debugger, BDD-testing framework built into the language and runtime itself (novel!), asynchronous/join in pipelines (novel!), middleware for postgres, jq, javascript, lua, graphql (with data loaders), etc. It does quite a bit. Take a look at my GitHub timeline for an idea of how long this took to build.
It is 100% an experiment in language and framework design. Why would I otherwise spend years of my life handcrafting something where I just want to see how my harebrained ideas play out when actualized?
I would absolutely love to talk about the language itself rather than how it was made but here we are.
And I wrote my own blog in my own DSL. Tell me that's not just good old fashioned fun.