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?
I was just thinking yesterday that some of what these AI generated sites have exposed is just how vacuous and low information content a lot of websites have become. The difference is previously you could at least say, "hey, someone at least spent a little money to create this" now that cost is pretty much zero. I think the answer is to simply demand more from people who have real products. If you have a product, I want to see a screenshot. Even better a demo and I'm not hitting the "schedule a demo" button. Either you step up and demonstrate capability or you're going to get lost in the noise.
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]?
Let's add it to ClickBench: https://github.com/ClickHouse/ClickBench/
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 was just thinking yesterday that some of what these AI generated sites have exposed is just how vacuous and low information content a lot of websites have become. The difference is previously you could at least say, "hey, someone at least spent a little money to create this" now that cost is pretty much zero. I think the answer is to simply demand more from people who have real products. If you have a product, I want to see a screenshot. Even better a demo and I'm not hitting the "schedule a demo" button. Either you step up and demonstrate capability or you're going to get lost in the noise.
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 generation
[2] This is a joke.
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?
It has the look: fonts, style, layout, too many em-dashes, and weird phrasing like "Every surface reaches the same optimizer and execution core."
The honesty is what makes it good
A graph analytics database? Could you talk about the motivation, and competition?