Most of the popular sport leagues don't have any rules disallowing female competitors. I'm sure the NHL, NBA, NFL, MLS, MLB, Premier League etc. would love to have a female player that was good enough because it would be a marketing dream.
117 karma · joined January 17, 2021
Most of the popular sport leagues don't have any rules disallowing female competitors. I'm sure the NHL, NBA, NFL, MLS, MLB, Premier League etc. would love to have a female player that was good enough because it would be a marketing dream.
Even if I accept that these quotes are an accurate portrayal of events that happened, I'd expect you to have more damning evidence to support canceling someone that has been extremely important in this industry for over 50 years.
I vehemently disagree. In my experience, a very substantial number of them fear the mob because there's so much at stake and nobody is interested in falling on their sword. Many people want to talk politics and philosophy and those subjects are often hard to avoid unless conversation is heavily restricted. I've had tons of conversations about algorithms that naturally turn into discussions of political and philosophical ramifications. A substantial amount of the screening that goes into accessing private communities revolves directly around likelihood of charitable interpretation, secrecy and behaviour on public social networks.
The second one, which I only use occasionally, is a private Android/iOS app that is very similar to Signal group chats.
I've heard of quite a few others but I don't have first hand experience with them.
Do you honestly think the situation improves if the discussion is censored here? Whether you like it or not these industry discussions, and much worse, are happening elsewhere and censoring relatively timid discussions like this only makes matters worse. There are 490 comments at the time of this post and I'd bet the vast majority of them are relatively benign.
> Wasn't most "legitimate discussion" already happening in private already?
Probably, but I think there was still much more interesting discussion going on publicly in years past. It's anecdotal but I've definitely seen a huge spike in how many of my colleagues are retreating entirely to private communities and most of them never make public comments anymore. That's disappointing to me because I think there's a lot of value in having these discussions in the open with respected and accomplished names attached. It also gives a level of perceived accessibility that I think is important.
When I was younger I learned so much and established many valuable relationships by having discussions on public services/websites. Many legends in the field were quite accessible on public sites and mailing lists. My life would be much worse if I hadn't had those experiences and it feels like a lot of younger people that don't have connections to the SV bubble are now going to miss out on similar experiences.
This isn't to say that we should be tolerant of everything but it definitely feels like we've swung too far in the opposite direction.
type SubsetFoo = Extract<Foo, { kind: 'B' | 'C' }>;They try to paint an extremely rosy picture of the current situation when the reality is that it's a very long way from the experience you get in Rust, Go, D, C, C++, Haskell, Ocaml or any of the languages where AOT is considered the default.
I actually like Java and the JVM but if AOT compilation and efficient memory usage is what you want Java is definitely not the language to use.
Part of the problem is that those also happen to be the frameworks that the vast majority of the community uses.
The Java zealots also tend to ignore all of the problems associated with AOT Java compilers and the fact that it will most likely be a few years before value objects are finalized and in a released version of Java. Even then, a ton of Java developers won't be able to use any features beyond Java 8 or 11 since a lot of companies don't want to give up the ability to easily use their libraries on Android.
Intellij's performance has never been good but it has continuously gotten worse over the years and it's bad enough now where I'll probably just cancel my subscription when it comes up for renewal.
The "boring, but necessary pieces" are usually just a call to a constructor. In my opinion it's almost never worth using a DI system that obfuscates dependency resolution and usually can't be checked at compile time just to avoid that.
> I know people will complain about speed of execution of language and framework but do you really care if you are not expecting Google like traffic.
If you don't care that's fine, but there are lots of us that do. This is subjective, but I find the memory use and overall performance of Rails/Django/Spring Boot applications to be completely unacceptable and there are far too many breaking changes.