Go mindshare suffers if it's seen as worse for prototyping, and necessary only for scale. Especially as there are more efficient (albeit more complex) ways to achieve scale.
On Mon, Jan 27, 2020, 10:55 AM Eric S. Raymond <e...@thyrsus.com> wrote: > Michael Jones <michael.jo...@gmail.com>: > > Python, to its credit, has the nice inclusive property of extensible > > interpreters of being friendly to "hang things" onto just like ornaments > on > > trees. By linking with C/C++-libraries and adding glue/shim code, > anything > > can be used from Python. This facility and interpretive execution (as > Eric > > Johnson observed above) makes it a natural for discovery and trying of > > things. > > > > These virtues may seem less so in eventual deployments, at scale, and in > > other cases. > > True, and connects directly to my recent experience report. > > Python was the best language to prototype reposurgeon in, > but scale pressure forced the move to Go. > -- > <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a> > > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAKvHMgRSCF5MQW4CTew5kD4KKNkdt4X7c0X1gqDq6Bxyz98ssQ%40mail.gmail.com.
