Love the idea, but I don't think this "built for [...] non-technical users" works. All the examples were more confusing to me vs a regular programming language and definitely not accessible to non-technical users.<p>Also, why would I want to compile to multiple languages? If I'm building a no-code platform, I won't bother supporting 3 different languages since I'm the only one seeing the code.
Maybe the most incredible part – did Claude write a recursive descent parser from scratch for this? <a href="https://github.com/enspirit/elo/blob/9f07fefcdf65c169089f123a2c0b684131b53dd7/src/parser.ts" rel="nofollow">https://github.com/enspirit/elo/blob/9f07fefcdf65c169089f123...</a><p>Not that it's super complex, but I'm surprised it didn't pick up an npm package. I wrote tarsec[1] and have been eyeing ohmjs[2]. And of course nearley is a classic.<p>[1] <a href="https://github.com/egonSchiele/tarsec" rel="nofollow">https://github.com/egonSchiele/tarsec</a>
[2] <a href="https://ohmjs.org" rel="nofollow">https://ohmjs.org</a>
[3] <a href="https://nearley.js.org" rel="nofollow">https://nearley.js.org</a>
Recursive descent parsers are basically mechanical structures, <i>if</i> you get the grammar right (which encapsulates all the logic).<p>When I was a CS student, they seemed like magic to me as well, but later I got to revisit them for a project at work, and finally managed to understand the logic.<p>Imo, the biggest complexity in using them comes from how they handle operator precedence, with recursive nested expressions in the grammar, which I still don't find intuitive at all.<p>If you decide to hand-roll your own parser/syntax today, I recommend you look at Pratt-parsers, they are much nicer to write by hand. Modern languages (Rust, Go) , ironically are much simpler to parse, since they defined the syntax in such a way that they can be parsed unambigously by looking 1-2 tokens ahead.<p>And since all of them follow the same logic, AI has a ton of sources to learn from.<p>I'm also working on my programming language, and AI assistants have been able to generate these parsers for well over a year.
That git commit is very impressive (for Claude)<p>Edit: Oh, I think the main dev is just using Claude to do the commits (I guess to summarise changes, etc). It does not mean that Claude wrote all that code.
FWIW, at the bottom of the landing page they credit Claude for “every line of code, tests, and docs”
Claude did, I swear<p>The parser was built gradually though, with logs of increments under automated tests.
SQL was also initially built for end users and not considered "code".<p>I'm not sure we should continue to stack supposedly simple languages one on top of the other for ever. Why not learn SQL instead?
Third example on the site does not in fact compile to SQL
I coincidentally worked on something similar but I kept closer to the SQL standard. It grew out of business cases where you don't have strongly typed data to act on.<p>I more or less adopted the syntax from dumbql (<a href="https://github.com/tomakado/dumbql" rel="nofollow">https://github.com/tomakado/dumbql</a>) and started off with a peg parser using ohm.js. As I started benchmarking I realized how slow it was and started looking for "fast paths" using regex. I ultimately resorted to a recursive descent parser similar to Elo. At that stage I already had a lot of tests and api in place, so I was able to get a lot of help from Claude.<p>Website here: <a href="https://filtron.dev" rel="nofollow">https://filtron.dev</a>
I really like this idea! I wish I knew other data expression engines for js.<p>I feel like adding filtering languages into our http endpoints is one of those forever bespoke tasks. This is probably not the right form for tackling that problem, since it is a fairly complex query language & processor and doesn't cleanly map to something we'd use in a URL query string. But it makes me miss odata a little bit. And it makes me wish there were more visible popular options for data expression languages.
This is very similar to what I'm building: <a href="https://lutra-lang.org" rel="nofollow">https://lutra-lang.org</a><p>The base premise is the same: SQL is not a proper programming language and everyone knows it only because they have to. And I feel like everyone who knows SQL enough admits that, but still none of the 20+ attempts of a better language stuck on.<p>As someone would say: sad.
The notion that this is for non-technical people is... wild. Curious to know who they've spoken to?!
Targeting Python, Ruby, and <i>SQL</i> seems impossible if you want certain features.
This looks amazing. We use Ruby, Javascript and SQL. I will try this out this week. Are you looking for contributors? What is your vision long term with this?
What would I use this for? Everything in the examples is pretty easy to do in scripting languages like Python, JS, and Ruby.
It would be pretty nice to write those simple things in one language if you have a ruby server, react front end, and postgres database. You could target different parts of the stack but think/implement in one language. Seems nice to me.
This looks perfect for people who desire terseness above all. The examples make my head hurt.
can't wait to never use this
Why would I teach this to someone instead of plain SQL?
The compilation example contains an error. You should ask Claude what it is, because clearly you didn't find it yourself.
[dead]
[flagged]