4 ms·
It's cool man, not everything is for everyone. > Were people really record-scratching over his totally reasonable decision to take a good-paying job at a big c
by steveklabnik 8y ago
It's cool man, not everything is for everyone.
> Were people really record-scratching over his totally reasonable decision to take a good-paying job at a big company?
I actually anticipated a few people being confused because of a few reasons. It seems like, so far at least, nobody has actually been confused. It happens. But I've experienced a lot of that previously; so like, moving from "writing documentation" to "product manager" and "everything is MIT/Apache2.0 licensed" to "a closed source platform" can look like big changes from the outside.
And really, I have wanted to write this bit about edge compute for a while, this is just a good excuse to finally publish the piece. I've been talking to CloudFlare for a few months, and it felt slightly odd to write it before I told the world "hey I may have some bias here." Now that I've made my decision and that bias is clear, that helps further discussion.
- tptacek 8y agoYeah just to be clear, you're simply at the leading edge of a phenomenon that's been puzzling me for awhile, probably starting with that Yegge/Grab piece (after which, from what I can tell, he was never heard from again). Don't fade away!
- steveklabnik 8y ago:) <3 Oh, one last bit I missed: > Like: did you want to write this, or did Cloud Flare reallllllly want you to write this? I brought up to them that I wanted to write a post about joining, and asked if they wanted marketing to look it over or something. They said "no need, we'll be happy with whatever you write." I see it as a mutually beneficial thing, and always have, everywhere I've worked.
- foobarbazetc 8y agoAre you concerned at all how the Wireguard thing is playing out vs your desire to see this stuff open sourced?
- zackbloom 8y agoThe Cloudflare Wireguard implementation is open-sourced and BSD licensed, what would be the concern? https://github.com/cloudflare/boringtun https://github.com/cloudflare/boringtun
- tptacek 8y agoThat Jason asked Cloud Flare to contribute to an actual sanctioned Rust port of WireGuard --- important to Jason because the current userland implementation is Go, and thus not as fast as it could possibly be, which is a priority for Jason --- and they refused and built their own instead. Also, WireGuard-the-protocol is not a collaborative effort, and so Jason's presumably a bit concerned about a divergent fork this early in the process of getting WireGuard fielded. Particularly because Jason is just one dude working on this with a couple volunteers, and Cloud Flare is, well, yeah. It was a pretty weird move on Cloud Flare's part. I'm not saying it was "bad", just, weird.
- steveklabnik 8y agoI think it depends on which "Wireguard thing" you're talking about, there were several semi-controversies. If you mean "Warp doesn't support generic clients", I commented about that over on the Reddit thread: https://old.reddit.com/r/programming/comments/b9sznr/im_joining_cloudflare/ek6tp9w/?st=ju4db19o&sh=0bcb793e&context=4 https://old.reddit.com/r/programming/comments/b9sznr/im_join... If you mean "CloudFlare pursued BoringTon outside of the general WireGuard project", well, I don't have any real insight into the specifics of why that was chosen, but it seems extremely open source to me. As far as I know, BoringTon is just an implementation of a protocol. There's a ton of reasons to want to do things on your own rather than work on upstream. And if anything, for protocols, independent implementations can be a good thing, more than a bad thing. If you mean something else, well, I'm not sure, those are the only ones I can remember :p
- tptacek 8y agoWell, they took WireGuard, wrote a Rust implementation of it, refused to collaborate with Jason, who's been trying to get a Rust implementation of his protocol off the ground, then rolled it out as a proprietary offering that WireGuard itself is not allowed to connect to. This seems like the sort of analysis that would be pretty cut-and-dried among open source advocates (I'm not one of those, so I'm not saying it's cut-and-dried for me). Your previous rooting interest in this story would have been for Rust itself. And Rust itself would have been been best served by having it host the dominant sanctioned userland implementation of WireGuard, not merely as an implementation detail for a commercial offering that also treats WireGuard as yet another implementation detail. Rust? Important! WireGuard? Important! Warp? Who gives a fuck? So this is a bit of a surprising response to see from you. Apologies for the late edit: I should lay my own cards on the table here. First, it's not much of a secret that I'm no fan of big Flare. But just to be clear: good friends of mine have worked there, and several other people I deeply respect have as well, and I don't judge any of them for that. Much more importantly: Jason Donenfeld is, to my mind, the hardest working person in show business, and he's set himself on one of the most important projects in network security, basically all on his own, and the momentum he's managed to achieve doing that is insane and a little inspiring --- especially given the amount of shade he's been repaid with by network security luminaries --- and basically the last thing in the world he needs is to burn cycles worrying what some giant corporation is doing with his work (which, sure, does not include this Rust implementation, but very obviously does include all the hard protocol design and validation work he's been doing over the last several years, which, if it were easy and straightforward to do, several people would have done before him). I've done about as much serious technical work on WireGuard as you have --- to wit: none, though I am a loyal, diligent distributor of WireGuard stickers. My partners all feel the same way, so we've just been sending the project cash. If your employer has done the same, and dumped a giant bucket of cash on Jason in exchange for having gotten so much mileage out of his work, that would be an excellent rejoinder to this particular set of concerns. Eagerly, therefore, awaiting my comeuppance on this thread! :)
- rpdillon 8y agoFWIW, I love posts like this. They combine tech, a dash of prognostication, an overview about career trajectory and how you think about it, and a bit about the space you're entering and how you see the competition. It's a fun read, and I appreciate you taking the time to pen it!