You’re welcome. But I must tell you, at work I asked how my answers are, keep me honest. So a coworker looked at this thread and was just like, “dude just get to the point, no one wants to read all that.” And then explained that in huge detail.
That’s just how I talk. With all the writing I’ve had to do lately - documentation, blog, announcements - it’s been a constant struggle forcing myself to say fewer words, keep it short, keep the eyeballs, come onnnnnnn, edit edit edit!!! And that’s good… it’s how it should be. It’s just totally unnatural to me personally… hehe.
FINALLY there’s a chance to simply talk about it to some humans, so I uh… maybe went a little wild with the verbosity.
Actually, I'm happy you spent all those words, and I read them all.
I've been looking for an SHM IPC for a very long time and not finding one. It's nice to know that I'm not the only idiot thinking along these lines.
In addition, it's also nice to know that this was hard. I have taken several stabs at doing this, and I always bounced off thinking "It can't be this difficult. I'm screwing up." Seeing that smart people working for a real company had to do major surgery on something like jemalloc is a bit of a validation.
Can't say I'm happy to see this in C++, but I'll take what I can get. :)
Thanks to all the folks who wrote it. And thank you for the long winded explanations otherwise I probably would have ignored it.
2. I too would like to explore other developments - not that I think C++ sucks or anything (not that I don’t think it doesn’t suck sometimes!) - Rust and all. Here’s hoping
3. At points during development of this, the ol’ impostor syndrome would kick in. “Surely someone would’ve done this already.” Or more often, “Meh, people will just roll their own version of this, it’s not that hard.” But then I’d actually go through the exercise of implementing whatever it was - and think to myself, “that WAS NOT obvious.” It dawned on me that by doing it, I proved (to myself at least) that it’s not easy to do it, and thus perhaps worth having started.
Thank you so much for posting everything that you did. Long-form details are hard to find. In my truest contribution, I suggest you're a pleasure to work with. Rarely have I seen anyone willing to give the deep-digest of their determination and problems with a function. Consider writing more!
EDIT
I didn't see the other posts about brevity. Fuck that. Details matter and so does the human experience. Who hasn't on this site been the unfortunate recipient of trying to get some brilliant but shitty function to work?
That’s just how I talk. With all the writing I’ve had to do lately - documentation, blog, announcements - it’s been a constant struggle forcing myself to say fewer words, keep it short, keep the eyeballs, come onnnnnnn, edit edit edit!!! And that’s good… it’s how it should be. It’s just totally unnatural to me personally… hehe.
FINALLY there’s a chance to simply talk about it to some humans, so I uh… maybe went a little wild with the verbosity.