My new favorite breed of commenters are AI bros who go around lamenting how trivial other peoples' work is, while they themselves fail to create anything that anyone else actually wants to use

You could have vibecoded a better comment too. But you didn’t.

we should have also claude-alternatives like projects that are entirely built by vibe-coders.

Few people actually know how Eurodollar system works under the hood.

Cursor CEO got grilled in HN for a good reason.

does duckdb scale well over large datasets for vector search ?

What order of magnitude would you define as „large“ in this case?

like over 1tb.

Some people are using DuckDB for large datasets, https://duckdb.org/docs/stable/guides/performance/working_wi... , but you'd probably do some testing under the specific conditions of your rig to figure out if it is a good match or not.

its clear many DuckDB sql queries can handle terabytes of data, but the question here was about vector search..

I think it is called false positive :)

>>That's where languages like Rust and Go come in. They offer native performance,

I'm not sure Go can offer native performance.

“Native performance” in this context means compared to scripting languages, not low-level languages like C. Of course, Go offers native performance relative to JavaScript. Your comment seems to assume the author was comparing Go to more systems-level languages like Rust or C. In those cases, Go may lag behind, but it still qualifies as native performance.

> scripting languages

The "script" is compiled all the way down to machine code by the runtime, for heavily used paths. The black/white distinction of "scripted" vs. "compiled" does not exist, has not for many years.

Too many of these discussions and arguments seem to be stuck in the 1990s technology level. It is much more mixed and complex now.

It's still a useful distinction IMO.

"Script" PLs tend to be interpreted, dynamic, and handwave various machine-level details. In contrast, "compiled" PLs usually provide you the constructs to manipulate native machine-level features directly.

Realistically, communities around "script" languages aren't going to talk much about memory layout or syscall. Instead, getting the job done fast (devtime-wise) is their main focus.

On the other hand, "compiled" languages tend to draw people who like squeezing every bit of computing power from their computer, even though it tends to raise the complexity.

I think the author puts Rust and Go in the same basket, and it is something that I can't agree.

A fair notice. In terms of performance, Go is similar to Java. Sth between scripting and native.

looks like, he didn't pay enough for bribes

lol https://puzer.github.io/github_recommender/#p=eyJ0IjoicHJvZm...

>>possible thanks to the DOM (scraping, ad blockers etc.) harder or impossible.

lol, you can scrape anything visible on your screen.