Hacker News Reader

Comment by rantanplan | Hacker News Reader

> My argument is that if you need a fat framework - this does not mean it has to be in some specific language. You have something like a counter argument? Please share.

I can't fathom how you can't think of counter arguments.

- Because a company invested in Go?

- Because they wouldn't want to have to maintain a lot of different technologies/languages, unless it's really necessary?

- Because a fat framework in Go is going to be lighter than a fat framework in python/ruby? (memory reqs, cpu, servers, etc)

- Because Go is easier to reason with/maintain in large codebases?

And still, right now I'd choose python, but I can't understand how someone would hold such strong opinions in such matters. Maybe I've seen too little in my career? Or have I seen too much, so as to not jump in such strong positions so easily? Genuinely curious and that's why I started this thread.

View on HN

>Because a company invested in Go?

I hardly can imagine a company that had invested only in Go and will need fat Go gramework. Seriously.

>Because they wouldn't want to have to maintain a lot of different technologies/languages, unless it's really necessary?

Not a lot of, but a number - once again, pretty hard to imagine something serious going on here. And startups will hardly chose Go as their starting point for obvious reasons.

>Because a fat framework in Go is going to be lighter than a fat framework in python/ruby? (memory reqs, cpu, servers, etc)

Absolutely not necessary. You can build framework in C and had results that will make you sad compared to that of Python. But even if it is - most likely it will be more expensive and you will have to make a choice. But okay, let's say it has some point.

>Because Go is easier to reason with/maintain in large codebases?

How so? In comparison to Python, for example.

>I can't understand how someone would hold such strong opinions in such matters

Hey, I'm not saying people shouldn't write fat Go framework, or stop doing if they've started already. If stars are lit - it means there is someone who needs it. I just don't get why would you use something like Go for this.

>I hardly can imagine a company that had invested only in Go and will need fat Go gramework. Seriously.

I don't know how to reply to this because I really don't see what's hard to imagine, but ok.

> And startups will hardly chose Go as their starting point for obvious reasons.

Well that's obviously false, or you haven't been paying attention to HN, or job listings :P

> How so? In comparison to Python, for example.

Static typing. In the case where you'd like to counter that point, I'm sincerely sorry, I'm tired of arguing over that point. I'd prefer if we left it at that and say "we agree to disagree".

> Hey, I'm not saying people shouldn't write fat Go framework, or stop doing if they've started already. If stars are lit - it means there is someone who needs it. I just don't get why would you use something like Go for this.

Fair enough. Sometimes I just like to elicit responses in order to gain new perspective/POV etc.

Cheers

Reply on news.ycombinator.com