News for hackers. Stuff that matters.
Re:135M messages a second between processes in Java (2013) by formula1 on Saturday August 13, 2016 @07:52PM (#12283640)
Java really isnt that bad. I think the biggest issue surrounding it is a package manager, better ui/templating language and a more obvious/documented import and linking api. Outside of that it isnt too bad

Edit : also events were annoying in 7. I dont have a particular interest in creating a class just to act as a listener. I believe 8 introduced lambdas which is nice

Re:135M messages a second between processes in Java (2013) by aeroevan on Saturday August 13, 2016 @08:33PM (#12283759)
Java 8 with lambdas and streams is actually fairly nice to program. It's still Java, but it is much better than it was before Java 8.

Maven is complicated, but Java 9 with project jigsaw might help things out on the packaging side.

I don't do ui or any templating in java (analytics and simulations) so don't really know what's going on in those areas.

Re:135M messages a second between processes in Java (2013) by Pxtl on Saturday August 13, 2016 @08:52PM (#12283806)
Is Java planning on custom primitives analogous to c# structs, or is copy-by-value semantics still the exclusive province of the core language primitives?
Re:135M messages a second between processes in Java (2013) by bitmapbrother on Saturday August 13, 2016 @09:16PM (#12283862)
Yes. Value Types, Reified Generics and Generic Specialization (e.g. List<int>) will all be in Java 10.
Re:135M messages a second between processes in Java (2013) by kasey_junk on Saturday August 13, 2016 @08:56PM (#12283814)
Project Valhalla is supposedly bringing value types to the JVM.
Re:135M messages a second between processes in Java (2013) by agibsonccc on Saturday August 13, 2016 @08:40PM (#12283776)
I'd consider maybe looking at gradle then. The awesome thing about maven is it is os agnostic and is at least stable.

Most of the jvm libs are stored in maven central.

Re:135M messages a second between processes in Java (2013) by _asummers on Saturday August 13, 2016 @09:11PM (#12283853)
Gradle is fantastic to work with. Groovy is nice when you need it, but the DSL is just much better to work with than Maven.
Re:135M messages a second between processes in Java (2013) by vorg on Sunday August 14, 2016 @04:39AM (#12284816)
Gradle 3, due out soon, will use Kotlin instead of Apache Groovy as its prefered language for writing build scripts and plugins.
Re:135M messages a second between processes in Java (2013) by durub on Tuesday August 16, 2016 @03:10AM (#12295992)
Re:135M messages a second between processes in Java (2013) by _asummers on Sunday August 14, 2016 @10:38AM (#12285730)
Ooooh how exciting! I like that a lot. I can find this out myself, but what do they plan on doing with existing Groovy plugins for gradle pipelines?
Re:135M messages a second between processes in Java (2013) by cel1ne on Sunday August 14, 2016 @05:19AM (#12284945)
...which will make it completely typesafe.
Re:135M messages a second between processes in Java (2013) by mablap on Saturday August 13, 2016 @10:33PM (#12284050)
I'm not saying Java is bad or not. All I'm saying is that, from my perspective, why should I bother? It just seems very big and unwieldy and if I'm not going to do these JVM optimizations anyway, why bother?

It's really just an impression.

Re:135M messages a second between processes in Java (2013) by formula1 on Sunday August 14, 2016 @05:55AM (#12285030)
Forces you to 100% commit to oop paradime. Often much easier to test and more clean than counterparts. Its used in enterprises for a reason.