That's fair, though I will say Kotlin's type system having nullability built-in is something I doubt Java will ever fully add (instead of the annotations it currently uses). So in that respect, it's making it more type safe, but the delta between Kt and Java isn't near as big as TS and JS.
I agree CoffeeScript usage has gone down dramatically, but has Typescript not usurped it? It doesn't seem like everyone just went back to using JS, so maybe Scala was CoffeeScript, and Kotlin is closer to Typescript?
As soon as I opened the page, I searched for "null" and saw it didn't show up in the original post. Leaving that out is almost a bad faith argument, because it is the number 1 Kotlin feature I doubt Java will ever get.
Now, I will say that build times are way better on Java. A large part of this is the ability to generate ABI jars with Gradle, which you can't do with Kotlin. If anyone from Gradle or Jetbrains are reading this, please please please try and make this work, I know there's ongoing tickets but in larger projects Kotlin and Java are not even close, for this specific reason.
I used Kotlin in a large codebase, and one of my only complaints is the compile times. We use Gradle for our build system, and relative to Java it is slooowwww. But we like the other benefits of Kotlin, so it's worth it in the end. But if they could get compile times down, it'd be the perfect language imo.
Are there other companies where a CX Specialist makes the same as an engineer? Usually I see Engineering offset from CX, so an entry level CX employee might come in at Level 1, while an engineer might come in at Level 3. I don't think I've ever seen an Engineer and CX Specialist have the same corporate level, but perhaps that's just the companies I've worked at?
If I understand correctly, the .so TLD is effectively a national resource of Somalia, and as such they have total control over it and could in fact shut it down if they wanted.
> It is an uncommon status that is usually enacted during legal disputes, non-payment, or when your domain is subject to deletion.
Serious question, if this is an extended legal dispute or the domain is actually subject to deletion, that would be hugely damaging to the Notion brand right?
I ask because I can't think of another company that's had a similar issue lately, so I find the domain dispute an interesting issue that we rarely see get to this stage.
This question gets more complicated in places like Ontario, Canada, where the term "engineer" is actually protected. To call yourself an engineer in a professional setting, you have to be a member of the Ontario Society of Professional Engineers. Of course in practice, they choose not to go after people who call themselves engineer vs developer, but perhaps that will change in the future.
I think the "overcompensating" can also happen when you hire, doesn't have to be an existing employee. Invariably other employees will find out what new hires make, and if you don't stick to loose compensation bands, you're going to have a tough time trying to justify this.
That doesn't mean much unless the employees have liquidity right? Presumably after the acquisition the employees would've been able to convert their options to cold hard cash.
Yeah definitely, but Amazon can always say "Go host on GCP". Then Google Cloud can say "Go host on Azure". Then Microsoft says "Go host on Digital Ocean", and repeat until you run out of hosts.
Is it like a game of hot potato where the last hosting company has to host them? Because it seems there are alternatives to each individually, and it's only when they all say no that there are issues for Parler. And to me that feels like a Parler problem, not an AWS problem.
In your example it's probably slightly different because religion is a protected class, while political leanings aren't.
I think what's particularly interesting is you substitute "right wing" with "Jews" like you did, and you start to wonder if Amazon crossed the line. But then change "Jew" to "terrorist", and you think Amazon might be in the right. Clearly we can't protect ALL groups, that'd be silly.
Serious question, it seems AWS is by no means a monopoly on web hosting (Google, Azure, Digital Ocean, Linode, the list goes on). It seems to be they're well within their rights as a company to not host Parler, and Parler can try to go somewhere else. If no other companies want to host Parler, isn't that more a reflection of Parler than the hosting companies? It doesn't seem like they should be obligated to host, since that's as slippery a slope as not hosting is. Perhaps this is a decision where not everyone will ever be happy, and that's just how it's going to be?