HN

Need help?
<- Back
UUID package coming to Go standard library

UUID package coming to Go standard library

soypat

Comments (80)

  • vzaliva
    A slow day in Go-news land? :)It is heathwarming to see such mundane small tech bit making front page of HN when elsewhere is is debated whether programming as profession is dead or more broadly if AI will be enslaving humanity in the next decade. :)
  • matja
    > UUID versions 1, 2, 3, 4, 5 are already outdated.Interesting comment, since v4 is the only version that provides the maximal random bits and is recommended for use as a primary key for non-correlated rows in several distributed databases to counter hot-spotting and privacy issues.
  • KingOfCoders
    One thing I love about Go, not fancy-latest-hype features, until the language collapses or every upgrade becomes a nightmare, just adding useful stuff and getting out of the way.
  • kayson
    Odd to me that the focus seems to be on the inactivity of Google's package when https://github.com/gofrs/uuid not only conforms to the newer standard but is actively maintained.
  • didip
    Based on the conversation, is it actually coming?
  • therealdrag0
    Golang lack of support for basic stuff like this is quite annoying.
  • kittikitti
    Every time I've implemented UUID's it's for a database and something like PostgreSQL would handle it. Still glad to see this feature being worked on, I would have utilized a random string generator instead of the full battle tested UUID specification.
  • waynesonfire
    what a bunch of drama in the comments.
  • cookiengineer
    Every time I read these types of Go issues, I think I am reading a writeup of a highschool debate club. It's like there is debate just for the sake of debate.I understand the defensiveness about implementing new features, and I understand the rationale to keep the core as small as possible. But come on, it's not like UUID is a new thing. As the opener already pointed out, UUID is essential in pretty much all languages for interoperability so it makes sense to have that in the standard language.Anyways, I'm just happy we'll get generic methods after 10 years of debates, I suppose. Maybe we'll get an export keyword before another 10, too. Then CGo will finally be usable outside a single package without those overlapping autogenerated symbols...
  • jeffrallen
    Am I the only one who hates UUIDs and doesn't see the point of them?Having any structure whatsoever in them is pointless and stupid. UUIDs should be 128 buts of crypto.Rand() and nothing else.Argh.