typical182

7 ms·

1.
by typical182 18d ago
FWIW, every commit for the Go project is tested on multiple 32-bit architectures, including pre-commit tests and post-commit tests. You can see a list here: https://build.golang.org/ (That particular build dashboard just sh
2.
JSON evolution in Go: from v1 to v2(antonz.org)
15 points by typical182 23d ago|0 comments
3.
by typical182 2mo ago
And to answer the second half of your request, here is that exact same code as above, but now using the 1.27 generic methods feature (with a runnable example using tip at https://go.dev/play/p/1YK62tGetsm?v=gotip )
4.
by typical182 2mo ago
It's not a great example. I think it's trying to show a mapping operation for a generic container where the container values are of one type and the mapping function is allowed to return a container with values of a different type
5.
by typical182 2mo ago
FWIW, I do remember that quote. It doesn't seem particularly damning to me, though, especially written by Russ Cox in hindsight. It's almost a truism that if you had spent less time on approaches that didn't pan out and more
6.
by typical182 2mo ago
> it finally took convincing Philip Wadler (of Haskell and Java generics fame) to help. Without that lucky break [...] Go probably still wouldn't have generics. Small correction, I think: My understanding is the core Go team was a
7.
by typical182 2mo ago
From what I've seen, I don't think the core Go team was ignoring the lessons of Java or C#. Here's a sample quote from Russ Cox from 11 years ago on this site: [1] We have spoken to a few true experts in Java generics and ea
8.
ATProto for Distributed Systems Engineers(atproto.com)
2 points by typical182 2mo ago|0 comments
9.
by typical182 8mo ago
Go modules did not get rid of vendoring. You can do 'go mod vendor' and have been able to do so since Go modules were first introduced. How long the google-run module cache (aka, module proxy or module mirror) at https:/&#x2
10.
by typical182 8mo ago
> They may be an expert in Go, but from their writing they appear to be misunderstanding (or at least misrepresenting) how things work in other languages Thanks for that link. Based on reading through that whole discussion there just n
11.
by typical182 9mo ago
There’s some more context in a proposal from the folks behind this project to upstream the needed Go runtime hooks into Go proper. From what I can tell, the core Go team seems generally favorable to it, so seems like a decent chance it will
12.
Go 1.26 Release Candidate 1 is released(go.dev)
4 points by typical182 9mo ago|0 comments
13.
Go 1.26 Release Candidate 1 is released(groups.google.com)
1 points by typical182 9mo ago|1 comments
14.
by typical182 9mo ago
Draft 1.26 release notes: https://tip.golang.org/doc/go1.26
15.
by typical182 1y ago
The arena experiment was essentially placed on indefinite hold: > The proposal to add arenas to the standard library is on indefinite hold due to concerns about API pollution. I think the parent comment was using arenas as an example t
16.
by typical182 1y ago
> The biggest problem is any string you pass as an argument to the fmt functions is moved onto the heap FWIW, that's not quite correct. For example, a string literal passed as a fmt argument won't be moved to the heap. The up
17.
Green Tea Garbage Collector(github.com)
2 points by typical182 1y ago|0 comments
18.
by typical182 2y ago
Bluesky and atproto seem to be built to be hackable. Someone in the community recently built a searchable directory of Bluesky "Starter Packs" (which are a way for a user to publish a set of interesting people & feeds to follo
19.
by typical182 3y ago
> you can simply forbid pointers into the stack. This means that your GC doesn't need to be moving. I believe that's what Go does I might have misunderstood your comment, but FWIW, Go does allow pointers into the stack from the
20.
Timoni – Next-Gen Package Manager for Kubernetes(stefanprodan.com)
1 points by typical182 3y ago|0 comments
21.
by typical182 3y ago
The “Personal” in PDS doesn’t mean it is only for self-hosting. Bluesky has a main PDS instance at https://bsky.social that serves almost all of the Bluesky user base. There is a good overview of the architecture here: https:&#
22.
by typical182 3y ago
If I understand the question, I think that is rsc.io/unix/v6unix, which is at https://github.com/rsc/unix/tree/main/v6unix : "Research Unix Sixth Edition (v6) kernel written in Go and u
23.
by typical182 3y ago
Effectively yes. A fix for the loop variable closure problem is now in the official proposal process, which is how language changes happen in Go. It’s a concrete proposal from the core Go team and seems to be on track for acceptance: https
24.
by typical182 3y ago
People should essentially never set GOROOT. It's mostly a holdover. For example, Ian Lance Taylor on the core Go team wrote [0] somewhat recently: "It's a special purpose hook that is almost never needed". [0] https:&#x
25.
by typical182 3y ago
> Generics seemingly split the community. May be some libraries won’t get used because they picked the wrong side. I haven't really observed that at all. One thing that is going on is there hasn't been a massive disruption whil
26.
by typical182 3y ago
goda[0] is excellent . You do do things like: # show the impact of cutting any package goda cut ./...:all which prints a sorted ASCII table with stats like 'size:4.4MB loc:134171' for each package, which is an es
27.
by typical182 3y ago
There is a pretty complete description of the origination of UTF-8 here: https://www.cl.cam.ac.uk/~mgk25/ucs/utf-8-history.txt Rob Pike opens with: > Looking around at some UTF-8 background, I see the same inco
28.
by typical182 4y ago
FWIW, this is maybe an area where Go goes against the grain a bit and goes out of its way to not allow code you just downloaded to execute anything while you are building. For things like 'go generate', the convention is to check
29.
Opting in to Transparent Telemetry in Go(research.swtch.com)
2 points by typical182 4y ago|0 comments
30.
by typical182 4y ago
This seems to be a nice example of maintainers of a popular open source project listening to feedback from the broader community: > Thanks to everyone who took the time to write constructive, helpful feedback. Those discussions are open

More ›