18 ms·
Go 1.23 Released
- scotthew1 2y agodirect link to the release notes: https://go.dev/doc/go1.23 https://go.dev/doc/go1.23
- ptman 2y agoAnd a different take on the changes: https://antonz.org/go-1-23/ https://antonz.org/go-1-23/
- hu3 2y agoOpt-in telemetry. A very rare sight these days. Glad to see. Not even Mozilla does that with Firefox [1]. > Starting in Go 1.23, the Go toolchain can collect usage and breakage statistics that help the Go team understand how the Go toolchain is used and how well it is working. We refer to these statistics as Go telemetry. > Go telemetry is an opt-in system, controlled by the go telemetry command. By default, the toolchain programs collect statistics in counter files that can be inspected locally but are otherwise unused (go telemetry local). > To help us keep Go working well and understand Go usage, please consider opting in to Go telemetry by running go telemetry on. In that mode, anonymous counter reports are uploaded to telemetry.go.dev weekly, where they are aggregated into graphs and also made available for download by any Go contributors or users wanting to analyze the data. See “Go Telemetry” for more details about the Go Telemetry system. [1] "Firefox collects telemetry data by default. We collect this data to help improve the performance and stability of Firefox. Telemetry data is made up of two data sets: interaction data and technical data." - https://support.mozilla.org/en-US/kb/telemetry-clientid https://support.mozilla.org/en-US/kb/telemetry-clientid
- mococa 2y agoUntil they decide it to be enabled by default.
- eps 2y agoExactly. Give it a couple of releases and the default "for new installations" will be On. Two more releases and all other installs will be opted in. Classic pattern for shoveling stuff down the throat of resisting gray masses.
- Foxboron 2y agoAt which point us, the Linux packagers and other package maintainers, is just going to patch it out. I wouldn't be very worried.
- cma 2y agoAnd Google makes you call it something other than Go, like Firefox did to linux packagers: > The Go trademark and the Go Logo ( ) – collectively, the “Go Trademarks” – are trademarks of Google and are treated separately from the copyright license grants contained in the BSD-licensed Go repositories, as described below. > Substantially unmodified distributions¶ > Substantially unmodified distributions may use the Go Trademarks if the derivative work complies with the terms of the Go programming language’s open source license and is made in a good faith attempt to replicate the quality and substance of the original project. > Examples of modifications that would be considered substantially unmodified include language translation and localization, bug and security patches, and necessary interoperability/compatibility modifications. > The Go Trademarks may be used in connection with such substantially unmodified distributions following the “Naming Conventions for Authorized Uses”. > Substantially modified distributions may include explicit changes to functionality, interfaces, or features. They can modify these trademark terms later too with a "backwards incompatible" change: > Guideline Version¶ > These Trademark Guidelines are version 1.0 and may be followed by subsequent versions. These Guidelines may be edited for clarity; the major version will be increased when changes introduce new requirements, define new criteria, or otherwise present a backwards incompatible change.
- Foxboron 2y agoIt's not 2006 anymore.
- candiddevmike 2y agoThere was a lengthy discussion to persuade them to not have it on by default: https://github.com/golang/go/discussions/58409 https://github.com/golang/go/discussions/58409
- mholt 2y ago> Opt-in telemetry. A very rare sight these days. Because it doesn't work. o:-) (Introduces a slant/bias to the data.) https://twi.github.io/blog/making-go-telemetry-opt-in-is-a-mistake.html https://twi.github.io/blog/making-go-telemetry-opt-in-is-a-m...
- wsve 2y agoI'm open to being convinced otherwise, but I feel like I'm the only one who doesn't get why opt-out telemetry is such a big deal. Sure, if it's a software library, I don't want it doing random network calls during my runtime. That's just rude. But if it's a user application (including a compiler), I don't see what the fuss is about. Of all the myriad of ways our data is harvested every single day, telemetry seems very unhelpful to advertisers and hackers, but very helpful to the people whose job it is to make the software you use better. I'd love to help them make the software I use better
- kingsleyopara 2y agoPrivacy concerns aside, I personally don't appreciate binaries making network requests unless it's strictly required for them to function.
- wsve 2y agoWhere is that line for you? Is occasionally checking for security updates strictly necessary? Is reporting a crash to the devs so they can fix it necessary? What about sending system & usage telemetry so they can prevent future bugs?
- Zuiii 2y agoFor me, it's like GP said: Absolutely no unauthorized network traffic unless strictly required for the purpose of the software (e.g. curl). No security updates, crash reporting, telemetry unless you prompt the user and show the user exactly what will be sent (similar to how syncthing does it). Anything less is voyeurism.* * extreme language I know, but it's precisely how I feel about these acts.
- justinclift 2y ago> Where is that line for you? None of the above is acceptable. Crash reporting can generate its output locally for people to manually send, if they choose to do so.
- _xiaz 2y ago
- rkharsan64 2y agoIt seems like the right way to respect a user's privacy, but opt-in telemetry just doesn't work. I see the concerns as a user (and disable telemetry wherever I can), but at the same time if I were to add telemetry to my OSS project, I would either make it opt out, or just not add it at all. The people who actually enable telemetry are a huge minority, and the data collected would be completely useless due to bias. The best way, in my opinion, is to have completely unidentifiable telemetry (not sure if something like this even exists), or nothing at all.
- slowmovintarget 2y ago> The best way... The best way is not to have telemetry at all. But then that's a user-centric take.
- traceroute66 2y ago> Opt-in telemetry. A very rare sight these days. Glad to see. Ahem. Cough. Given Google's ties to Go, of course it was NOT opt-in when originally announced. After, shall we say, a "lively" discussion on the relevant Github topic[1], it was changed to opt-in. :D Opt-in is the correct stance. [1]https://github.com/golang/go/discussions/58409 https://github.com/golang/go/discussions/58409
- bananapub 2y agothere's infinity things to criticise google for, but "the go team want useful metrics" isn't one of them.
- deleted 2y ago[deleted]
- kjs3 2y agoThere's the "If you have nothing to hide..." guy.
- frosting1337 2y agoBut it is now, and that's good and should be applauded.
- _xiaz 2y agoI don't believe the Go team deciding not to break GDPR law after massive backlash is anything that should be applauded.
- frosting1337 2y agoI'm not really understanding the logic here, but you do you bud.
- euroderf 2y agoI'd bet you dollars to donuts that the Go team originally asked for opt-in and got overruled by suits.
- rollcat 2y agoGoogle can already see every installation of every Go program/package in existence, unless you set GOPROXY=direct (or a custom proxy). The default is to use https://proxy.golang.org https://proxy.golang.org, which is operated by Google.
- ianlancetaylor 2y agoThe default proxy has a privacy policy: https://sum.golang.org/privacy https://sum.golang.org/privacy.
- tharax 2y agoBut better than this is would be if my go tooling didn't default to trying to pull codebases through a proxy Forgive me for being cynical, but I don't like that out of the box the toolchain tries to pull all the code at `example.com/business/logic` through google servers.
- divan 2y agoboring <3
- tmountain 2y agoThe way it should be.
- ronsor 2y agoAdding support for encrypted client hello to the TLS library is pretty exciting. I've been waiting a while for that.
- fourseventy 2y agoI don't like the "range-over-func" addition. I feel like it is adding complexity and syntactic sugar to the language that has thus far been mostly avoided.
- icholy 2y agoThe change adds no syntax.
- fourseventy 2y ago"for key, val := range m.Range" is syntactic sugar for using the m.Range iterator directly "m.Range(func(key, val any) bool". In a vacuum I think it's fine, but I don't want to see stuff like this getting added to the language routinely. I prefer a small language.
- pptr 2y agoI think the key difference is that in a loop body you can return from the outer function. In a function passed to m.Range you can't.
- tedunangst 2y agoGo 1.22 is still right there.
- unscaled 2y agoGo grew too big (in popularity) to be small. Popular languages tend to grow as the userbase grows. This is natural — the language gets used across a wider range of industries, and the programs being written in the language become larger, more mature and more diverse. The language maintainers need to balance a small specification or a small implementation versus the users' demand, but in most cases at least some user demands win routinely. This is especially true when the language has just one major implementation. There is a significant cost for making that implementation more complex, but there is a more significant cost for making millions of programs that rely on a single implementation more complex just to make that implementation simpler.
- epage 2y agoAs someone who was advocating for a similar warning in Rust (finally added to clippy in 1.78), I'm glad to see this improvement in `go vet` > The go vet subcommand now includes the stdversion analyzer, which flags references to symbols that are too new for the version of Go in effect in the referring file. (The effective version is determined by the go directive in the file’s enclosing go.mod file, and by any //go:build constraints in the file.) > > For example, it will report a diagnostic for a reference to the reflect.TypeFor function (introduced in go1.22) from a file in a module whose go.mod file specifies go 1.21.
- minkles 2y ago> Go telemetry is an opt-in system Great job Go. Hat tip and respect for this. Unlike .Net. I will enable this where it is appropriate.
- efilife 2y agoWhere is it? I honestly want to know
- maccard 2y agoThis is a great example of why it's utterly useless. In the link we're discussing, the release notes say: > To help us keep Go working well and understand Go usage, please consider opting in to Go telemetry by running go telemetry on. In that mode, anonymous counter reports are uploaded to telemetry.go.dev weekly, where they are aggregated into graphs and also made available for download by any Go contributors or users wanting to analyze the data. See “Go Telemetry” for more details about the Go Telemetry system. If someone who is genuinely interested in knowing where it is can't click one link for information, what chance do the go team have of people turning it on?>
- neonsunset 2y agoFWIW .NET tooling telemetry can be easily opted-out, which the SDK explicitly tells you about, and there is a page that has full list of the kind of data that is collected (CLI usage metrics and tooling crash stack traces). You can also review the metrics yourself. About: https://learn.microsoft.com/en-us/dotnet/core/tools/telemetry https://learn.microsoft.com/en-us/dotnet/core/tools/telemetr... Collected metrics: https://dotnet.microsoft.com/en-us/platform/telemetry https://dotnet.microsoft.com/en-us/platform/telemetry Source code: https://github.com/dotnet/sdk/tree/main/src/Cli/dotnet/Telemetry https://github.com/dotnet/sdk/tree/main/src/Cli/dotnet/Telem... In either case, many teams have CIs with 'DOTNET_CLI_TELEMETRY_OPTOUT=1' and call it a day even if it makes no difference to them.
- minkles 2y ago[flagged]
- deleted 2y ago[deleted]
- ffpip 2y agoAny good resources on learning go? Has anyone had any luck with the YT videos or courses way?
- candiddevmike 2y agoIf you are familiar with programming, Tour of Go is a good overview of the language: https://go.dev/tour/ https://go.dev/tour/
- ffpip 2y agoThanks
- DoctorOW 2y agoI hope I don't sounds rude saying this but Go code is generally self evident. I personally got my Go knowledge from reading Go code on GitHub or the like. There's a certain beauty to Go code in that you can grasp what code does pretty easily, which definitely helps with learning.
- sapiogram 2y agoYou've clearly never opened Kubernetes' source code.
- wrs 2y agoGo is superficially readable, but be careful. It has some (in my experience) quite non-evident semantic aspects, such as interface nils and channel “edge cases” (which aren’t “edge” at all, you do have to handle them). The Timer thing they just fixed is an example of how the Go core team really expects you to read the manual. The good news is that the language and stdlib docs are concise and extremely clear. One of the really impressive things about Go.
- rowanseymour 2y agoI've been writing go for about 7 years and still occasionally footgun myself with nil interfaces. Drives me insane that they try so hard everywhere else to protect devs from themselves but that still exists.
- nalgeon 2y agoIf you find the official release notes a bit dry (they really are), I've prepared an interactive version with lots of examples: - Iterators (range / types / pull / slices / maps). - Timer changes (garbage collection and reset/stop behavior). - Canonical values with the `unique` package. - HTTP cookie handling. - Copying directories. - Slices and atomics changes. https://antonz.org/go-1-23 https://antonz.org/go-1-23
- danielvaughn 2y agoThank you for your service, this is awesome! I'd love to see language maintainers post interactive release notes like this.
- felixge 2y agoThis is great, thank you.
- metadat 2y agoI want to understand the purpose of maps.All(). In the example: m := map[string]int{"a": 1, "b": 2, "c": 3} for k, v := range maps.All(m) { fmt.Printf("%v:%v ", k, v) } fmt.Println("") for k, v := range m { fmt.Printf("%v:%v ", k, v) } These both output the same thing. What's the point of the addition? Slices.All() seems similarly redundant and pointless. Surely I must be misunderstanding something, I hope.
- sakjur 2y agoThey’re useful because they let you pass a slice or map to something built to handle the new func(func (…) bool) style iterators. If I create a IterateOver(fn func(func (K, V any) bool)) function, you cannot pass a slice since that doesn’t match fn’s type, but if you wrap it with slices.All it’ll work.
- deleted 2y ago[deleted]
- ianlancetaylor 2y agoYou can use it with other functions that use iterators. For example, here is code that makes a copy of a map keeping only the even keys. maps.Collect(xiter.Filter2(func(k, v int) bool { return k%2 == 0 }, maps.All(m)))
- rkharsan64 2y agoFrom the release notes [1], which I think this post should actually point to: > For backward compatibility, existing usages of //go:linkname found in a large open-source code corpus remain supported. Any new references to standard library internal symbols will be disallowed. How does this work? Does the compiler have a whitelist of allowed uses? [1]: https://go.dev/doc/go1.23 https://go.dev/doc/go1.23
- tedunangst 2y agoThe source has to be annotated to export the function.
- rkharsan64 2y agoJust confirming if I understand this correctly: they went through a big chunk of existing code, and then made any internal symbols used in that corpus accessible via //go:linkname? I don't know why, but I (stupidly) assumed that they wouldn't allow new code to be written that uses those symbols, while allowing old code to work. :) This explanation makes a lot more sense. So, you can keep using the symbols exposed with this change (until a future release hides/changes them), but cannot use any other internal symbol(s) anymore.
- ianlancetaylor 2y agoYes.
- 38 2y agoWhy is it not dated?
- euroderf 2y agoI'd like to see a best-practices range-compatible depth-first preorder push iterator for a tree. Any tree implementation would do for purposes of exposition; for example package ast, where node order is important, unlike package filepath. FWIW there is current discussion in issue 64341 (and also 61405).
- EdiX 2y agoYou could do: func inspect(n ast.Node) func(func(ast.Node) bool) { return func(f func(ast.Node) bool) { ast.Inspect(n, f) } } used: for n := range inspect(f) { fmt.Printf("%T\n", n) }
- euroderf 2y agoOK, this works cos package ast already has `func Inspect`. So how about a more general case ? A case where we do not have a `func Inspect` already in the stdlib ? Maybe just replace it with (for example) `filepath.WalkDir` ?