Live data from Hacker News

RayforceDB – a pure C analytics database with a Lisp-like syntax

rayforcedb.com

11–20 of 21 posts

Re: RayforceDB – a pure C analytics database with a Lisp-like syntax

#11
afaiu this is a kdb-adjacent columnar runtime and query engine

think SIMD, morsels and so on ~ Clickhouse, DuckDB …

but more like a lisp-like vector language and execution engine at its core + allowing for numeric and analytics adjacent use-cases instead of the other way round

Re: RayforceDB – a pure C analytics database with a Lisp-like syntax

#12

It's a little weird to truncate the history [0] of your open source project and lock the v1 commits in a separate repo with limited access [1]. Are the authors embarrassed of the commit history? [0] https://github.com/RayforceDB/rayforce/pull/166 [1] https://github.com/RayforceDB/rayforce2/blob/master/README.m...

I just did this recently to reduce the noise I got for using 'superpower's skill for an internal library. Personally trying to find the right git ops balance of observability/transparancy of agent work while keeping human readablity. I haven't seen any accepted standards or workflows, its really interesting to watch dev culture evolve with this

Re: RayforceDB – a pure C analytics database with a Lisp-like syntax

#13
post #3

At this point, I see an AI generated site I quit. this might be good stuff, but I'm not even interested anymore!

How can you tell it's AI generated?

Just like you can recognize Hemingway's prose voice from a few sentences. After dozens-to-hundreds of hours with Claude, you can tell.

Re: RayforceDB – a pure C analytics database with a Lisp-like syntax

#14
post #3

At this point, I see an AI generated site I quit. this might be good stuff, but I'm not even interested anymore!

How can you tell it's AI generated?

You start with a hunch and then dive into their github repo to confirm that Claude is a top contributor. At least, that's my strategy. Honestly though, I don't care about the website being AI generated. That's not what's important for a project like this.

Re: RayforceDB – a pure C analytics database with a Lisp-like syntax

#15

The claim of "built for teams that measure latency in microseconds" is conflicted by the pseudo demo showing a simple query that takes 4 seconds. I could assume that this is slowed down for effect, but the glowing green label[1] tells me this is a "real engine run" so now I'm confused. My core question is why would I use this instead of duckdb and writing SQL as God intended[2]? --- [1] A clear indication of AI gener…

FWIW I liked your joke :D

Re: RayforceDB – a pure C analytics database with a Lisp-like syntax

#16

The claim of "built for teams that measure latency in microseconds" is conflicted by the pseudo demo showing a simple query that takes 4 seconds. I could assume that this is slowed down for effect, but the glowing green label[1] tells me this is a "real engine run" so now I'm confused. My core question is why would I use this instead of duckdb and writing SQL as God intended[2]? --- [1] A clear indication of AI gener…

[2] duckdb indexes suck

Re: RayforceDB – a pure C analytics database with a Lisp-like syntax

#17

The claim of "built for teams that measure latency in microseconds" is conflicted by the pseudo demo showing a simple query that takes 4 seconds. I could assume that this is slowed down for effect, but the glowing green label[1] tells me this is a "real engine run" so now I'm confused. My core question is why would I use this instead of duckdb and writing SQL as God intended[2]? --- [1] A clear indication of AI gener…

FWIW I liked your joke :D

I think God did intend SQL for us. There is no going back. It's too deeply intertwined.

Re: RayforceDB – a pure C analytics database with a Lisp-like syntax

#18

The claim of "built for teams that measure latency in microseconds" is conflicted by the pseudo demo showing a simple query that takes 4 seconds. I could assume that this is slowed down for effect, but the glowing green label[1] tells me this is a "real engine run" so now I'm confused. My core question is why would I use this instead of duckdb and writing SQL as God intended[2]? --- [1] A clear indication of AI gener…

[2] duckdb indexes suck

Remember duckdb is for OLAP, not OLTP!

Re: RayforceDB – a pure C analytics database with a Lisp-like syntax

#19

Earlier quoted context omitted.

[2] duckdb indexes suck

Remember duckdb is for OLAP, not OLTP!

olap doesn't mean no indexes. Prev gen olap (cubes, star schemas) were index heavy, you can't achieve subsecond analytics without indexes.
Post reply on HN