News for hackers. Stuff that matters.
Re:Java is back? Programming language trends for 2345 teams by paukiatwee on Monday April 21, 2014 @10:09AM (#7621104)
Any reason why Go is better than Java on Android? Concurrency is the reason? I personally think Go is good for System Programming, e.g. Docker, GoRouter (Cloud Foundry), etc.
Re:Java is back? Programming language trends for 2345 teams by rakoo on Monday April 21, 2014 @11:45AM (#7621632)
I have a personal preference for Go over Java, but I'd say Go's big focus on concurrency is a big win for mobile , where you don't need to compute many things but need to react to many exterior stimuli.
Re:Java is back? Programming language trends for 2345 teams by melling on Monday April 21, 2014 @11:10AM (#7621421)
Should get faster binaries, thus better on the batteries. I think better compile times would help with the edit-compile-run cycle.
Re:Java is back? Programming language trends for 2345 teams by pmelendez on Monday April 21, 2014 @10:13AM (#7621121)
Another reason would be that JNI is horrible and if you need to mix your app with native code you are out of luck.
Re:Java is back? Programming language trends for 2345 teams by paukiatwee on Monday April 21, 2014 @10:17AM (#7621135)
So Go solve the problem, right? How is Go's OpenGL/OpenGL ES?
Re:Java is back? Programming language trends for 2345 teams by kasey_junk on Monday April 21, 2014 @10:18AM (#7621140)
Is the Go FFI any better? How does it interact with the garbage collector? What aspects of the JNI are horrible in your mind (I have a few in mind as well) and how does the Go FFI differ?
Re:Java is back? Programming language trends for 2345 teams by kyrra on Monday April 21, 2014 @10:32AM (#7621205)
The most common solution in go is to use cgo[0] when wanting to bind with another language. From C you can then do whatever you'd like. That's how people are interacting with OpenGL[1] or QT[2] for example. Though, it seems like most common use cases of Go are to stay within the libraries supported by the shipping library or 3rd party libraries written in pure Go.

[0] http://golang.org/cmd/cgo/

[1] https://github.com/go-gl/gl

[2] https://code.google.com/p/goqt/

Re:Java is back? Programming language trends for 2345 teams by kasey_junk on Monday April 21, 2014 @10:41AM (#7621240)
Right, but how is that different than JNI?

For instance one of the major complaints about the JNI is that adds a pretty high performance penalty to any native calls (and typically you want native calls when performance is important). Does Go's FFI not have this performance penalty? If not, why not?

Like with the JNI, Go's garbage collector needs to understand life cycle semantics of objects coming in/out of the native binding, how is this accomplished and does it do a good job? Does it complicate the garbage collection of other unrelated parts of the system?

Basically, if you are going to claim that the JNI is awful (and I think that is a valid claim) and then imply that Go's isn't, I'd like to know why that is.

Re:Java is back? Programming language trends for 2345 teams by Zariel on Monday April 21, 2014 @04:45PM (#7623694)
The go runtime will manage memory of thins allocated in Go land but you must manage memory in C land.

If you allocate memory using C.malloc you must use C.free otherwise you will leak memory.

Re:Java is back? Programming language trends for 2345 teams by kasey_junk on Monday April 21, 2014 @06:36PM (#7624424)
Which again is very similar to JNI. I'm genuinely curious as to how Go's FFI differs from Java's to make that a distinguishing characteristic between the 2 languages.
Re:Java is back? Programming language trends for 2345 teams by twic on Monday April 21, 2014 @06:25PM (#7624377)
So how can native code get access to objects on the Go heap?