> > > In Scala at least, I'm finding almost the entire community still think of > themselves as Java programmers. Java nowadays is first and foremost a > platform, and you're still programming against Java even if you're not not > using Java-the-language. > > Fair enough, but you aren't really programming against Java (the API) either though are you? You constantly live in this shadow world (not unlike Java arrays vs. generics, C const vs. non-const etc.).
> What Java *isn't* about here is default mutable collections, and use-site > variance, and get/set property accessors, and lambdas being delayed at the > same time as you gain the ability to put underscores in numbers, or any of > the other delays and setbacks that cause a project like Lombok to even be > needed in the first place! > > However, the JVM and bytecode is so heavily tied to Java that it seems like an uphill battle, which is what Lombok is now hitting. The bytecode is still OO (new, invokeinterface, invokevirtual), with operators required to having been assigned a type (iadd vs. fadd) etc. Considering how many of the later advanced features of Java (the language) relies on hacks and workarounds (inner classes, generics by erasure, reference equality) and how we are now getting silly unsigned int arithmetic utilities in JDK8 rather than simply a new unsigned byte, I can only imagine what goes on underneath with Clojure, Scala etc. when implementing i.e. "yield" efficiently. -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/cIH-KCNQQjsJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
