Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
rsc
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
91.
▲
by
rsc
3y ago
If P1236 ( https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p12... ) is really what it says ("alternative wording") then I don't believe that's true. Certainly P0907R3
92.
▲
by
rsc
3y ago
Not true, as the post explains.
93.
▲
by
rsc
3y ago
There is no major upcoming Go change related to this post. This is just a much longer version of https://research.swtch.com/plmm#ub that I drafted years ago and finally cleaned up enough to post.
94.
▲
by
rsc
3y ago
It's not true that Go can't add new keywords. Now that we have Go modules, all Go code is now explicitly annotated with the version of Go it was written against. We can add a new keyword in a later version of Go as long as the com
95.
▲
by
rsc
3y ago
If you turn off the GC then no memory is collected. In general this is not something people actually do. The only time I've ever even seen it mentioned is in an old blog post by ESR, and between him and me, at least one of us didn'
96.
▲
by
rsc
3y ago
The benchmarks in the blog post are believable but the profile is not. The benchmarks do roughly the same amount of cgo work; all the extra work in the finalizer benchmark is setting up the finalizer, specifically 'runtime.addspecial&#
97.
▲
by
rsc
4y ago
As designed, the system allows an opt-out _either_ by setting GOTELEMETRY=off in your environment or by running 'go env -w GOTELEMETRY=off' which writes a config file. (Specifically the one reported by 'go env GOENV'.) I
98.
▲
by
rsc
4y ago
You can also echo GOTELEMETRY=off >> $(go env GOENV)
99.
▲
by
rsc
4y ago
Right. My hope would be that language tooling offering library developers visibility into compile-time information about library usage would reduce their desire to insert run-time collection instead.
100.
▲
by
rsc
4y ago
I am concerned about run-time telemetry in libraries as well. It might make sense for language ecosystems to offer more data about library usage gathered at build time eventually, as a different system than the one I'm posting about to
101.
▲
by
rsc
4y ago
The only option is to have a proxy sit in the middle between the uploader and the server. You mentioned Tor but it doesn't have to be Tor, just some proxy most users would trust not to collude with the server and that doesn't itse
102.
▲
by
rsc
4y ago
My point is about (1) the broader ecosystem of tools that may need to interoperate and have easy access to "SHA256 the whole file" and (2) the fact that not everything is a tar file that the Nix tools can process. So yes, that
103.
▲
by
rsc
4y ago
> If you adopt Nix fully, ... The case where Nix is not adopted fully is the one I have in mind.
104.
▲
by
rsc
4y ago
You're not wrong, but you're also not being realistic. Nix is not the only system that takes this approach. The Go modules "directory hash" is roughly equivalent, although we defined it in terms of somewhat more standard
105.
▲
by
rsc
4y ago
Thanks for the quick rollback. I want to encourage you to think about locking in the current archive details, at least for archives that have already been served. Verifying that downloaded archives have the expected checksum is a critical b
106.
▲
by
rsc
4y ago
The arena goexperiment contains code used inside Google in very limited use cases that we will maintain, but the discussion on https://go.dev/issue/51317 identified serious problems with the very idea of adding arenas
107.
▲
by
rsc
4y ago
Opting out of background refreshes would mean that fetching a module version that (1) no one else had fetched in a few days and (2) does not use a recognized open-source license might not be in the cache, which would make 'go get'
108.
▲
by
rsc
4y ago
Sounds good. I will reach out over email. Thanks.
109.
▲
by
rsc
4y ago
This isn't true. Sourcehut reported a bug, and since the bug is somewhat involved to fix entirely, we asked what the impact of the bug is to them and offered to make a custom change for the site in the interim. The impact matters: the
110.
▲
by
rsc
4y ago
The Go team has been making progress toward a complete fix to this problem. Go 1.19 added "go mod download -reuse", which lets it be told about the previous download result including the Git commit refs involved and their hashes.
111.
▲
by
rsc
4y ago
That code was in turn a loose port of the dial function from Plan 9 from User Space, where I added TCP_NODELAY to new connections by default in 2004 [1], with the unhelpful commit message "various tweaks". If I had known this code
112.
▲
by
rsc
4y ago
Apologies if the comment sounded like I was trying to provoke. My point was that there is a line, and different languages draw the line in different places. It's true that ints _can_ be made more library-like, but it's also true t
113.
▲
by
rsc
4y ago
Do types like 'int' and built-in operators like integer division smell bad too?
114.
▲
by
rsc
5y ago
> In terms of actual influence the much more obvious choice for father of computer science is Charles Babbage, whose work was both influential during his lifetime and who pioneers like von Neumann and Aiken referenced in their developmen
115.
▲
by
rsc
5y ago
Some tools get unhappy - maybe they are fixed now. There is a reason golang-hg was last!
116.
▲
by
rsc
5y ago
What a sad world it would be if Git were the end of the story, if no one ever built a more compelling version control system. :-)
117.
▲
by
rsc
5y ago
This was done as a joke, but not in response to the Go! issue. If you have the original Mercurial repo from the time of the release, you will see it there from the start. I wrote a longer post about this at https://research.swtch
118.
▲
by
rsc
5y ago
Exactly. In this case, the package manager should use the version of colors that svgo asked for, not the one that appeared on the internet 5 minutes ago.
119.
▲
by
rsc
5y ago
> You're making a big deal about "bought" but it doesn't really matter whether money changed hands. godoc.org existed, Google showed up, and now it does not. This is just as untrue as "Google bought just to cance
120.
▲
by
rsc
5y ago
As far as blessing certain licenses, I believe that we currently recognize all the OSI and SPDX licenses and display documentation for code with any license that permits commercial use. The full list is at https://pkg.go.dev/
More ›