typical182

8 ms·

61.
by typical182 5y ago
There is also a WIP Go proposal for adding a set to the standard library using the upcoming generics: https://github.com/golang/go/discussions/47331
62.
by typical182 5y ago
I think though it is recommending against strncpy as well… linters and code reviewers commonly recommend alternatives such as strncpy (difficult to use correctly; mismatched semantics) […] Besides their individual shortcomings, these answe
63.
by typical182 5y ago
People can have different definitions and still communicate usefully, and I think there is not 100% agreement on the exact boundaries between the two. That said, for me: they are distinct but related, and that distinction is useful. For exa
64.
by typical182 5y ago
There is a good LWN article that gives a useful overview of the current proposal as well as briefly hits on some of the history: https://lwn.net/Articles/829242/
65.
Add experimental fuzz test support for Go 1.17(github.com)
121 points by typical182 6y ago|30 comments
66.
by typical182 6y ago
Based on reading through various posts from Discord people after that blog was posted, my understanding was there was a material gap in time between the last time they tried in earnest to solve the latency issue with Go (with Go 1.10, as in
67.
by typical182 6y ago
> Do you know if that was the case when the decision to switch was made? It’s a good question. The timing is a bit confusing because the blog was apparently published a bit after the fact, but I think I saw that they said they made the d
68.
by typical182 6y ago
True, and it was an interesting case study.
69.
by typical182 6y ago
I had looked at the Discord GC blog issue [1] fairly carefully, and it certainly seemed that specific GC latency issue they hit and blogged about would have been solved by upgrading to a modern Go version.... Also, after publishing that blo
70.
by typical182 6y ago
FWIW, “comparable” and “ordered” are well defined terms in the Go language specification: https://golang.org/ref/spec#Comparison_operators
71.
by typical182 6y ago
In terms of where it is used, here is a related tweet by Filippo Valsorda: https://twitter.com/FiloSottile/status/1270115515378384897 For scale, this GnuTLS vulnerability is considerably worse than Heartbleed. If
72.
by typical182 7y ago
It looks like it has been released now.
73.
by typical182 7y ago
If you haven't already, it sounds like it would probably be worth your time to open an issue. If things like workspace-scoped references and renaming aren't working for you when they are working for other people, perhaps you have
74.
by typical182 7y ago
Are you using an old version of gopls? From the v0.3.0 release notes[1]: Workspace-scoped references, rename, and go to implementation. These features use your workspace root as the search scope, so behavior will vary based on the director
75.
by typical182 7y ago
> Godoc is broken because of it That was resolved a while ago. Godoc supports modules[1]: For those who are following this issue because you are waiting for module support in the godoc command (golang.org/x/tools/cmd&#x2F
76.
by typical182 7y ago
As far as I understand, I don't think it is officially released as of this moment. (It is getting close, though). For example, as of now, the standard release note url for 1.14 currently 404s: https://golang.org/doc&#x2
77.
0-day? 677-day? Linux security in a nutshell(mobile.twitter.com)
2 points by typical182 7y ago|0 comments
78.
by typical182 7y ago
Do you have any load tests or synthetic benchmarks that are still capable of producing this? It would be interesting to see what a more modern Go would do given there have been a bunch of tail latency GC improvements since your older 1.9 Go
79.
by typical182 7y ago
Maybe that is what they hit... but it seems there is a pretty healthy chance they could have resolved this by upgrading to a more modern runtime. Go 1.9 is fairly old (1.14 is about to pop out), and there have been large improvements on tai
80.
by typical182 7y ago
Where does it say that? It says things like: “We were not creating a lot of garbage.” ... but that statement there doesn’t say anything about the heap size, including the size and count of live objects (i.e., not garbage). It also says:
81.
by typical182 7y ago
Probably a dumb question, but how do you envision connecting something like a networked printer? Front it with a cheap device?
82.
by typical182 7y ago
For context, this is a post from bradfitz, the creator of LiveJournal, memcached, OpenID, been on the core Go team for last 10 years or so. There was a recent thread on him leaving Google: https://news.ycombinator.com/item?i
83.
Joining Tailscale: Simplifying Networking, Authentication, and Authorization(bradfitz.com)
74 points by typical182 7y ago|32 comments
84.
by typical182 7y ago
As far as I have followed, I think it is more that while a fair amount of work had gone into prior designs for generics in Go, the general feeling of the core Go team was the prior designs did mesh well with the rest of the language, wherea
85.
The Life of a Bad Security Fix(grsecurity.net)
2 points by typical182 7y ago|0 comments
86.
by typical182 7y ago
For Go on Darwin: libSystem is now used when making syscalls on Darwin, ensuring forward-compatibility with future versions of macOS and iOS. From https://golang.org/doc/go1.12#darwin
87.
by typical182 7y ago
Probably worth filing an issue, if you haven’t already? Some chance you might be hitting some pathological behavior that could be fixed or tweaked.
88.
by typical182 7y ago
> The mainline kernel, as released by the Linux core team is up to date with security. Hold to account people that decided to skip patches as a matter of course To me, the particulars of this exact case are not as interesting as the fa
89.
by typical182 7y ago
To me, the biggest part of this story is: 1. Over two years ago, this was apparently detected automatically by the syzkaller kernel fuzzer, and automatically reported on its public mailing list. [1] 2. Over a year and a half ago, it was app
90.
by typical182 7y ago
Yes, fixed upstream near start of 2018, but apparently never merged back to various “stable” kernels. See for example: https://mobile.twitter.com/grsecurity/status/118005953923380...

More ›