Lack of Tail Call Optimization is still a bummer in some cases.
JDK 8 Release Notes
191–200 of 314 posts
Re: JDK 8 Release Notes
#192I'm very happy with the JVM in general, but I really, really, really wish they fixed the start up time. People compile Clojure down to Javascript for command line tools precisely because of this. lein takes annoyingly long, so I don't do it. I realize this is not a real concern for them for e.g. servers, but I wish they had some developer- or desktop-specific configuration that would start about as fast as a Python V…
Can you please give a use case of a program that a few hundred ms delay during startup would be an issue?
ls
Re: JDK 8 Release Notes
#193Does anybody know if static libraries made it in?
Re: JDK 8 Release Notes
#194Earlier quoted context omitted.
No, actually, Java is a really bad language. It has a very complicated type system, but doesn't even allow you to express things like function composition or generic sums at the language level. Its syntax is stunningly verbose (e.g., no map literals; only now adding lambda literals; no type synonyms; no operator overloading). There is no macro system or method_missing or any other way of really extending the language…
Java is not a bad language. It was written as a reaction to C++ - a simpler, more consistent systems programming language. In that regard it has been wildly successful. It doesn't really look like a dynamically typed scripting language because it was never trying to be one. You pick a bunch of language flavour / syntactic sugar and say that Java is bad because it doesn't have those. Personally I like it because it do…
This. I realize the perl people love to have twenty different ways to do everything, but when I'm trying to get maintainable code out of an average team of programmers I don't mind the verbosity and I don't mind the lack of cryptic language features.
The original java architects took operator overloading and the macro preprocessor out for a reason - you can end up with orders-of-magnitude more ugly code if those features are abused.
Re: JDK 8 Release Notes
#195Earlier quoted context omitted.
Checked Exceptions and null. I write a lot of Java and I generally enjoy the language, but those two things; if Oracle could fix those somehow I would be extremely pleased. I'm so tired of writing null checks and I hope Optional is not the final answer since it too can be a null due to programmer error. I am really worried about Optional getting abused in Java 8... Actually, I waffle on checked exceptions; it seems e…
> Checked Exceptions and null. Let's not forget about type-erasure generics. And the existence of arrays. And the fact that people still use arrays.
I really don't have a problem with erased generics for the same reason a poster below pointed out.
Re: JDK 8 Release Notes
#196Earlier quoted context omitted.
There are warts in the standard library to be sure, but many of them have already been filled in by third parties like Apache Commons, Google Guava, and Joda-time. I'm sure there are others I'm not thinking of.
Filing in the holes is nice, but without actually making it a design choice java embodies TMTOWTDI more than perl ever did. For many common tasks there are 5 or 6 different standard library calls that seem to do the same thing, but 4 of them are to be avoided at all cost, but there's no depreciation tag and the official javadocs don't contain any pointers to the newer classes.
This just isn't true.
Re: JDK 8 Release Notes
#197Earlier quoted context omitted.
It's a bad sign for .js devs: trouble ahead.
JS ecosystems in terms of quality, tooling, and engineering is already bad, can't be worse than that really... PS: No, yet-another-js-library-to-replace-jquery is not considered tooling. No, yet-another-replacement-for-grunt/bower/yeoman is not a good sign of the ecosystems. Java has Maven since 2004.
Maven is horible. Hth
Re: JDK 8 Release Notes
#198Earlier quoted context omitted.
Not sure if I enjoy SBT but Scala/Play/Akka is definitely great
Does anyone enjoy SBT? My love for Scala is profound, but fuck SBT
Once I got my head around it, I began liking it. If you're using Akka's clustering, SBT's multi-JVM testing is killer.
Re: JDK 8 Release Notes
#199Earlier quoted context omitted.
logback is pretty great. I can't take anyone seriously that defers all logging to System.out.println - do you really want the inability to change logging levels between live, test, etc?
Hmm. I've used that feature about once in 20 years of coding professionally. My production systems don't generally log; they're busy serving (I once worked on a hard real-time embedded air traffic control system where production logging was literally a single bit of information - a logic level that went high when the processor was busy, and low on idle - so we could measure our timing safety margin with an oscillosco…
> Hmm. I've used that feature about once in 20 years of coding professionally.
Try debugging systems for which you can't access the system directly ... say in a product that you redistribute to customers. You will change your tune rather quickly.
For product development, having a good logging system is critical. And, honestly, other than rolling my own over the years (20+ years experience developing and distributing products), the Java logging systems are pretty decent. It can be a pain to get different logging systems to work together and properly configured, and I do wish it were better, but System.out.println() ain't the answer either. When I spend a little time getting them to work right, they do their job. And that is time well spent in my opinion for redistributed products.
Re: JDK 8 Release Notes
#200Earlier quoted context omitted.
JavaFX is now a default platform (supported by Oracle) for developing desktop apps. It replaced the clumsy Swing and is showing a lot of promise. http://www.oracle.com/technetwork/java/javase/overview/javaf...
What is the case for desktop apps these days vs web apps? I would love to mess around with JavaFX but really can't come up with a compelling reason to use it.
Offline + sync, and higher performance requirements are my two use-cases for desktop apps.