4 ms·

Summary: At a GoSF meetup audience member asked if Go was reliable... - Op was surprised because he had been using it in production for nearly 3 years. - Pre

Summary: At a GoSF meetup audience member asked if Go was reliable... - Op was surprised because he had been using it in production for nearly 3 years. - Previously used it at a Financial Company (wholesaler for institutional share traders and stock brokers). - Op used it previously for system Monitoring, as a data store and messaging middleware. - Go's adoption is gathering pace thanks to the terse syntax, straightforward powerful standard library, excellent tooling and concurrency primitives. [Sic. And performance] - Go's core development team a reason for why it is showing maturity beyond it's years. - Op changed positions so he could work on Go full-time.

carbocation 13y ago
Question: is this an automated summary or are you doing these summaries yourself manually? On topic, it seems odd that a Python process that would take 3 minutes to scan nodes could be reduced to a go script that takes under 1 second. Perhaps this is entirely due to going from serial to parallel, but the timeout thing that he mentioned sounds like an error in the Python code rather than a language problem. And I say this as someone who uses/enjoys go.
- joshbaptiste 13y ago
  Indeed.. I would have liked to hear what took the Python script 3x longer. The longest part I would assume would be the network requests themselves which is inherent regardless of language.
  - eudoxus 13y ago
    its actually 180x faster if it went from 3 mins to less then a second
  - wglb 13y ago
    Sounds like it the execution time required to processing the vast amounts of data produced. go is quite likely to beat python in compute bound or data crunching tasks.
    - Patrick_Devine 13y ago
      Go is definitely faster than Python for those types of tasks, however I'm suspicious of it being that much faster. I've crunched massive data sets in Python and as long as you're aware of its limitations, you can make things pretty zippy.

carbocation 13y ago

Question: is this an automated summary or are you doing these summaries yourself manually? On topic, it seems odd that a Python process that would take 3 minutes to scan nodes could be reduced to a go script that takes under 1 second. Perhaps this is entirely due to going from serial to parallel, but the timeout thing that he mentioned sounds like an error in the Python code rather than a language problem. And I say this as someone who uses/enjoys go.

joshbaptiste 13y ago
Indeed.. I would have liked to hear what took the Python script 3x longer. The longest part I would assume would be the network requests themselves which is inherent regardless of language.
- eudoxus 13y ago
  its actually 180x faster if it went from 3 mins to less then a second
- wglb 13y ago
  Sounds like it the execution time required to processing the vast amounts of data produced. go is quite likely to beat python in compute bound or data crunching tasks.
  - Patrick_Devine 13y ago
    Go is definitely faster than Python for those types of tasks, however I'm suspicious of it being that much faster. I've crunched massive data sets in Python and as long as you're aware of its limitations, you can make things pretty zippy.