Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Scala vs Go

quora.com

Post reply on HN
Print view View original

101–109 of 109 posts

Re: Scala vs Go

#101

Post by strictfp »

strictfp wrote: post #98
fauigerzigerk wrote: post #83

Earlier quoted context omitted.

For what it's worth, the initial EJB spec was written by IBM, so I guess the answer to your question could be yes. "The EJB specification was originally developed in 1997 by IBM and later adopted by Sun Microsystems" https://en.wikipedia.org/wiki/Enterprise_JavaBeans

Thank you for the link. I looked up Java EE, which according to wikipedia mostly originated from WebLogic. The founders didn't seem that enterprisey though: http://otechmag.com/magazine/2015/summer/michel-schildmeijer... So IBM does sound likely.

The anwers to this question is also interresting: https://www.quora.com/What-were-the-original-principles-behi... .

Hints that https://en.wikipedia.org/wiki/CICS was the product inspiring EJB.

Re: Scala vs Go

#102

Post by untoreh »

fbunau wrote: post #67

The analysis is done from the perspective of an imperative programmer. It's like someone writing Java-like Python code. When you write in Scala you completely change the way you write code, the whole paradigm. This question could be asked Haskell vs Go, it would be the same IMO. If you have chosen Scala, you don't choose it as a Java replacement, you choose it as a programming philosophy replacement Edit: Picking on…

Why do you change the way you write code with Scala? Scala is both functional and oo, Go is also like this except it is minimal at being both

Re: Scala vs Go

#103

Post by lowmagnet »

voidlogic wrote: post #87
mi100hael wrote: post #60

Earlier quoted context omitted.

> For all my non-trival projects I always fork all my dependencies into their own repos That sounds absolutely terrible. Even worse than having to track down & install libraries and headers for C projects. At least in the case of those libraries, you can enforce a particular version using autoconf or whatever. Vendoring source code for dependencies (especially in separate repos) is fragile and a pain for anyone else…

How so? The project just includes a script that git clones the forks into your Go workspace for the project /foobar/src....

And of course the fact you're forked off means you can update at your own pace and not have to take someone's ticket to "fix" a "broken" build. While I don't do this forking, it can help control churn, especially in projects with lots of deps.

Re: Scala vs Go

#104

Post by dude01 »

willvarfar wrote: post #94
dude01 wrote: post #85

Earlier quoted context omitted.

Speaking of tangents... I use pycharm too. Do you ever use type annotations in Python? I'm really digging it in Typescript for Javascript.

(I have my own, and I'm probably the only user ;) https://pypi.python.org/pypi/obiwan/ )

Oh wow, thanks for the link. Looks like you discovered typescript way before I did. It looks like Mypy is pretty popular these days. Cheers!

Re: Scala vs Go

#105

Post by chipz »

pyrale wrote: post #61
chipz wrote: post #7

One 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,

Is it available only on Java/Scala, or any language on the JVM ? If Java/Scala, do you have an idea of how much work would be needed to exploit the informations from flight recorder in e.g. Clojure ?

it should be available in any language on JVM although I've never tried it myself. It's simple enough, I don't think it would take too much work to get the information from flight recorder.

Re: Scala vs Go

#106

Post by lowmagnet »

mi100hael wrote: post #45
willvarfar wrote: post #10

Earlier quoted context omitted.

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 yo…

I get where you're coming from, but relying on an IDE for safety is a recipe for disaster. What happens when you just quickly pop open that file in on a shell to make a small change and fat-finger something? What happens when a different developer decides to use vim for everything? I used Python extensively for years and it's still my scripting language of choice, but to use it to build something safe in a business-c…

1) you get an error, and since it's a small change I'd assume you could guess where you caused it. 2) they get errors but they may have more difficulty finding them. (or they use a vim plugin for that, or pylint, etc. on save)

I'd guess your ability to suss out an error's cause without an IDE is a matter of comfort with a language, and your lack of ability isn't an IDE's fault.

Re: Scala vs Go

#107

Post by LOLOLOLO1 »

alextheparrot wrote: post #29
pweissbrod wrote: post #11

Transportability is an oft under-valued quality when comparing languages. Yes you could write something highly performant/compact/domain-specialized in perl,scala,lisp etc but when the time comes that your product is successful and your team needs to scale or you want to transfer ownership to another team how easy is that transition going to be?

A lot of Scala is written to be that scaling code, see Spark. I know your point was the possible hand-off between teams, just wanted to indicate it is often used as that scaling language in data-processing.

Spark is not just written in Scala, they shared the same philosophy of underthought design.

Luckily, there's a little reason of using Spark after Yandex released their Clickhouse: it better compresses data, it is much faster, it doesn't need crazy infrastructure of low quality Apache's code, it can be used in a realtime which is really huge.

Re: Scala vs Go

#108

Post by LOLOLOLO1 »

geodel wrote: post #8

Scala 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.

Spark is a poor joke.

Re: Scala vs Go

#109

Post by sctb »

LOLOLOLO1 wrote: post #108
geodel wrote: post #8

Scala 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.

Spark is a poor joke.

Please no empty snark like this here.
Post reply on HN