Comment by marcellus23
2 days ago
> Marketing note: I'm sure you're proud of P Core/V Core, but that doesn't matter to your users, it's an implementation detail. At a maximum I'd write "intelligent execution that scales from small files to large files".
Speaking personally, "intelligent execution that scales from small files to large files" sounds like marketing buzz that could mean absolutely nothing. I like that it mentions specifically switching between RAM and disk-powered engines, because that suggests it's not just marketing speak, but was actually engineered. Maybe P vs V Core is not the best way to market it, but I think it's worth mentioning that design.
I wish every product had an engineer-only landing page I could set as a default in my browser. The number of companies that assume I'm familiar with their offering is astounding, and I'm usually looking for implementation docs just to figure out what it actually does.
I'm not saying we need a morlock/eloi toggle.
Thanks for the thoughtful take—really appreciate both perspectives.
You're right that terms like "intelligent execution" can feel vague without concrete backing. My goal with mentioning P Core/V Core was to hint at the underlying design—switching between in-memory and disk-based engines like Polars and Vaex—without overwhelming with technical detail.
I’ll look for a better way to explain the idea clearly and briefly. Thanks again!