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 @05:54PM (#15666445)

Yes, that's my point. It is premature optimization, because you do not have a use case for such performance. Instead you might want Python's extensive numerical libraries, or you enjoy its quick prototyping capacities. The same way that you do not always go for C, and sometimes prefer Go, because of non performance related requirements.

That's why saying a compiled performant language should be default is not logic I understand. Default should be whatever you need for your requirements. If you don't need anything special, just go with what you already know well.

[ Parent | on HN ]

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

Fine, but if that's your point, don't say "Why not use C all the time by default then?" Actually make that point, rather than leaving us all guessing as to what your point is, and more important, why it's your point.

And, as I said, "Why not use C all the time by default then?" does not actually follow as the logical endpoint of the argument that your trying to answer, so making that your response really doesn't contribute much to the advancement of the conversation.

[ Parent | on HN ]

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

The only reason python has numerical libraries (e.g. numpy) is because they are written in C.

[ Parent | on HN ]