Developer tools live in their own space. And I assume most devs don't really care that "Copilot" started to show up everywhere, especially in MS365 products. At least I don't. Conversely, do non-technical people care where the term comes from, and now means "LLM integration" in a bunch of MS products?

I think it's better that Google going through Bard, Gemini, IDX, Firebase Studio, Antigravity, ...

I assume the server side usage is not zero, but not enough to reach a critical mass, you're probably right there.

But I don't know why I'd pick Swift on the server when Rust is better in almost every dimension, with a thriving and more community-driven ecosystem.

Spring was ready on day 1, as virtual threads had been an experimental feature since Java 19. Spring Boot added support within a couple months.

> In my experience, most companies using Java are chronically multiple versions behind (e.g. some of my friends still in the Java world are on 11).

And that's on you.

There's also the upcoming Metals v2 that's using another compiler frontend optimized for performance, Google Turbine: https://metals-lsp.org

Actionable diagnostics for Java aren't implemented yet though.

For instance the Android runtime has chronically lagged behind mainline JVM bytecode versions, iirc once Scala started to emit Java 8 bytecode, Android was stuck on Java 6.

Kotlin had other obvious advantages on Android like its thin standard library or the inlining of higher-order functions.

It's not really true anymore, Kotlin has slowly absorbed most of the same features and ideas even though they're sometimes pretty half-baked, and it's even less principled than the current Scala ecosystem. JetBrains also wants to make Kotlin target every platform under the sun.

At this point, the only notable difference are HKTs and Scala's metaprogramming abilities. Kotlin stuck to a compiler plugin exposing a standard interface (kotlinx.serialization) for compile-time codegen. Scala can do things like deriving an HTTP client from an OpenAPI specification on the fly, by the LSP backend.

The functionality used to be really barebones outside of Samsung DeX. Now it's a bit better since it's officially supported by Google.

Some things are actually worse on the iOS side. It took years for Apple to catch up with spam and scam calls/SMS detection.

Plain Google search is still the main vector of scams, I eventually set up NextDNS on her devices.

Does it make sense compared to C#, Go, Rust or a JVM language? I don't know, but it's there, and Apple put some resources behind the initiative.

But in the end I can't help but feel Swift has become an absolute beast of a multi-paradigm language with even worse compile times than Rust or C++ for dubious ergonomics gains.

Once Wero becomes usable in Austria, France, Germany, Benelux, and interoperable with those, the few remaining players will have a strong incentive to join.

On the other hand, there's a significant chunk of the population that just pays using their mobile phone. They don't care about cards, numbers (which are going to disappear anyway), or the legacy infrastructure behind that.