rsc

7 ms·

1.
by rsc 3mo ago
As a long-time open-source maintainer, I find all the second-guessing and armchair psychoanalysis here (not just in this comment, all over HN) about Tridge's motivations, state of mind, and so on incredibly off-putting. Tridge doesn&#x
2.
by rsc 5mo ago
The $20K was the total across all the files scanned, not just the one with the bug.
3.
by rsc 6mo ago
Worth noting these were not written as rules of programming generally but rules specifically targeted at complexity. They are lifted from the "Complexity" section of Rob's "Notes on Programming in C". https:/&
4.
by rsc 7mo ago
Raises hand.
5.
by rsc 1y ago
FWIW, the versions are not semver but they do follow a defined and regular version schema: https://ai.google.dev/gemini-api/docs/models#model-versions .
6.
by rsc 1y ago
[Also posted to Lobsters: https://lobste.rs/s/ms94ja/what_is_go_proxy_even_doing#c_vz2... ] I apologize for the traffic. We clearly need to look at the “thundering herd” you are observing. That shouldn’t be happeni
7.
by rsc 1y ago
This is a strange and dangerous thing to try to do from assembly. In particular, all these details about write barriers being hand-coded in the assembly are subject to change from release to release. Better to structure your code so that yo
8.
by rsc 1y ago
The parent comment is the first time I've said anything publicly (it has only been a few weeks). I didn't feel like it needed an announcement, but since it came up, it seemed worth correcting. It's not a state secret. :-) In
9.
by rsc 1y ago
Officially, I have left the Go team too; I started on a new team at Google a few weeks ago. I still use Go quite a bit, I still talk to people on the Go team regularly, and you will still see the occasional code change, code review, or blog
10.
by rsc 1y ago
Those are semantically different (one is nil and one is not) but neither allocates.
11.
by rsc 1y ago
Not sure what the betrayal is? He contributed a quote for yesterday's post. https://tailscale.com/blog/tailscale-enterprise-plan-9-suppo...
12.
by rsc 1y ago
We had to do some Plan 9 work, which makes sense when doing something new, but the actual Tailscale implementation is far _less_ work than for other Unixes.
13.
by rsc 2y ago
https://docs.rs/txtar/latest/txtar/
14.
by rsc 2y ago
In the link in the parent comment. :-)
15.
by rsc 2y ago
People who go install it get an error that it's not a valid source tree at all.
16.
by rsc 2y ago
While you can create and build a local package with U+FE0E in its file name, you cannot create or download a module using that character in a file name. So you could run this attack in someone's top-level repo but not in any of their d
17.
by rsc 2y ago
No. It's just Go assembly. (It happens to be a Plan 9-derived syntax, but we call it Go assembly.) See https://go.dev/doc/asm .
18.
by rsc 2y ago
I replied to the other copy of this comment: https://news.ycombinator.com/item?id=41136122 .
19.
by rsc 2y ago
This is definitely not true. "Inside of Google" would have been just linux/amd64 for a very long time. Now it includes linux/arm64 too, but that port happened before Google needed it. And all the other ports are not used
20.
by rsc 2y ago
If you just want to run Go programs on Alpine, it works fine. (I put some effort in back in Go 1.21 to make sure that the downloaded binary toolchains for Linux even work fine on Alpine.) If you want to use c-shared mode and dlopen, then ye
21.
by rsc 2y ago
Happy to hear that. Still going to write and think. :-)
22.
by rsc 2y ago
https://www.youtube.com/watch?v=ek1yjc9sSag&list=PLrwpzH1_9u... I don't intend to make more of those, but that was a lot of fun.
23.
by rsc 2y ago
Me too!
24.
by rsc 2y ago
The wording may be a joke but the concept is real and widely used.
25.
by rsc 2y ago
https://research.swtch.com/deps#watch_your_dependencies > Creeping dependencies can also affect the size of your project. During the development of Google’s Sawzall—a JIT’ed logs processing language—the authors discovere
26.
by rsc 2y ago
There were certainly buggy tests that relied on the old behavior. We didn't find any actual code that relied _correctly_ on the old behavior. https://go.dev/wiki/LoopvarExperiment
27.
by rsc 2y ago
> rsc, thank you very much for all the hard work on the language that brought me into software engineering. You're quite welcome, and thank you for this comment. I never expected when we started that Go would have such a positive im
28.
by rsc 2y ago
> Both Austin and Cherry are relatively unknown outside Google and are to my knowledge not active in the community outside Google. I don't believe this is true at all. They are both highly active in external Go development, far more
29.
by rsc 2y ago
I would frame it differently: stack hash bisect is only suitable where your code is linked into some other large program that you don't understand, and when your changes can be toggled on a per-invocation basis. Then you can use it to
30.
by rsc 2y ago
The assumption is that for a given test program, the call stack used at the specific moment where the failure begins is the same each run. If that's not true, there will be problems. If there are two different call stacks that get to t

More ›