3 ms·
> the root cause of my decision to leave the core team is a toxic environment in the meetings themselves. The catalyst was a specific meeting last summer: after
by loeg 5y ago
> the root cause of my decision to leave the core team is a toxic environment in the meetings themselves. The catalyst was a specific meeting last summer: after being insulted and yelled at over WebEx (not for the first time, and not just one core team member), I decided to take a break. I was able to get leadership to eventually discuss the situation with me last Fall, but after avoiding dealing with it, they made excuses, and made it clear they weren't planning to do anything about it. As such, I decided not to return.
Oof. Yeah, that’s relatable. It’s hard to continue contributing volunteer efforts to projects you care about when you’re getting shouted at all the time.
- programmarchy 5y agoIt's very disappointing that such a talented person was pushed out, especially someone like Chris who seems to be a genuinely good person. It's all too common to see brilliant founder types be pushed out by power- and influence-grubbers who end up ruining the original spirit of the project. I read through one of the threads he linked that was producing "more heat than light" [1] and, yeah, it's easy to see why he'd move on. The person responding to Chris wasn't adding any value to the discussion, just being a pedantic troll. What's worse is that person was a moderator. [1] https://forums.swift.org/t/if-let-shorthand/54230/188 https://forums.swift.org/t/if-let-shorthand/54230/188
- deleted 5y ago[deleted]
- microtherion 5y agoReading this thread for the first time, it looks to me like (1) everybody is fairly well behaved by the standards of an online forum and (2) Chris is probably using more inflammatory language than anybody else. So maybe one the problems is that at this point, he's no longer getting the deference from other community members that he feels he's still owed?
- gregoriol 5y agoSwift was never about volunteering: it's an Apple product, even if they tried to market it as open, it's Apple that manages the roadmap, with the usual secrecy, ...
- loeg 5y agoLattner was volunteering: > For context, I left Apple over five years ago and the only constant in my life is that I'm always "very busy" :smile:. That said, Swift is important to me, so I've been happy to spend a significant amount of time to help improve and steer it. This included the ~weekly core team meetings (initially in person, then over WebEx), but also many hours reading and responding to Swift Evolution, and personally driving/writing/iterating many Evolution Proposals 19. As such, my decision to leave the core team last summer wasn't easy.
- echelon 5y agoFork it! Call it Bird or Goose or something. Pull out SwiftUI and keep it simple. Focus on the server market more.
- shtopointo 5y agoThat would actually be an interesting direction. Swift would be an amazing server side language.
- zozbot234 5y agoObligate ARC is not a good fit for server software. Even obligate tracing GC ala Go and all the JVM/CLR languages gives you better throughput than that, though obviously doing neither is best.
- skohan 5y agoI think Swift could work very well in a lambda/serverless context. In that case, you'd be writing mostly functional Swift code with sparing use of reference types, which would mean you wouldn't hit ARC at all and you'd have static memory management similar to Rust. That, along with Swift's expressiveness, ADT's and awesome type system in general would make it a great experience. Kind of like the ergonomics of Python with an actual good compiler eliminating obvious mistakes like Rust.