I'm just a "rando" from the peanut gallery, but over the past 2 years I've
nearly *always* been able to find bindings with which to "hang things on" a
Go-based prototype, if indeed it wasn't already in the stdlib.

So golang has become my 'go-to' for prototyping, replacing Python entirely
for new work. One of the main drivers for me taking the dive into golang
from C and Python was the superb tooling and lightning-fast build/test/run
cycle it enabled, which felt almost as low-friction as Python.

On Mon, 27 Jan 2020 at 11:55, Robert Engels <reng...@ix.netcom.com> wrote:

> easy prototyping != scaling
>
> Pick one.
>
>
>
> On Jan 27, 2020, at 1:42 PM, Liam Breck <l...@networkimprov.net> wrote:
>
> 
> 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
> <https://groups.google.com/d/msgid/golang-nuts/CAKvHMgRSCF5MQW4CTew5kD4KKNkdt4X7c0X1gqDq6Bxyz98ssQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> --
> 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/BE504CA9-0E8F-4B09-8522-CDC7139F264B%40ix.netcom.com
> <https://groups.google.com/d/msgid/golang-nuts/BE504CA9-0E8F-4B09-8522-CDC7139F264B%40ix.netcom.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CAN4yCu_WyzHDrLvvtectUbRZndTDtaxL5AKmhL7BMBVWaUd96w%40mail.gmail.com.

Reply via email to