Earlier quoted context omitted.
There are many conventions held around technologies no longer in common use, but which still have an avid following of those that still find usefulness or enjoyment from them. For example, conferences around the Amiga and the Commodore 64 are still going on in 2018. I would honestly not be surprised if there was truly a conference dedicated to the Gopher protocol out there. If there was, I would totally want to read…
Gopher is not the only topic, but Bitreich Con had some talks about gopher like "Migrating the web to gopher". gopher://bitreich.org/1/con/2018
GopherCon 2018 Performance Tuning Workshop
11–20 of 22 posts
Re: GopherCon 2018 Performance Tuning Workshop
#12When I saw the headline I thought for a moment this was about the protocol. https://en.wikipedia.org/wiki/Gopher_(protocol)
Really? Would you care to talk about your work with the gopher protocol and it's application in today's computing environment?
edit: apparently it exists! http://gopher.floodgap.com/gopher/gw?gopher://hngopher.com:7...
Re: GopherCon 2018 Performance Tuning Workshop
#13darn, was hoping this was for the protocol
Re: GopherCon 2018 Performance Tuning Workshop
#14Earlier quoted context omitted.
Really? Would you care to talk about your work with the gopher protocol and it's application in today's computing environment?
I would love to see "high performance" Gopher! It would certainly be a nice way to browse websites like HN and reddit without suffering bloat (especially the reddit redesign) edit: apparently it exists! http://gopher.floodgap.com/gopher/gw?gopher://hngopher.com:7...
Re: GopherCon 2018 Performance Tuning Workshop
#15I find the simplest way to performance tune Go programs is to wait for the next release.
Re: GopherCon 2018 Performance Tuning Workshop
#16I find the simplest way to performance tune Go programs is to wait for the next release.
Re: GopherCon 2018 Performance Tuning Workshop
#17I find the simplest way to performance tune Go programs is to wait for the next release.
I wonder are people really using go where performance is bottlenecking on code (and not say network)?
Re: GopherCon 2018 Performance Tuning Workshop
#18I find the simplest way to performance tune Go programs is to wait for the next release.
performance improvements untill 1.9 were great, but last few releases performance improvements were meh. Maybe we have reached the peak.
Of course, maybe by then, gccgo/gollvm will have just as good a runtime and be the way to go if you want performance.
Or maybe they are just prioritizing non-performance tasks like debugging and Go 2.
Re: GopherCon 2018 Performance Tuning Workshop
#19I find the simplest way to performance tune Go programs is to wait for the next release.
I wonder are people really using go where performance is bottlenecking on code (and not say network)?
For non C/C++ developers, Go is much easier to work with and get performance benefits that before would only be possible by porting to C, or you end up not writing idiomatic Scala, which defeats the purpose of using Scala (imho)
Re: GopherCon 2018 Performance Tuning Workshop
#20Earlier quoted context omitted.
I wonder are people really using go where performance is bottlenecking on code (and not say network)?
About 6 years ago we adopted Scala for our server side language, and for the past 4 years we have been migrating old code that was CPU/memory hungry to go and getting very good results. All new code, if it's going to be cpu/memory intense, we write it in Go. For non C/C++ developers, Go is much easier to work with and get performance benefits that before would only be possible by porting to C, or you end up not writi…
Ooh for me, more than 50 connections a second would be unusual, but also the service really should never die.