kmicklas

13 ms·

61.
by kmicklas 9y ago
> there is no foolproof way of implementing that pseudocode's "has_seen(message.id)" method Wait why? Just because you'd have to store the list of seen messages theoretically indefinitely?
62.
by kmicklas 9y ago
This is the final state of tech (until general AI). Fully-proven infrastructure, AI-powered user level features.
63.
by kmicklas 9y ago
Well I downvote racists and sexists on HN all the time. But I think people with good intentions should be free to discuss.
64.
by kmicklas 9y ago
Such logic will not convince such sexists, sadly.
65.
by kmicklas 9y ago
Was not aware of this. It seems like the downvote war already begun just for me asking this question...
66.
by kmicklas 9y ago
> but it really reads like they are playing with going the way of Github. What's the way of GitHub?
67.
by kmicklas 9y ago
That might already be the case. The problem is new (non-research) OSs aren't written that often...
68.
by kmicklas 9y ago
Use a big enough hash length that this is less likely than cosmic rays flipping your bits or something.
69.
by kmicklas 9y ago
The fact that the majority of infrastructure in tech is oblivious to something as obvious and beneficial as content-addressable storage is one of the most depressing things about the industry to me.
70.
by kmicklas 9y ago
I have no idea why you would think that. It's pretty standard usage of punctuation like (){}[] etc. If it's hard to read that's because the libraries and infrastructure for writing derivations is not simple or well-documented
71.
by kmicklas 9y ago
> probably the only gripe I would make is to have comma-separated lists instead of having to use parentheses to separate non-atomic expressions. Wait no separators are evil. This is the best thing about the syntax.
72.
by kmicklas 9y ago
It's more than anything because of Google's clout, and secondarily the general worse-is-better fetish in tech. Go actually just pushes all the complexity into the code you write with it, so I don't buy that that is the reason
73.
by kmicklas 9y ago
Replacing a 50s language which a 60s language! Amazing!
74.
by kmicklas 9y ago
In the general space of competition with Go, probably the various JVM languages (Java, Scala, Kotlin, etc.), Rust, Haskell, Nim, ML, etc.
75.
by kmicklas 9y ago
Of course you can find people using all manners of languages/systems in production. That doesn't mean they are well designed. And I don't think it's necessary for me to reiterate at this point why Go is poorly designed.
76.
by kmicklas 9y ago
Haskell is much more suited to production use than Go though. Better concurrency, more invariants checked at compile time, easier to refactor, etc.
77.
by kmicklas 9y ago
That's only if you're used to imperative languages. Of course even in functional land a slimmed down language like Scheme is probably better for teaching.
78.
by kmicklas 9y ago
Basically all these articles about Go make it sound like it was designed to be some kind of teaching language with a low conceptual barrier to entry, except Google intends it to be used in real settings, which is the problem.
79.
by kmicklas 9y ago
That's an implementation detail. Code written in these languages is generally trivially retargetable.
80.
by kmicklas 9y ago
The real answer here is, text is a bad data structure.
81.
by kmicklas 9y ago
> or UTF-16 Please no. UTF-16 needs to die a painful death.
82.
by kmicklas 9y ago
It's the Unix/text fetishizing developers who aren't the smart enough ones I think...
83.
by kmicklas 9y ago
True, if you lose your job and can't get on disability you're pretty screwed.
84.
by kmicklas 9y ago
> Why should a country not be permitted to prohibit you entry if you don't add value to said country? That's what sovereignty is all about. The problem is that capital flows more or less freely but labor does not.
85.
by kmicklas 9y ago
Wait, wtf? You're advocating for occupational licensing in tech?
86.
by kmicklas 9y ago
> It would be great if someone could get a high-paying job and not worry about being bankrupted by an unforeseen medical disaster, but that's not the case in the US. I agree with this sentiment but if you have a high-paying tech job
87.
by kmicklas 9y ago
Amazon employees should organize, strike, and get these non competes mass nulled.
88.
by kmicklas 9y ago
This is definitely true but I think that possibly as the big cloud players devote more and more of their revenue towards developing all kinds of (vendor lockin) APIs each of which does not concern the average user, rather than generic and r
89.
by kmicklas 9y ago
And most importantly, outside the Bay Area.
90.
by kmicklas 9y ago
As I said, signing such a contract doesn't make you a bootlicker. (I have signed such a contract myself.) But I can't for the life of me understand why people are feeling bad for working on side projects and not wanting to have th

More ›