Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
xh-dude
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
xh-dude
4y ago
Women’s chess will be fine in any case. FIDE will take a hit.
32.
▲
by
xh-dude
4y ago
Use of Go’s runtime reflection to produce a struct definition would result in one instance of the key string, many instances of the numeric value This approach is available/implemented in the standard library, the whole story with JSON
33.
▲
by
xh-dude
4y ago
I don’t like this example in particular because observing too much “restore” activity is an excellent piece of information.
34.
▲
by
xh-dude
4y ago
Totally agree. Telemetry has been around and matured and benefits users. I’m not sure the benefits for Go would be as significant as other software but, really, why not?
35.
▲
by
xh-dude
4y ago
The next stat line says “4,764 workers were killed on the job in the United States.” in 2020. I’m not sure we’re given clarity here - rhetorically, ok, fine, but the math doesn’t line up quite this way.
36.
▲
by
xh-dude
4y ago
I think it excludes exceptions: exceptions are a side effect
37.
▲
by
xh-dude
4y ago
An undercurrent here is how FIDE, steeped and mired in tradition, shepherds the sport alongside technological disruption, both in how the game is played and how it is enjoyed. Magnus Carlsen would not be the first world champion to go to wa
38.
▲
by
xh-dude
4y ago
+1 about Butch Vig, an incredible producer. Steve Albini, also incredible, did In Utero in a much different way. I get why Cobain would’ve liked the latter, I think Vig’s albums were all amazing though. Nerding about the audio production, I
39.
▲
by
xh-dude
4y ago
Oh, mermaid looks nice! I hadn’t seen it before. Thanks for mentioning it. If UML tooling had just focused on diagrams, I would not revile UML.
40.
▲
by
xh-dude
4y ago
Definitely, random time is adding no correlation where it would count. Move time is an easily captured psychometric observation, the clever bit is that it’s intermingled with automated chess analysis. Feels like there could be a lot of surp
41.
▲
by
xh-dude
4y ago
This is pretty tremendous: https://codegolf.stackexchange.com/questions/19397/smallest-... Chess computing is one area where there’s a lot of attention to hard details as well as the algorithms, lots of gems like
42.
▲
by
xh-dude
4y ago
Hmm, the std lib uses channels for a variety of scheduling hook sorts of things - contexts, timers, os signals for example. That’s maybe just a little narrower than how Go users can use them - they aren’t really for transport, but for synch
43.
▲
by
xh-dude
4y ago
My impression of Burja is that he’s better at the writing - there are always interesting details - than average but not generally a superior analyst. For example: https://brief.bismarckanalysis.com/p/modern-russia-can-f
44.
▲
by
xh-dude
4y ago
> I think that women who have sex and conceive children should be held responsible for raising those children. The misery in situations where consensual decision-making isn’t the fact of the matter is IMHO tragically under-explored in t
45.
▲
by
xh-dude
4y ago
Maybe there’s a counterfactual timeline where Apple didn’t nuke Flash on phones, hmm… interesting to think about. I think I’m happier with apps rather than apps-in-the-browser in the end, and this might be a similar contrast - it’s technic
46.
▲
by
xh-dude
5y ago
In the sense of - where Rust can do some amazing program transformations because it’s quite demanding about memory safety, ATL purports that if the math is all tensors, then there’s potential in program transformations based on automated re
47.
▲
by
xh-dude
5y ago
Is the situation for Rust different than as described here: https://github.com/rust-lang/rfcs/pull/208 “Currently, attributes and macros/syntax extensions are both conceptually macros: they are user-defi
48.
▲
by
xh-dude
5y ago
Yeah - the tradeoff isn’t about the benefits in places where macros would solve problems, but the problem of having macros. It’s an opinion.
49.
▲
by
xh-dude
5y ago
It seems significant (major? I dunno) that Go doesn’t have inheritance or subclassing or co-/contra-variance.
50.
▲
by
xh-dude
5y ago
My hunch is that Go packages will still work fairly well for isolating gory details. The guts of a package can get more complicated with generics but there is friction for consuming anything more clever than, like, ‘lists.NewLinkedList[myTy
51.
▲
by
xh-dude
5y ago
OTOH there’s no ‘while true’ or do-while or while-do, none of which are particularly fluent.
52.
▲
by
xh-dude
5y ago
I don’t think the concern is unreasonable at all but ‘any’ feels pretty solid as far as I’ve had the chance to poke around. There’s some tensions where I think ‘any’ is arguably much simpler: The baseline is that constraints aren’t best exp
53.
▲
by
xh-dude
5y ago
A subtlety I’m ok with here … channels are a a language primitive but, in terms of runtime, an opinionated composition of data and concurrency semantics; the opinions give the runtime some privilege to do some nice things without a lot of e
54.
▲
by
xh-dude
5y ago
A reduced version of this is maybe where Go and Rust have a pretty similar contract for things that “Read” and lean hard into permitting partial success. Both allow for some relatively sharp edge cases with zero-sized reads. The contract is
55.
▲
by
xh-dude
5y ago
I feel like an object lesson here would be context.Context in Go, which sort of rhymes with Result types in a way … I figure this sort of programming in Go post-generics won’t emerge as uniform baseline but thematic variations will arise in
56.
▲
by
xh-dude
5y ago
I really think Go’s opinion here arises from a sense that some abstractions of control flow just should be verboten for concurrency. For example exceptions dumping a stack trace in a concurrent program is often OK and occasionally extremely
57.
▲
by
xh-dude
5y ago
What frustrates me a bit about this argument is that interfaces really do offer a tool to solve problems around dispatch and polymorphism. Like a lot of things in Go there are lots of opinions and tradeoffs that can’t or can’t easily be rev
58.
▲
by
xh-dude
5y ago
Because passing messages still means dispatch on concrete types - something concrete sends a message, something concrete receives a message. That’s the whole ballgame - get one concrete type to talk to another. Even if ‘concrete’ is in a se
59.
▲
by
xh-dude
5y ago
There is no categorical presumption in Go that an error invalidates what would be boxed in a Result or Option. I do think that what seems obviously true and categorical in the absence of concurrency is quite a bit more subtle when concurren
60.
▲
by
xh-dude
5y ago
net/http is a great example. The std lib is disciplined about using safe Go ideas except in the exceptional cases. I feel like it’s nothing that is enforced by the formal spec of the language, just that the std lib has an exceptional e
More ›