Conversation

That's not what happened. Now, here is where I'm going to call you out as someone being incredibly dishonest. You're pushing false narratives. If people don't like being called out for doing this, they should stop doing it.

Quote Tweet

Marsh Ray

#BLM

@marshray

Aug 22, 2019

Replying to @marshray and @DanielMicay

And seeing someone flip out and claim they’re being personally attacked the first time someone says “well I don’t see that your proposal brings all the benefits you claim in our usage” is a big red flag.

1:59 AM · Aug 22, 2019Twitter Web App

Replying to

I'm not flipping out, I'm not the one claiming there were personal attacks and that's clearly not what happened. Someone wrote an incredibly misleading and inaccurate summary / comparison of my work without actually bothering to look into it and I responded to that countering it.

Quote Tweet

Replying to @DanielMicay @AzureCrimsonE and @damienmiller

i.e. why compare specifically to jemalloc and not everything else? I have some comparisons about the philosophy / approach to OpenBSD malloc because it's the closest cousin of it and is the most direct inspiration for it. It just stopped being a viable platform for what I wanted.

Quote Tweet

Replying to @DanielMicay @AzureCrimsonE and @damienmiller

I don't portray design choices in hardened_malloc as being more valid or better but rather I explain why it takes the approach that it does based on the goals and compromises. The jemalloc design isn't any less modern and it's not badly implemented. It's just not the same thing.

Quote Tweet

Replying to @DanielMicay @AzureCrimsonE and @damienmiller

It very aggressively uses address space and it explicitly makes performance sacrifices as part of the design for security. I'm not on that thread telling them that they should use it. I simply don't want it portrayed unfairly/inaccurately and dismissed as something near useless.