5 ms·

It is, but the problem with that is that they're doing it in JavaScript. Kotlin could offer better performance and certainly offers strong type safety througho

• hasenj 10y ago
  Have you tried TypeScript?
  • deno 10y ago
    Typescript is nice but its type system is not the strongest selling point. For example this compiles without warnings: const foo: Promise<string|null> = Promise.resolve(null); const bar: Promise<string> = foo; bar.then((value) => value.toString()); // runtime null error
    • coldtea 10y ago
      That's because null is an acceptable value for a string object. Which is the same thing as in Java and plenty of other languages.
      • deleted 10y ago
        [deleted]
      • ptx 10y ago
        Not in Kotlin, though. You have to make it explicitly nullable if you want it to be null.
        • hasenj 10y ago
          You can enable strict null checking.
      • deno 10y ago
        You can replace string|null with string|number in this example.
  • mathw 10y ago
    A bit. It's an improvement, but if you're writing Kotlin on the backend then Kotlin/JS starts to look tempting on the basis that it's the same language everywhere. Although using the same language in different environments obviously feels a bit different.