[dead]
1. Wrong. There are cases where reproducible builds are valuable. There are other times when you don’t care. This allows you to choose for what fits your situation.
2. Okay, what about projects that don’t fit your criteria? This is useful and requested.
You seem to have a different philosophy than other people but seem to be unable to consider those other philosophies. It’s your way or the highway.
Not everyone wants an exciting language. Some people want a stable and useful language. Go is intentionally not exciting. They add features based on user feedback and real world use, at a slow and careful pace.
Also consider you might get downvotes not because it’s about go, but because you’re kinda rude. You just spouted negativity with no explanation and called tons of people Sons of Bitches. Could be that?
Re:Three Minor Features in Go 1.18
by aniforprez on Wednesday December 22, 2021 @09:07PM
(#29657874)
I think the guarantee of downvotes is for your absolutely awful attitude
For your criticism regarding reproducible builds, I'm not sure it's entirely correct. The impression I got from a skim was that version control metadata was being embedded, such as the git commit hash or maybe a tag. Both of which are static within the constraints that builds are generally reproducible across. However, if it includes timestamps or some generated metadata, then I wholeheartedly agree with your concerns.
Re:Three Minor Features in Go 1.18
by jdhendrickson on Wednesday December 22, 2021 @10:46PM
(#29658433)
Ok, if GO is soulless what languages have a soul? Just curious.
1. Care to elaborate?
2. What does this even mean?
3. It’s in the pending release notes with all the other new features and further information in the post you’re commenting on. https://tip.golang.org/doc/go1.18
Try to be more constructive if you want a conversation please.