cs-szazz

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.

(not a frontend dev, so excuse any ignorance)

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.

We're already using the new IR compiler on 1.4, but I'll check out 1.5!

11,503 files, 1,431,195 lines of code. (spread out over <50 Gradle modules).

I think the main problem is that Gradle doesn't have the same support as Java for ABI compatible changes, so invalidation of modules are more common.

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?

Unfortunately we heavily shard our tests, running on a single laptop would take a while.

Unfortunately right when we were trying to deploy a hot-fix to production, our CI can't clone the PR to run tests.

What do other folks use to avoid this situation? Have a Gitlab instance or similar that you can pull from instead for CI?

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.

+1, though sadly Ontario has cut their tax credit so it's just Federal for us now.