News for hackers. Stuff that matters.
Re:Go best practices, six years in by gtrubetskoy on Sunday May 01, 2016 @07:54PM (#11608420)
Java was:

1. Wow, this program runs on any platform!

2. Wow, no need to free memory!

3. Wow, threads and locks are so easy to do!

Then many years later

4. Who really cares about cross-platform code if all I do is on Linux?

5. Why does this program require 4GB of ram?

6. Must I really download and install the JVM all the time, and what is it good for anyway?

Go:

1. Wow, I can write stuff that previously could only be done in C/C++, and I can do it almost as easily as writing Python or Ruby.

2. Wow, I don't need anything installed for my program to run, it just runs!

Re:Go best practices, six years in by bad_user on Monday May 02, 2016 @02:52AM (#11609575)
> 4. Who really cares about cross-platform code if all I do is on Linux?

Deployment happens mostly on Linux, but development happens mostly on OS X and Windows. Having guaranteed behavior, compiling it only once, being able to deploy as a simple JAR file, the same JAR file that you tested locally, is awesome.

> 5. Why does this program require 4GB of ram?

Java is actually very memory efficient, all things considering. There are Ruby developers choosing JRuby for deployment because of that efficiency. By the time Go's GC will reach the same maturity, it will behave similarly.

> 6. Must I really download and install the JVM all the time, and what is it good for anyway?

The JVM ensures consistent behavior across all platforms and is able to do optimizations based on runtime profiling, with JVM bytecode acting as a very efficient ABI, making the JVM an efficient target for multiple languages, including Scala, Clojure, Groovy, Ruby, Kotlin, Ceylon and others, languages that have been able to bootstrap easily and have a huge ecosystem at disposal because of the JVM.

> 1. Wow, I can write stuff that previously could only be done in C/C++, and I can do it almost as easily as writing Python or Ruby.

Go is not a replacement for C/C++ because it has a GC. In fact it's impossible to use Go for the same use-cases where C/C++ is required. And if you can use Go, then you can use Java as well. And in fact, because Java is more mature and has alternatives like Azul's pauseless GC, it's more amenable for projects with soft real-time constraints.

> 2. Wow, I don't need anything installed for my program to run, it just runs!

That's cool sometimes, but Java is almost as ubiquitous as POSIX and HTML5. On Linux it's basically one "apt-get install" away, just like everything else. So the advantage of not requiring a runtime for me is, you know, meh.

Re:Go best practices, six years in by gizzlon on Monday May 02, 2016 @07:44AM (#11610611)
>> 5. Why does this program require 4GB of ram?

> Java is actually very memory efficient, all things considering.

Huh? Considering what? Compared to what?

> There are Ruby developers choosing JRuby for deployment because of that efficiency.

Yeah, Java !=JVM, and Ruby is not Go so this is kind of moot.

>By the time Go's GC will reach the same maturity, it will behave similarly.

Says who? You can't just state that as a fact without backing it up somehow.

Re:Go best practices, six years in by fauigerzigerk on Monday May 02, 2016 @04:39AM (#11610009)
>Java is actually very memory efficient, all things considering

That makes me wonder about your universe of things to consider. Java's terrible memory usage was set in stone the moment they decided not to include structured value types.

Re:Go best practices, six years in by pjmlp on Monday May 02, 2016 @06:50AM (#11610429)
Besides being planned for Java 10, there are AOT and JIT compilers for Java that are able to convert simple Java types that follow a specific value pattern into value types.

An example would be how the IBM J9 JIT converts a final Point class, just with getters and setters into a value type.

Also there are language extensions from JVMs like IBM Packed Objects or Azul Object layouts that are exploring how to involve the language into value types.

It sucks that they didn't follow the route of Mesa, Modula-3, Eiffel and Oberon in regards to value types, but they aren't holding still.

Re:Go best practices, six years in by fauigerzigerk on Monday May 02, 2016 @07:20AM (#11610510)
If the compiler can prove that an object is final and immutable and is never used in any other context that requires reference semantics, it could potentially use that optimization.

But then you also need data structures that can be parameterized to store such value objects as values. Otherwise you're back to square one.

Re:Go best practices, six years in by pjmlp on Monday May 02, 2016 @07:54AM (#11610643)
Which is the point of IBM and Azul's research.
Re:Go best practices, six years in by threeseed on Monday May 02, 2016 @06:30AM (#11610358)
Value Types are being worked on now for Java 10+.

https://en.wikipedia.org/wiki/Project_Valhalla_(Java_languag...

The Java language is definitely not set in stone.

Re:Go best practices, six years in by fauigerzigerk on Monday May 02, 2016 @06:48AM (#11610427)
No, the Java language is not set in stone. Its terrible memory usage is set in stone as long as the language doesn't have value types.

If (and that's a big if) they introduce value types in 2018, it will have been almost 25 years since that fateful decision that has done so much damage.

Re:Go best practices, six years in by pjmlp on Monday May 02, 2016 @07:13AM (#11610488)
While it sucks that Java does not support value types like other GC enabled languages, apparently Go owner's are fine with that decision, to the point of fighting to keep using it on their products instead of replacing it with Go.
Re:Go best practices, six years in by fauigerzigerk on Monday May 02, 2016 @07:38AM (#11610586)
That's like saying you're fine with every decision taken by a government you voted for.

Go owners have millions and millions of lines of existing Java code and they employ many people whose entire careers were made on top of Java.

I'm not saying there are no rational reasons to prefer Java over Go. But Google is hardly the yardstick for that.

Re:Go best practices, six years in by geodel on Monday May 02, 2016 @08:49AM (#11610881)
With >3 years release cycle by mid 2017 we are hoping to get Java 9 so to me Java 10 seams 2020 at the earliest.
Re:Go best practices, six years in by peteretep on Sunday May 01, 2016 @08:16PM (#11608495)
You're in stage 2, then.
Re:Go best practices, six years in by catnaroek on Monday May 02, 2016 @02:21AM (#11609488)
> threads and locks are so easy to do!

I don't think concurrent programming was ever particularly easy in Java. If you're talking about `synchronized` methods, well, they are of limited usefulness (to put it mildly) when you need to lock objects in an interleaved fashion: "lock A, lock B, unlock A, lock C, unlock B, lock D, unlock C, etc.", which isn't too uncommon a user case.

> stuff that previously could only be done in C/C++ (...) almost as easily as writing Python or Ruby

Metaprogramming, any? C++ has templates. Python and Ruby have metaclasses. What does Go have?

Re:Go best practices, six years in by spriggan3 on Monday May 02, 2016 @05:35AM (#11610190)
> What does Go have?

Go generate AKA C Macros but even worse since there is no macro syntax , you have to code you own code generator yourself .

Re:Go best practices, six years in by dig1 on Sunday May 01, 2016 @09:22PM (#11608687)
2. Yea, right. Obviously you haven't run enough Go binaries
Re:Go best practices, six years in by gizzlon on Monday May 02, 2016 @07:40AM (#11610598)
Really? I also find that to be true for the go stuff I run.

The last example is nsq[1]: Download, unzip and run the binaries .. aahh :)

Obviously this can be true for non-golang programs as well, but I can't think of any right now.

1: http://nsq.io/deployment/installing.html

Re:Go best practices, six years in by spriggan3 on Monday May 02, 2016 @05:30AM (#11610172)
> 5. Why does this program require 4GB of ram?

The biggest issue with Java IMHO , 6 not so much since deployment is automated.

> 1. Wow, I can write stuff that previously could only be done in C/C++

Not true, like at all. Every Go does can be done with Java.

Re:Go best practices, six years in by incepted on Sunday May 01, 2016 @11:44PM (#11609091)
> 4. Who really cares about cross-platform code if all I do is on Linux?

Most developers write their code on Windows and MacOS and then deploy on Linux. I'd say this "Write once run anywhere" thing was and still is a pretty big deal.

> 5. Why does this program require 4GB of ram?

Oh no! I need to buy a $5 piece of hardware to run this Java code? What kind of nonsense is that?

> 6. Must I really download and install the JVM all the time, and what is it good for anyway?

Once or twice a year, if you really want to. You update your browser much more often.

Re:Go best practices, six years in by throwaway_exer on Monday May 02, 2016 @01:04AM (#11609285)
> Oh no! I need to buy a $5 piece of hardware to run this Java code? What kind of nonsense is that?

4 GB per program absolutely destroys VM consolidation. I love the look on managers' faces when they ask for a 1 GB VM and I ask them, "Is this for a Java program?" :)

Re:Go best practices, six years in by nixusg on Monday May 02, 2016 @01:44AM (#11609396)
Just adding some ram is also not so easy in an embedded system.
Re:Go best practices, six years in by Hydraulix989 on Monday May 02, 2016 @02:39AM (#11609537)
But the Java JRE update installer wizard for Windows touts the fact that Java is "in" thousands of embedded systems -- parking meters, toasters, etc.
Re:Go best practices, six years in by threeseed on Monday May 02, 2016 @06:31AM (#11610363)
There are dozens of Java VMs some of which are optimised for embedded systems:

https://en.wikipedia.org/wiki/List_of_Java_virtual_machines

Re:Go best practices, six years in by dig1 on Monday May 02, 2016 @04:34AM (#11609984)
Imagine, Java is run on your phone's SIM card. Enough?

On other hand, on truly constrained embedded systems where real time is essential, no GC-based language has any business, no matter how GC is good. Even C++ is sometimes avoided.

Re:Go best practices, six years in by pjmlp on Monday May 02, 2016 @07:10AM (#11610481)
You mean like missile radar control systems?

http://www.pr.com/press-release/136232

Or do you prefer Aegis battleship Weapons System ?

http://dl.acm.org/citation.cfm?id=2402699

These are my favorite examples for Java being used in life critical situations.

Re:Go best practices, six years in by geodel on Monday May 02, 2016 @09:44AM (#11611230)
Well 2 thing stand out for me from links you mentioned:

> The applications use a combination of Thales proprietary middleware written in C combined with Java code enabled by the Java™ Native Interface (JNI).

> AONIX has additionally delivered professional services to help PERC Ultra users at Thales optimize their applications and improve execution performance including, a customer-specific training course handled the needs of coding in Java™ with hard real time constraints.

Seems like with helping of C and Consulting on 'How to do Java right' they made it work.

> End-to-end distributed thread timing constraints measured from stimulus to response are typically under 100 ms.

Since it is slightly faster than typical (per char) typing speed on keyboard. It appears nice but terribly impressive real time Java use case.

Re:Go best practices, six years in by pjmlp on Monday May 02, 2016 @10:26AM (#11611609)
For me it is impressive, because if the system doesn't work, the wrong guys die.
Re:Go best practices, six years in by frankzinger on Monday May 02, 2016 @09:51AM (#11611291)
> Imagine, Java is run on your phone's SIM card. Enough?

Not Java, not even close. JavaCard is an extremely stripped-down version of Java. I've used it and it feels like C.

From https://en.wikipedia.org/wiki/Java_Card#Java_Card_vs._Java:

> However, many Java language features are not supported by Java Card (in particular types char, double, float and long; the transient qualifier; enums; arrays of more than one dimension; finalization; object cloning; threads). Further, some common features of Java are not provided at runtime by many actual smart cards (in particular type int, which is the default type of a Java expression; and garbage collection of objects).

[EDIT] But I am not arguing with the overarching argument that Java proper can run efficiently on very constrained devices. It all depends on the implementation.

Re:Go best practices, six years in by m_mueller on Sunday May 01, 2016 @11:49PM (#11609104)
> What kind of nonsense is that?

.. and then someone gets the idea that your application should now run natively on Android phones, since they all run Java anyway, right?

Re:Go best practices, six years in by incepted on Sunday May 01, 2016 @11:51PM (#11609112)
Yes, they all run Java.

What's your point?

Re:Go best practices, six years in by frankzinger on Monday May 02, 2016 @12:03AM (#11609139)
I'm guessing his point is that "4 GB" is a big problem on a phone.
Re:Go best practices, six years in by incepted on Monday May 02, 2016 @12:07AM (#11609150)
Yes it is, but his number was an exaggeration in the first place.

There are hundreds of millions of phones running Java today, what does that tell you?

Re:Go best practices, six years in by m_mueller on Monday May 02, 2016 @01:28AM (#11609346)
The point is that memory still matters, not that Java is inherently a problem. You're shifting the goalpost here - earlier your claim was that 4GB is not a big deal since we can just buy more memory, now it's that 4GB is a ridiculous number anyway.

It's not if you meet one of these typical "don't do any premature optimisations (even in the design phase of my data structures), because some important CS person said so"-designs. There's all too many programmers who think they should never have to care about hardware anymore.

Re:Go best practices, six years in by viraptor on Monday May 02, 2016 @01:30AM (#11609349)
> Once or twice a year, if you really want to.

I really hope you actually mean 7+ times a year. https://en.wikipedia.org/wiki/Java_version_history#Java_8_up... - most versions contained security updates.

Re:Go best practices, six years in by incepted on Monday May 02, 2016 @02:51AM (#11609571)
None of these updates are mandatory. You don't have to upgrade anything if you don't want to.
Re:Go best practices, six years in by viraptor on Monday May 02, 2016 @03:06AM (#11609624)
If you looked at the issues and verified they're either not applicable in your case or don't affect your application, you already spent a lot of time on it. If you do install, you should verify your app still works. If not, you already spent time on analysis. The actual installation time is next to nothing compared to everything else around the "new jre came out" event.

What I'm saying is - you should care 7+ times a year. Doesn't matter if you only update twice.

Re:Go best practices, six years in by goodplay on Monday May 02, 2016 @12:15AM (#11609166)
> Oh no! I need to buy a $5 piece of hardware to run this Java code? What kind of nonsense is that?

Funny. That's Microsoft line of thought with Vista.