Yes, and creating a new product with a familiar name has some benefits. To the consumer it gives them familiarity without expectation, they know from the name what it does and what to expect in limitations (e.g. Go = minimalist). On the developer it gives them the freedom to ignore or abandon unpopular, limited use, or difficult to implement features in the name of stream lining a product.
Wouldn't it just make sense to optimize the original version? Having multiple naming conventions seems like an invite to confusion.