HNHacker News
TopNewBestAskShowJobs

dmkolobov

444 karma · joined October 13, 2013

submissionscomments
dmkolobov··on Thousands are monitoring police scanners during the George Floyd protests
Completely outside of my area of expertise, so this may be a silly question, but are police transmissions distinguishable from others in their encrypted form? If so, there could still be a use case for knowing _where_ the cops are. Wonder if some sort of mesh could be used to triangulate the positions of these signals.
dmkolobov··on Twitter hides Donald Trump tweet for “glorifying violence”
There's a difference between "editorializing" and "omitting". They're not changing the hate speech, they're just not showing it.
dmkolobov··on I Don't Use Classes
It's a product type[0], containing a single inner type of `u32`. Sometimes classes look like product types.

[0] https://en.wikipedia.org/wiki/Product_type

dmkolobov··on Show HN: A Simple GPU Hash Table
Even so, GPU-based hash tables are useful in that they can be used to speed up various kinds of simulations for video games and animation:

https://wickedengine.net/2018/05/21/scalabe-gpu-fluid-simula...

https://developer.nvidia.com/gpugems/gpugems3/part-i-geometr...

dmkolobov··on Typestates in Rust (2018)
It does! But you still have to actually "use" it, meaning that it appears as a field in the definition, and you have pass a PhantomData value whenever you create new instances of your data type.

In Haskell, you can omit these fields entirely, and achieve the same thing just by annotating the function.

For example, in Haskell, we can have

  data Const a b = Const a
whereas in Rust, it would be:

  struct Const<A, B> {
      konst: A, 
      // does not exist at run-time
      discard: PhantomData<B>
  }
dmkolobov··on Typestates in Rust (2018)
This is one of my favorite patterns from Haskell, which I've known as "type-level programming". One of the most common examples is a "sized vector"[1] which allows compile-time bounds checking. This is achieved by annotating each vector type with a phantom type variable representing its size.

Nice to see something like this in Rust! One thing that's a bit of a bummer, and I'm sure there are very good reasons for this, is that we HAVE to use every type argument of struct in its definition. If this restriction were to be relaxed, we wouldn't need the "state" field in the struct at all, and we could make the state type variable truly "phantom".

[1] https://www.schoolofhaskell.com/user/konn/prove-your-haskell...

EDIT: Typos.

dmkolobov··on Low Level Bit Hacks You Absolutely Must Know
always been fond of `even x = x == ((x >> 1) << 1)`
dmkolobov··on On GNU and on hackers
Or just about any time cops gun down an unarmed person of color.
dmkolobov··on On GNU and on hackers
I think generalized induction about "contept X" is the wrong tactic here, even though the formalization is for the sake of clarity. The specifics of this case matter. The thing is that "context X", in this case, refers to "rape culture", which at its core is a name for institutionalized systems which support and allow rape to occur. Allowing trivializations of such a term is completely out of line for a community that claims to support inclusivity and diverrsity. I understand that in this way many trivializations of many different "concepts x" could be argued to be not ok. When "concept x" refers to oppressed groups speaking abut the issues that affect them, especially if the issues are ones so violent and brutal as rape, I think this is good. Such things should not be trivialized.

Organizations setting limits on what type of discussion is allowed is a good thing, and again, specifics matter. The statement, at its heart, stifles the speech of these groups by trivializing the concerns of those people who are affected by the systems termed "rape culture"( systems supporting violence against certain groups ). The fact that the transition to a more inclusive community involves prohibiting this type of speech is a given IMO, since that speech is precisely what makes for a hostile climate to non-white-guy contributors. Such statements are problematic if the community in question claims to be based on freedom and inclusivity.

[Edit]: In general, I think "freedom of speech"( and the implied "freedom to be offended" ), are less important than maintaining a community climate that feels safe for its members.

dmkolobov··on On GNU and on hackers
The authors opinion about the misogyny of the speaker's trivialization does not carry nearly the amount of weight as legal prohibitions on hate speech. I do not think it's valid to dismiss a community's right to enforce a code of conduct to protect its members within its bounds. Maybe it's my own opinions, but ideally that is how positive social change is implemented. I do not think trivialization of concerns about hate speech would fly in most liberally minded circles either. If you are defending nuanced discussion about the value of rape culture, then I think there are better examples of nuance than this joke.

I think a lot of good would come if we stopped using the word "censorship", and just responded to what people actually had concerns with. Censorship is distinct from a dude stating his opinions, and encouraging others to agree with him.

(Edit): * defending nuanced discussion about the value of rape culture as a concept

dmkolobov··on On GNU and on hackers
The joke seems like a response to the efforts to implement the anti-harassment policy in question. In that context, this joke is, as others have stated, about trivializing concerns with rape culture in tech( valid concerns IMO ) . That sucks, even when you ignore the question of whether this is a real rape joke or not.
← PreviousPage 5 of 5