In fact postgresML took naming heat because Postgres is right there in the name and they weren't affiliated with the brand. "pg" is just two letters. like WP-engine (literally the name as they say it is "double U P engine").
And a cat and a dog is fun.
don't think they're trying to get one over on you.
I don't think they're trying to get one over me, nor do I think it's _that deep_. One should simply acknowledge the prior projects that led to where you are today, even if they are your own. I 100% stand by my original statement and think that pgDog should mention that they're affiliated or a paid product on top of pgCat!
The trailing snark at the end will likely get you downvoted but I'm latching on: wtf is "system card". My previous coworkers popped that in the general slack channel when Mythos first "dropped" - "have you seen the system card" without any context whatsoever. The nerds get their clique!
Also research preview pops across new upstarts in place of beta. It's eye-rolling coming from a lifelong curmudgeon.
But most hype-dependent projects need new vocabulary for old concepts to keep people from looking too closely and maybe drawing parallels to "legacy" "unsexy" projects, so whitepapers get called "system cards" and startups get called "labs", and so on.
Couldn't someone else equally well argue that "whitepaper" and "startup" are hyped-up vocabulary for "report" and "unprofitable company"? It kinda seems to me like the cause and effect are in the other direction, and the vocabulary of a particular niche becomes cool and hype-sounding when that niche starts to pull in a lot of money.
> [Isn't] "whitepaper"... hyped-up vocabulary for "report"[?]
Yes, I agree strongly. I used "whitepaper" because I didn't want my comment to reach back before too many HN readers were born... but I generally use the term "report".
> [Isn't] "startup" ... hyped-up vocabulary for ... "unprofitable company"?
No. It's hyped-up vocabulary for "new, investor-funded company". Many are unprofitable, but they need not be. Old companies will declare themselves to be a startup company, but that's like an eighty-year-old human declaring that he's spry and flexible.
> ...the vocabulary of a particular niche becomes cool and hype-sounding when that niche starts to pull in a lot of money.
It does, yes. But there's more to it. Projects that want to generate hype because they don't stand up to careful scrutiny will invent new jargon for old concepts. This causes people who would rather deeply misunderstand something than appear to not understand something that they think their peers strongly support to fail to discover that the "new, sexy, revolutionary" thing is the same system everyone has been using, just in a new wrapper.
yes at some point language evolves as the new normal, as designed.
My curmudgeon gripe with system card and research preview is really the parroting; so cant blame anthropic for what others do. It’s just… no, prediction markets for dogs doesn’t have a research preview.
Interestingly, as a professional developer I had the opposite first experience. It's a tracker. It looks like every other tracker. Everything is really small and "clean" which means they just hide everything, for that modern look.
I was thoroughly unimpressed. "This is it?" - "It's a tracker"
I feel comfortable saying this because in the weeks after, actually using it is the aha experience. Linear nailed the UX of working where people already work. Which again is really funny because the best part of Linear is how well it works outside of Linear.
(disclaimer: I actually now use their UI a lot. It's a helpful dashboard. But it suffers from every other hard-problem of information dense task-based dashboards.)
reminds me that there's built in color names in CSS. I use them extensively and I think this is what the OP is getting at? Not overthinking it. cornsilk and tomato are two of my favorites.
I agree but the practical cost is most heavily paid in a collaborative work setting. Now everyone at all layers of a company is doing build prototype exploration but without the intermediary internal-filter check. Instead, these explorations get a straight line to production, for reasons I'm not exactly sure. Because it can I guess?
That's the part that surprises me. I have only ever shared one prototype I made with AI, and only because we were presenting on how we were exploring AI use and with constant mention that it was a proof of concept prototype.
I feel like putting any prototype, even if it was hand written, would be really risking my credibility if I put it into production without having it at least to the point that it wouldn't matter if it was vibe coded, via a few weeks of using the project myself.
Yeah that's where my eyebrows go to the moon. My investigations are at best in staging after a dev machine review, if nontech people are involved you need per-user cloud dev I think
reply