dkdcio
Joined 1 year ago
Joined 1 year ago
side note, I’ve been trying to remember when it launched internally if anybody knows. I feel like it was pre-COVID, but that’s a long timeline from internal use to public preview
immediately to a fantasy slippery slope argument, cool!
your argument seems to boil down to paid ads being the lifeblood of the flow of information. my argument is it corrupts that flow of information, and we’d be better without them —- everything would operate just fine. individuals and organizations would have better incentives to share valuable information, not what they get paid to. obviously there would be plenty of details and edge cases to work out, as with any policy in the real world
I’m not going to write out policy in HackerNews comments and play that game with someone who jumps to the “imagine this crazy world where the police start arresting all of us over free speech!” as their explanation for what would go wrong
> people can pay to have their messages displayed where they will be seen
…why? distribution of information is free across the world, which was not the case a century ago. let the message speak for itself
I ask again, what’s your actual argument against? you’ve seen things through ads you’ve liked? you think people should be allowed to pay to put their thumbs on the scale of the distribution of information? to what end?
- you don’t need to use Python (but Pythonic wrappers like Ibis exist; disclaimer I worked on Ibis, you can find my blogs on performance comparisons easily there); CLI, WASM, etc. w/o Python
- governance: DuckDB as OSS is setup in a more sustainable way (DuckDB Labs + DuckDB Foundation). while there is a VC-backed company (MotherDuck), it doesn’t employ the primary developers/control the project in the same way the Polars company does
- overall just simplicity and focus. tends to break less, solely focused on single-node, easy to extend, etc. — not trying to do a cloud product, distributing computing, supporting GPU execution
still doesn’t really prove much
- agents tend to need (already have) a filesystem anyway to be useful (not technically required but generally true, they’re already running somewhere with a filesystem)
- LLMs have a ton of CLI/filesystem stuff in their training data, while MCP is still pretty new (FUSE is old and boring)
- MCP tends to bloat context (not necessarily true but generally true)
UNIX philosophy is really compelling (moreso than MCP being bad). if you can turn your context into files, agents likely “just work” for your use case