4 ms·

I think the problem here is with HN's obsessive title editing, not the library name.

• bmitc 4y ago
  I agree on the title editing, which I in general dislike, especially when no comment is left. But I disagree that this isn't confusing. Imagine the conversation: Dev1: Says something about nodal diagrams. Dev2: Suggests taking a look at Svelvet. Dev1: Confused since they're already using Svelte and ignores the comment or suggestion and moves on. <months later> Dev1: We're developing our own internal nodal diagram library. Dev2: Did you look at Svelvet like I suggested. Dev1: Yes, we're already using Svelte. Dev2: No, I mean *Svelvet*. Dev1: Oh... It's like calling a React library Reactor or Reacts or something like that. It's way too close for no reason. Just look at this thread for many examples of why naming your library so close to the framework it sits on top of is a bad idea.
  • toqy 4y ago
    Imagine how much time Dev2 could have saved by sharing a link instead of name dropping obscure libraries they read about on HN
    • bmitc 4y ago
      It's an anecdote. Conversations, text-based or auditory, happen in passing. Maybe you missed where someone literally did drop a link (this post) and people, including the mods who renamed the title from Svelvety to Svelte and then back again, confused the two.