Scala vs Go
quora.com
Scala vs Go
1–10 of 109 posts
Re: Scala vs Go
#2Would be interesting to get a gauge on how many bugs are typical in code in each language.
From what I've heard Go code features a comparable number of bugs to Python per line of code. But far more lines of code. I don't know how that compares to Scala but would be very interested to know.
Re: Scala vs Go
#3The language complexity comparison based on the number of pages in the spec is incredibly not useful and disingenuous.
The Java specification is actually a fairly good specification and also covers a great deal of the runtime (of which Scala gets a free ride).
The C specification is 500 or so pages.
IMO the Go specification is sorely lacking in details (albeit I must confess written in a much more modern and pithy way). It also doesn't have legacy baggage. This isn't to say Go is bad or good but you shouldn't base your decision on the length of the spec (particularly when formatting also plays a large part).
BTW if you are looking for close to the best of both Go and Scala (an in between) take a serious hard look at OCaml. Yes OCaml multicore is not done but it is coming. And in ref to the authors mention of being explicit IMO OCaml is the most explicit language I know (ironic given it has incredibly good type inference).... Oh and for completeness its specification is 657 pages. I actually learned most of the language by reading the spec.
Re: Scala vs Go
#4FIGHT!
Re: Scala vs Go
#5Worth the read if only for the meme of the dog at the end.
Re: Scala vs Go
#6The language complexity comparison based on the number of pages in the spec is incredibly not useful and disingenuous. The Java specification is actually a fairly good specification and also covers a great deal of the runtime (of which Scala gets a free ride). The C specification is 500 or so pages. IMO the Go specification is sorely lacking in details (albeit I must confess written in a much more modern and pithy wa…
> The Java specification is actually a fairly good specification and also covers a great deal of the runtime (of which Scala gets a free ride).
but isn't the java spec split in two: the java language specification and the java virtual machine specification? (honest question)
Re: Scala vs Go
#7One thing that I like about Scala is that we can use Java Mission Control to analyze how our code (to the 'method' level,) perform in production. Not just deploy and pray that our code will hold strong enough to handle the load.
I only see this feature in Scala and Java --not that we wanna compare in this case,
Re: Scala vs Go
#8Scala is half a decade older than Go and has lead in big data infrastructure projects. Go has lead in container management infrastructure. May be that's their niche areas.
I would be interested in seeing when they are applied in other's domain and how good/bad they really are.
Re: Scala vs Go
#9One thing that I like about Scala is that we can use Java Mission Control to analyze how our code (to the 'method' level,) perform in production. Not just deploy and pray that our code will hold strong enough to handle the load. I only see this feature in Scala and Java --not that we wanna compare in this case,
Ops support and transparency is superb on the JVM. That some languages don't even have something remotely comparable is something that didn't even occur to me before expanding my horizon beyond Java.
Re: Scala vs Go
#10Would be interesting to get a gauge on how many bugs are typical in code in each language. From what I've heard Go code features a comparable number of bugs to Python per line of code. But far more lines of code. I don't know how that compares to Scala but would be very interested to know.
Complete tangent, but I must say that since I recently started using pycharm it has really caught most of the obvious typo and uninitialized bugs and my python code is really crashing surprisingly rarely as I prototype to death.
Just saying in case there are others who haven't been trying modern python tooling and don't know that you can get real close to a compiled language type safety certainty these days before you run a line of code.