107 karma · joined December 18, 2019
This approach is available/implemented in the standard library, the whole story with JSON in Go is includes a few different approaches but this is definitely anticipated.
I’m not sure we’re given clarity here - rhetorically, ok, fine, but the math doesn’t line up quite this way.
Magnus Carlsen would not be the first world champion to go to war with FIDE, and it’s surprising how recent stories don’t mention the surprising withdrawal-but-not-retirement of Carlsen from championship play here. Put together with the other puzzle pieces, ot feels like Magnus is trying to play a game that’s not on the board.
The last candidates tournaments and championship matches have IMHO been boring, over-prepared, extremely risk-averse, uninspiring stuff, and it’s not fun to watch Carlsen/Caruana/Nepo loaded like Atlas or Sysiphus. More enjoyable things happen in looser formats. So some disruption sounds good to me.
Nerding about the audio production, IIRC - Vig was using Dave Grohl’s drum tracks to trigger digital samples into reverb, mixing just the wet reverb in. Albini had a bunch of mics in weird places capturing room acoustics and mixed between them. Really different approaches and even if listeners don’t know, they hear it.
Cobain was such a tragic roman candle of talent, but I really think collaboration with producers was necessary to get albums as good as these. Somehow I suspect industry economics have changed in a way that I don’t think rewards elite producers assembling great albums, although digital tech lowers the cost and great sounding stuff still happens.
If UML tooling had just focused on diagrams, I would not revile UML.
Feels like there could be a lot of surprising inferences to think about here … just a few quick thoughts - how long does someone pause after a blunder, how does one react to unpredictable moves. Can definitely imagine AI being of significant utility here.
Chess computing is one area where there’s a lot of attention to hard details as well as the algorithms, lots of gems like this in the genre
It doesn’t similarly expose mutexes that package clients have to fiddle with.
For example: https://brief.bismarckanalysis.com/p/modern-russia-can-fight... has interesting and useful details but I think has been demonstrably and obviously short of similar analysis from experts in the field who are less certain but more reliable vis-a-vis outcomes.
The misery in situations where consensual decision-making isn’t the fact of the matter is IMHO tragically under-explored in this framing and in Alito’s opinion. Without respect to the legal and political status of Roe, I still think it was morally right where it limited government intrusion and authority.
Will you feel responsible for this kind of outcome when it occurs in America, as it has in the past and does in the world?
“Currently, attributes and macros/syntax extensions are both conceptually macros: they are user-definable syntactic extensions that transform token trees to token trees.”
FWIW I definitely admit the point about Go compiler directives sort of cheating into this space a bit - I see them used responsibly for the most part but it’s a valid point. (Go’s struct tags OTOH, are an escape hatch I revile…).
The baseline is that constraints aren’t best expressed as interface literals in situ. Unlike exceptional use of ‘interface{}’, ‘any’ will be a more naturally invoked constraint.
Also, some of the uses of constraints rely on a unification involving an ‘any’ term that cancels out. Here, the use of ‘interface{}’ is not incorrect but maybe indirect.
It feels like a lesser sin to use channels in clever ways to recreate mutexes or other patterns than the other way around. But it’s definitely true that they are juiced up to make tradeoffs that are morally wrong for some things.
The contract is always right … how well it is expressed through language mechanics is maybe another way to contrast things here. (FWIW I think Go could tighten up a few things - dropping or shadowing errors is a bit worrying - but I’m fairly convinced sum vs product is a little too harsh of a reduction; a useful distinction but not a complete one.)
IMHO there are convincing arguments that Go needs x, y, z (or: prefer another language if you need x, y, z). A good example of one of these that is being addressed would be priority queues. Doing them via interfaces was always possible - there’s a whole std lib package for them. Generics will be better. But looking at the pre-/post-generic ways of doing priority queues confirms and emphasizes, rather than negates, the utility of interfaces as a way of structuring code. It’s still opinionated and I think it’s fair to argue about alternatives but it’s absolutely not the case that some large class of reasonable problems was entirely ignored or forgotten.
I think it’s telling that Go, Rust, as well as more inspired stuff in later editions of C++/Java/C# all seem to be demonstrating that nominal inheritance-first polymorphism is not the only or always the best maze of abstraction for getting to a concrete dispatch from type A to type B in imperative-feeling languages.
I do think that what seems obviously true and categorical in the absence of concurrency is quite a bit more subtle when concurrent. It’s obvious when rewriting the kind of chains where ‘?’ makes perfect sense from sequential to concurrent invocation.
By no means do I think Go is perfect or can’t learn from Rust but I do think it’s important to consider the tradeoffs against Go’s colorless concurrency - it’s a very compelling affordance. Like garbage collection it’s easy to show the pros and cons in a codebase the size of a demonstration but at scale it’s a decision with pros and cons.
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 emphasis on making it really hard to walk away with misconceptions.