4 ms·

Wouldn't java be the natural rewrite, for performance speed up? Java is betwen Python and C, in terms of ease-of-use and performance. They mention a C rewrite,

by hyp0 12y ago

Wouldn't java be the natural rewrite, for performance speed up? Java is betwen Python and C, in terms of ease-of-use and performance. They mention a C rewrite, but not a java one... I guess the concept here is that Go is between Python and Java: (much of) the ease of use of Python + (much of) the performance of Java. The type system literally straddles the dynamic and static. [ I also detect an enthusiasm for cool, new tech for its own sake (despite risks and cost, or whether it's actually better or not - hell let's find out!) ]

untothebreach 12y ago
Since they are targeting an embedded ARM system, maybe they had concerns about running the JVM on such constrained hardware?
- pjmlp 12y ago
  You mean like these? https://www.aicas.com/cms/en/JamaicaVM https://www.aicas.com/cms/en/JamaicaVM
- rcfox 12y ago
  Actually, some ARM processors have instruction set extensions to execute Java bytecode in hardware. http://en.wikipedia.org/wiki/Jazelle http://en.wikipedia.org/wiki/Jazelle
sagichmal 12y ago
> The type system literally straddles the dynamic and > static The Go type system is fully static...
- nostrademons 12y ago
  Go has an escape hatch (interface{} and downcasts) that basically give it an embedding of a dynamic type system inside the static one. You end up having to use this a lot if you're doing things like decoding complex JSON data structures or working with containers, since Go doesn't have generics.
  - masklinn 12y ago
    > Go has an escape hatch (interface{} and downcasts) that basically give it an embedding of a dynamic type system inside the static one. No, that gives you a static type system with loopholes, same as Java, you have to use reflect to get a dynamic system in which you can invoke an arbitrary and unchecked method on an object (also same as Java). Granted, because Go's type system is structural you could define an interface with just the method(s) you want, cast your object to that interface and then call the methods, and you can even define the interface anonymously and inline. Still, go requires your static types to match unless you use reflect.
bsg75 12y ago
> [ I also detect an enthusiasm for cool, new tech for its own sake (despite risks and cost, or whether it's actually better or not - hell let's find out!) ] Why? Because they did not choose Java?
njharman 12y ago
> Java is betwen Python and C, in terms of ease-of-use Opinions vary highly on that claim. In fact, I've never seen anyone claim "ease-of-use" as one of Java's properties.
- kazagistar 12y ago
  He is putting it higher then C. Its not like he is setting a particularly high bar.

by hyp0 12y ago

untothebreach 12y ago

Since they are targeting an embedded ARM system, maybe they had concerns about running the JVM on such constrained hardware?

pjmlp 12y ago
You mean like these? https://www.aicas.com/cms/en/JamaicaVM https://www.aicas.com/cms/en/JamaicaVM
rcfox 12y ago
Actually, some ARM processors have instruction set extensions to execute Java bytecode in hardware. http://en.wikipedia.org/wiki/Jazelle http://en.wikipedia.org/wiki/Jazelle

sagichmal 12y ago

> The type system literally straddles the dynamic and > static The Go type system is fully static...

nostrademons 12y ago
Go has an escape hatch (interface{} and downcasts) that basically give it an embedding of a dynamic type system inside the static one. You end up having to use this a lot if you're doing things like decoding complex JSON data structures or working with containers, since Go doesn't have generics.
- masklinn 12y ago
  > Go has an escape hatch (interface{} and downcasts) that basically give it an embedding of a dynamic type system inside the static one. No, that gives you a static type system with loopholes, same as Java, you have to use reflect to get a dynamic system in which you can invoke an arbitrary and unchecked method on an object (also same as Java). Granted, because Go's type system is structural you could define an interface with just the method(s) you want, cast your object to that interface and then call the methods, and you can even define the interface anonymously and inline. Still, go requires your static types to match unless you use reflect.

bsg75 12y ago

> [ I also detect an enthusiasm for cool, new tech for its own sake (despite risks and cost, or whether it's actually better or not - hell let's find out!) ] Why? Because they did not choose Java?

njharman 12y ago

> Java is betwen Python and C, in terms of ease-of-use Opinions vary highly on that claim. In fact, I've never seen anyone claim "ease-of-use" as one of Java's properties.

kazagistar 12y ago
He is putting it higher then C. Its not like he is setting a particularly high bar.