Hacker News Reader

If the metric is Google-ability," then so are a lot of other languages:

C D Go Julia R Rust

Google's gotten a lot better when it comes to searches for C++ (formerly always wrote 'cpp'), Go ('golang'), C#, etc. But when you combine a specific search and the language it's still ambiguous for a lot of these languages.

Forever the discord between branding and specificity.

View on HN

I have long advocated for switching away from normal pronounceable names and to UUIDs for everything. For example, Google's Go could be CFF77685-513C-4B4D-82EC-81C171D52E82 and the older one could be 7EFD13ED-BF35-4547-9701-6E13F0D8911E. If we renamed C to F51AD0F2-8159-4515-BE14-5E9D9AE3372B it would become much easier to search for.

Sincerely, 57C1566F-1DA9-4AAB-9F88-E31C4B950DD6

I agree with you, but actually, 57C1566F-1DA9-4AAB-9F88-E31C4B950DD6 is my UUID.

Then I'm afraid we must fight to the death to see who has the rightful claim to it, as described in the secret provisions of RFC 4122.

The first rule of RFC 4122 is that implementers MUST NOT talk about RFC 4122.

Which RFC 4122 are you not talking about, the one that came first or the one that came before?

Yes, trial by combat is the way to go. No pun intended.

Reply on news.ycombinator.com