HNHacker News
TopNewBestAskShowJobs

xh-dude

107 karma · joined December 18, 2019

submissionscomments
xh-dude··on Golang vs. C# (.NET 5.0) at Benchmarks Game
It is, and it’s not directly tunable … the opinion is ‘we’re IO-bound, not compute-bound’.

I spent a chunk of time recently (10s of hours) doing dumb C# vs Go benchmarks - files and networking, and nothing worth taking seriously - just, usually the part about being IO-bound was true. C# is really impressive and was just a little slower with the best async solutions I could come up with. The machinery for async has overhead, so do Go routines and channels … the first-pass, not very performant code was just a little faster and IMHO clearer with Go (but I’m much better with Go /shrug).

xh-dude··on Error stack traces in Go with x/xerror
I’m not sure the mentality is exactly “oops, oh well, leave it broken forever” [0]; it is intentionally ponderous. As a stop-gap, linters [1] can get excellent insight from ASTs.

The stability of Go is something I value a lot, so I don’t mind stop-gaps like this too much on balance.

[0] https://github.com/golang/go/issues/20148

[1] https://github.com/golangci/golangci-lint

xh-dude··on Fighting Like Taliban
There is an argument that the ‘stay and tolerate the corruption for another generation’ strategy would eventually outlast native “Taliban” resistance - this is the path the U.S. was on, fairly explicitly since 2010 or so. In a realist framing, this is something that deserved more careful consideration before, and also now, in the aftermath.

Look at the outcomes for Karzai and Ghani as an indicator - I don’t know that ‘popular support’ is something to attribute to the Taliban but we ought to entertain the notion that the framing of Afghanistan for domestic consumption in the U.S. distorts a useful, realist analysis. How could we arrive at the current state of things if, outside of Kabul, the dynamics were as simple as painting a target on the Taliban?

xh-dude··on Generics enabled by default in Go tip
Fair point. Maybe there are contrived cases that can get nasty (an interface{}-typed variable boxing a function is possible, not so with any non-empty interface ), but in practice the pathology would be ‘panic’ more than ‘here are the keys to the exploit kingdom’, if this is what you were thinking.

I was thinking more about silence where someone expected a greater degree of compile-time type safety than they really had, or relatedly e.g. the subtleties in JSON encoding / decoding where there is silent data corruption that could fall through the cracks - mostly I feel like I avoid these things by not using interface{}; I certainly did not grasp that without some experience with the language.

xh-dude··on Generics enabled by default in Go tip
Parametric polymorphism is a better fit for container types IMHO. There are some interesting notes here…

In Go prior to generics, interface{} is an escape hatch less frequently needed but not necessarily much safer than void*. Post generics, interface{} is suddenly more useful and will be aliased by ‘any’.

The way the std lib heap works in Go, an implementation doesn’t have to mention interface{}. Using the Go std lib solution is about satisfying a few interfaces, defining some methods for sorting and swapping over the element type. The use of interface{} is internal.

Go’s generics solution is going to have type constraints, which I think will be very familiar to some and probably new to others … So, the Go generics PQ should still require some constraints on elements, not ’any’thing will work. I’ve really enjoyed constraints in languages and it’s not quite natural in C++/Java, but Go’s interfaces already do some ‘constraint’ work conceptually and can be used as constraints in Go’s generics syntax. I’m interested to see how this plays out.

xh-dude··on Interview with a ransomware group
I think it’s fair to assume that adding ethical gray is a well understood tactic in this world. And just that - a tactic.
xh-dude··on [dead]
McAfee’s story seems worth recording, and that story can’t be reduced to semiotic gestures without losing fidelity about the complications and contradictions in it.
xh-dude··on Asynchronous Everything (2015)
Like, I see ‘common event loop’ here and don’t OSs (and hardware) past a certain size generally provide interrupt handling, threading, memory management and so forth? These are all highly general mechanisms that have evolved to meet concurrent execution models… because of the generality, a lot of relevant things remain at a lower level of abstraction than languages often expose.

