Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
typical182
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
typical182
4y ago
FWIW, there is a proposal to add telemetry to LLVM [0] and Rust used to have telemetry [1], both off by default. Some things in the node.js world have telemetry enabled by default, like Next.js [3]. Some people are posting here as if this i
32.
▲
by
typical182
4y ago
Some additional context in this comment: https://news.ycombinator.com/item?id=34754632
33.
▲
by
typical182
4y ago
FWIW, people had started to post obscene ASCII drawings, were using various curse words, and there were many, many repetitive comments across the ~400 comments posted. From what I understand of the conversation there, the core Go team said
34.
▲
by
typical182
4y ago
I just submitted shfmt separately: https://news.ycombinator.com/item?id=34754116 It’s nice, and it probably deserves to be more widely known...
35.
▲
Shfmt – format shell programs
(github.com)
115 points
by
typical182
4y ago
|
23 comments
36.
▲
by
typical182
4y ago
shfmt is like gofmt, rustfmt, ..., but for shell programs. Supports bash, posix, mksh, bats.
37.
▲
by
typical182
4y ago
For open source projects in general, and the Go project in particular, I think it is easy to underestimate how much maintainer time is consumed discussing & considering whether a change should be made.
38.
▲
by
typical182
4y ago
As I understand it, written in Go. There's a mildly humorous "How do you know" exchange where someone on HN quizzes the very person most likely to know: https://news.ycombinator.com/item?id=9920020
39.
▲
by
typical182
4y ago
> the ban prevents me from discussing the matter further Hi ddevault, FWIW, in May 2022 on that #44577 issue [0] you had opened, it looks like someone on the core Go team commented there [1] recommending that you email the golang-dev mai
40.
▲
by
typical182
4y ago
Some people today raised concerns about disabling background refreshes (the temporary workaround originally suggested by the Go team) as having possibly unacceptable resulting performance for end users... ...but it sounds like disabling bac
41.
▲
by
typical182
4y ago
Semi-related question: did Latacora or @tqbf ever open source their Go-based SAML IDP: https://twitter.com/tqbf/status/938501701526487040 (That tweet I think was a teaser saying it was coming. I subsequently looke
42.
▲
The Go Programming Language and Environment
(cacm.acm.org)
3 points
by
typical182
4y ago
|
1 comments
43.
▲
by
typical182
5y ago
Hi Steve, first, thanks for weighing in here! I might have misunderstood your comment, but in my GP comment I was indeed attempting to contrast 'go install foo@latest' with 'cargo install foo', which both install binarie
44.
▲
by
typical182
5y ago
In that same section, the blog describes the behavior of 'go install foo@latest' and contrasts it to how the default install "in some ecosystems bypass pinning." That is also a difference in default behavior between Go a
45.
▲
by
typical182
5y ago
The default way Go handles go.mod is fairly different than the default way Cargo handles Cargo.lock files, including for example with libraries. Also, when the blog says: > Moreover, when a dependency is added with go get, its transitive
46.
▲
by
typical182
5y ago
That's a nice & concise way to describe it.
47.
▲
by
typical182
5y ago
> Okay but if I depend on A and A depends on C and has it pinned at 1.5, but I also depend on B and B has C pinned on 1.8, then I get 1.5? No, you end up with the highest explicitly required version. So 1.8 in that scenario, if I follo
48.
▲
by
typical182
5y ago
I think you might have a small typo here: > by choosing the lowest version specified in any package that depends on a given package It picks the highest version specified in any of the requirements. (That's the minimal version t
49.
▲
by
typical182
5y ago
That's not correct. You can unilaterally decide to update the version of E without waiting for anyone. Alternatively, if only C for example decides to update their required version of E, you would get that version of E if you updated y
50.
▲
by
typical182
5y ago
I suspect the primary purpose of the word "may" in that sentence is that you can choose to disable checking the hash against the Certificate Transparency style https://sum.golang.org . In other words, you can opt out. I
51.
▲
by
typical182
5y ago
Continuing that example -- in Go you end up with v1.0.1 of X by default even if v1.0.2 is the latest version of X. That is a difference with many other package managers that can default to using the latest v1.0.2 of X (even if v1.0.2 was
52.
▲
by
typical182
5y ago
FWIW, that's not what Go does. In your scenario, a Go binary ends up with a single copy of library X -- the 1.0.1 version. That's because library A is stating "I require at least v1.0.0 of X", and library B is stating &q
53.
▲
by
typical182
5y ago
FWIW, there are two machine-formatted sections of go.mod -- the first for direct dependencies, the second section for indirect dependencies. (That's as of Go 1.17. Previously, that information was communicated via machine-generated com
54.
▲
by
typical182
5y ago
There are some subtleties here, but go.mod files are not lockfiles, including go.mod files don't follow a traditional constraint/lockfile split, which I think is part of the point in that snippet you quoted. Another way they diffe
55.
▲
by
typical182
5y ago
> tradeoffs against an alternative security model, where transitive dependencies are automatically updated to pick up security fixes. One thing to keep in mind is that Go doesn't stop you from updating. For example, its common to
56.
▲
by
typical182
5y ago
There is also a new set of FAQs on generics: https://go.dev/doc/faq#Type_Parameters
57.
▲
by
typical182
5y ago
I think they meant “type information is not available at parse time” (rather than “compile time”). There is a longer and more precise description of the problem as part of this FAQ of the generics proposal: https://go.googlesourc
58.
▲
by
typical182
5y ago
FWIW, the best intro to CUE I’ve found so far is: https://bitfieldconsulting.com/golang/cuelang-exciting …which does a nice job of starting from the problem, and building up from "how could we improve JSON for use
59.
▲
by
typical182
5y ago
This is a great list of influences on the design (from the article comments where the prototype author Sam Gross responded to someone wishing for more cross pollination across language communities): ————— "… but I'll give a few mo
60.
▲
by
typical182
5y ago
Very nice write up. Go’s focus on simplicity means that there is only a single parameter, SetGCPercent, which controls how much larger the heap is than the live objects within it . FWIW, there is a new proposal from a member of the core Go
More ›