357
Java at 30: How a language designed for a failed gadget became a global powerhouse (www.zdnet.com)
submitted 1 year ago by to c/technology@lemmy.world
124 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 1 year ago (1 child)

Sure, and Kotlin is largely syntax sugar for Java. It's certainly nicer, but the semantics are largely the same.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 year ago (1 child)

    You must not write much Kotlin then? It’s far more than sugar when a language fixes core issues in another.

    It’s a modern, statically typed language that addresses many of Java’s longstanding limitations with robust type safety, expressive functional features, coroutine-based concurrency, and extensibility — all integrated natively. Interoperability with Java is a strength, not a sign of dependency.

    Calling Kotlin merely syntactic sugar is like saying Swift is just Objective-C with prettier syntax — it misses the deep improvements in language design, safety, and developer experience.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 year ago

    I've written a fair amount, enough to know it's a significant improvement on Java, but that it still suffers from the unnecessary abstraction in the standard library. And that's pretty much my main problem with Java.

    Swift is a different story because the main issue with Objective C is the syntax.

  • permalink
  • fedilink
  • source
  • parent