Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Elo – A data expression language which compiles to JavaScript, Ruby, and SQL

elo-lang.org

Post reply on HN
Print view View original

1–10 of 36 posts

Re: Elo – A data expression language which compiles to JavaScript, Ruby, and SQL

#2

Post by jauntywundrkind »

I really like this idea! I wish I knew other data expression engines for js.

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.

Re: Elo – A data expression language which compiles to JavaScript, Ruby, and SQL

#4

Post by h1fra »

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.

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.

Re: Elo – A data expression language which compiles to JavaScript, Ruby, and SQL

#6

Post by swrobel »

h1fra wrote: post #4

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. 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.

Yeah, P30D as presumably intuitive to non-technical users has me chuckling

Also, knowing that TODAY > signup + P30D transpiles to TODAY > signup + 30.days in Ruby. Which one is more readable?

Re: Elo – A data expression language which compiles to JavaScript, Ruby, and SQL

#8

Post by egonschiele »

Maybe the most incredible part – did Claude write a recursive descent parser from scratch for this? https://github.com/enspirit/elo/blob/9f07fefcdf65c169089f123...

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.

[1] https://github.com/egonSchiele/tarsec [2] https://ohmjs.org [3] https://nearley.js.org

Re: Elo – A data expression language which compiles to JavaScript, Ruby, and SQL

#9

Post by gatapia2 »

egonschiele wrote: post #8

Maybe the most incredible part – did Claude write a recursive descent parser from scratch for this? https://github.com/enspirit/elo/blob/9f07fefcdf65c169089f123... 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. [1] https://github.com/egonSchiele/tarsec [2] https://ohmjs.org [3] https://nearley.js.org

That git commit is very impressive (for Claude)

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.

Re: Elo – A data expression language which compiles to JavaScript, Ruby, and SQL

#10

Post by ElectricalUnion »

swrobel wrote: post #6
h1fra wrote: post #4

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. 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.

Yeah, P30D as presumably intuitive to non-technical users has me chuckling Also, knowing that TODAY > signup + P30D transpiles to TODAY > signup + 30.days in Ruby. Which one is more readable?

Is this even valid ruby? Doesn't it need Rails-specific Active Support to work?
Post reply on HN