Learning Go by porting a medium-sized web back end from Python

Re:Learning Go by porting a medium-sized web back end from P... by didibus on Thursday November 09, 2017 @12:10PM (#15664038)

OP was saying porting a project to Go sounds like premature optimization. The alternative is obviously to continue to use the original language.

The question to be answered is why are you porting it? Fun and giggles? Hoping to achieve better performance? Scale? Portability? Correctness? Simplicity? Support?

I'd say most of the time its for fun and giggles. Which I think is as fine a reason as all the others, but when its costing someone's elses money, maybe you should be more considerate.

[ Parent | on HN ]

Re:Learning Go by porting a medium-sized web back end from P... by hasenj on Thursday November 09, 2017 @09:28PM (#15667495)

I think it's the opposite. Choosing python in the first place is mostly for fun and giggles.

People want to switch away from python because of all the pain they feel from it.

[ Parent | on HN ]

Re:Learning Go by porting a medium-sized web back end from P... by didibus on Thursday November 09, 2017 @09:42PM (#15667539)

Ya, maybe for some. I think for businesses part of it is familiarity, as its now a lot of people's first language. I also think its a choice made often when you start, because it allows you to go faster in the beginning. Which is where a lot of new projects need to be the fastest. Its still a great choice for projects that are short lived, that's why ML works so well on it, most of ML is just quick iterations on prototypes until you find a solid model.

[ Parent | on HN ]