What I wonder about is what happens when we lift runtime policy decisions into the type system, in a way that allows something more performant - I think I have a sense of what this pans out like and I just am skeptical than for every case (for many, many cases, it seems like a great idea!) that this approach leads to the best implementation. It reframes a lot of the inherent difficulties, I’m not sure it helps abstract over them.

xh-dude··on Asynchronous Everything (2015)
There is a presumption of some runtime behaviors in the Go language spec that makes me wonder here … details can be lifted into the type system but if we’re trying to eliminate overhead, can we do this without revisiting a lot of the issues we were trying to solve with interesting concurrency primitives?
xh-dude··on Response from Greg Kroah-Hartman to University of Minnesota Researchers
Fair enough that Greg can’t know whether Aditya is playing a game. But when Greg says “You, and your group” - it’s surely not Greg’s responsibility to untangle the knot at this point. This comes after Aditya had the opportunity to recognize that Dr. Lu and UofM were on Greg’s radar. There was a window of opportunity for working out the details, having some situational awareness, detangling things. Instead, Aditya just hit back, in a personal and to my mind fairly repugnant way. I maintain he should have talked to Dr. Lu at this point because Dr. Lu could have sought a better resolution at this point. Everyone would be better off.

Yeah, Greg seemed angry in response - I think that’s understandable. Should Greg apologize? Sure, why not. But from the skid marks on the road, I’m pretty convinced about who was driving unsafely here.

xh-dude··on Response from Greg Kroah-Hartman to University of Minnesota Researchers
Dr. Lu’s research is asking dangerous, thoughtful questions. The answers are sort of unsurprising. It’s not ethical.

As I read the discussion archive carefully: 1) A submits patch 2) G suggests a particular patch was “wasting his time”, and that he’s suspicious of this kind of submission from Dr. Lu and UofM. 3) Nearly a day later, A accuses G of ‘wild accusations, bordering on slander’.

In fact, no one denies that what G claimed is in fact true - that Dr. Lu and his students had a history of submitting “hypocrite” patches. They published about it!

But according to A, it’s G that is being ‘unwelcoming’ and ‘intimidating’, due to ‘preconceived biases’. To me, this is where it starts feeling dramatically personal in nature.

4) I don’t see the language in G’s response to (3) as nearly so personal as (3) itself. It does question A’s professionalism. I’m sympathetic. What was A thinking?

xh-dude··on Response from Greg Kroah-Hartman to University of Minnesota Researchers
Aditya should’ve talked to his advisor before suggesting the gatekeepers were, gasp, gatekeeping
xh-dude··on Has UML died without anyone noticing?
Agreed ... the thing that bothers me about UML is that it has displaced better, smaller-bore tooling in a significant way. The idea of thinking-before-coding work is of course completely necessary.
xh-dude··on Green vs. Brown Programming Languages
I don’t know, of course, but I have a different sense of where Go will be if it survives generics. The lack of change will mean it’s reliable, it was never as pretty as some other things, and it doesn’t go too far out of its niche. A lot of languages that suffer past the honeymoon, it isn’t survival of the fittest, it’s just evolving bloat or ending up with vestigial organs - this is hard to get on board with for new developers.
xh-dude··on On navigating a large codebase
https://missing.csail.mit.edu/ is on point here.

I think there’s an argument that instructors’ time is better spent on other things, but, yeah, students should be exposed to this stuff somehow or other.

xh-dude··on Alex Trebek has died
I’ve heard the contrast described as the difference between amazement at how someone knows something versus how they don’t know something.
xh-dude··on The Accelerating Adoption of Julia
My experience with Julia is not deep, but I’ve found it’s really nice to iterate on something that floats towards something that flies in one ecosystem. It’s not harder than Python to get the working implementation up and going - really there is a lower volume of idiosyncrasies.
xh-dude··on Go’s Major Versioning Sucks – From a Fanboy
Then you don’t have breaking changes, though?
xh-dude··on A new theory about political polarization
There are plenty of thoroughly competent, talented, quantitatively oriented PoliSci researchers. Relative to other social sciences it can be less straightforward to be productive with quantitative methods ... there are cases where quant methods shine, the field needs more of it IMO, but the field can’t be reduced to that kind of scholarship alone.
← PreviousPage 3 of 3