Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

On Sat, 2016-09-10 at 10:21 -0700, 'Isaac Gouy' via golang-nuts wrote: > No one seems to have needed to discuss what was meant by library, like > sascha they seem to think they understood what was expected. Prior to your earlier post, I thought I did too, but after that many libraries I have used

[go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

Hallöchen! 'Isaac Gouy' via golang-nuts writes: > [...] > > From a sociological perspective: > > mid-May, contributors of k-nucleotide programs that used a custom > written-for-k-nucleotide hash table were notified that those > programs would no longer be shown, but programs that used a > built-i

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

On Friday, September 9, 2016 at 6:25:38 PM UTC-7, kortschak wrote: > > Can you explain the rationale behind the classification of libraries as > libraries or not libraries? It seems pretty arbitrary. > > (I'm interested from a sociological perspective, but not enough to > bother to go to the b

[go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

Hallöchen! RogerV writes: > I replaced C with C++ (mind you not C/C++) and then the curve > takes a dramatic upward spike in year 2016 (I'd say it was getting > going well in 2015). I think all the very recent changes in this statistics are due to a new (set of) repos that were added to the corp

[go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

I replaced C with C++ (mind you not C/C++) and then the curve takes a dramatic upward spike in year 2016 (I'd say it was getting going well in 2015). IOW, it looks like the efforts to modernize C++, starting with C++11, are paying off big time. I program mostly in Java these days. But I've int

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

Can you explain the rationale behind the classification of libraries as libraries or not libraries? It seems pretty arbitrary. (I'm interested from a sociological perspective, but not enough to bother to go to the benchmarks game discussion forum). On Fri, 2016-09-09 at 15:08 -0700, 'Isaac Gouy'

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

On Wednesday, September 7, 2016 at 7:44:28 PM UTC-7, Jason E. Aten wrote: > > Observe that the java benchmark continues to be allowed to use an > accelerated hash table library. > "accelerated" ? By all means, post your reasons for *why that Java library should not be used* in the benchmarks

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

On Wednesday, September 7, 2016 at 6:47:59 PM UTC-7, Clark Wierda wrote: > Apparently, you can only use approved libraries that produce the ranking > he wants. > Which one of us is the language advocate? :-) -- You received this message because you are subscribed to the Google Groups "gola

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

Observe that the java benchmark continues to be allowed to use an accelerated hash table library. -- 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+unsu

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

On Wednesday, September 7, 2016 at 1:01:23 PM UTC-4, sascha.l@googlemail.com wrote: > > > Am Mittwoch, 7. September 2016 18:20:28 UTC+2 schrieb Isaac Gouy: >> >> >> On Wednesday, September 7, 2016 at 8:15:09 AM UTC-7, >> sascha.l@googlemail.com wrote: >> >>> >>> If this does not count the

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

Am Mittwoch, 7. September 2016 18:20:28 UTC+2 schrieb Isaac Gouy: > > > > On Wednesday, September 7, 2016 at 8:15:09 AM UTC-7, > sascha.l@googlemail.com wrote: > >> >> If this does not count the Benchmark game follows a skewed defintion of a >> library. >> > > > I'm sorry that you don't s

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

On Wednesday, September 7, 2016 at 8:15:09 AM UTC-7, sascha.l@googlemail.com wrote: > > If this does not count the Benchmark game follows a skewed defintion of a > library. > I'm sorry that you don't seem to understand what is expected. > Can you eleborate please, what a library is?

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

Am Mittwoch, 7. September 2016 16:32:19 UTC+2 schrieb Isaac Gouy: > > > > On Wednesday, September 7, 2016 at 2:12:21 AM UTC-7, > sascha.l@googlemail.com wrote: > >> >> Maybe. For the shootout I prefer the embedded variant to >> to demonstrate it is do-able without resorting to 3rd party libs

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

On Wednesday, September 7, 2016 at 2:12:21 AM UTC-7, sascha.l@googlemail.com wrote: > > Maybe. For the shootout I prefer the embedded variant to > to demonstrate it is do-able without resorting to 3rd party libs. > Unfortunately, k-nucleotide now explicitly requires use of a built-in / li

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

Am Mittwoch, 7. September 2016 11:12:21 UTC+2 schrieb sascha.l@googlemail.com: > > I hope you submit your code... I would be great to be on par with java > all > > around! here's the instructions -- > > > > http://benchmarksgame.alioth.debian.org/play.html > > I will try. Currently my Go

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

2016-09-06 22:47 GMT+02:00, Jason E. Aten : > nice! would you mind releasing under an MIT or BSD license? I think it > would be It's MIT licensed now. > worth posting the hashmap alone as a reusable library. Maybe. For the shootout I prefer the embedded variant to to demonstrate it is do-able w

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

Am Montag, 5. September 2016 15:41:28 UTC+2 schrieb Jason E. Aten: > > > On Wednesday, August 31, 2016 at 8:44:57 AM UTC-7, Eric Johnson wrote: >> >> >> On 8/31/16 2:04 AM, Harald Weidner wrote: >> > The Java counterpart of this benchmark does not use the Java build-in >> > maps, but imports a

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

On Wednesday, August 31, 2016 at 4:47:35 PM UTC-7, Tim Hawkins wrote: > > I would have expected that aside from informing about general performance, > one of the purposes for benchmarks would have been to create pressure for > improvement of key features of the laguage, this seems to circumvent

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

On Wednesday, August 31, 2016 at 6:31:05 AM UTC-7, Peter Herth wrote: > > And, as this very benchmarking site is far too often abused to talk down > on languages, just because they have some bad test results, we as the Go > community should try to get the fastest results there - most other progra

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

On Wednesday, August 31, 2016 at 3:53:12 PM UTC-7, Harald Weidner wrote: > > > The regex-dna benchmark is even more strange. Neither the measured Go nor > the > Java implementation use the standard regexp libs. The Go program imports > bindings to PCRE, the Java program uses TclRE. > There'

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

On Wednesday, August 31, 2016 at 8:44:57 AM UTC-7, Eric Johnson wrote: > > > On 8/31/16 2:04 AM, Harald Weidner wrote: > > The Java counterpart of this benchmark does not use the Java build-in > > maps, but imports a map implementation for fixed data types from the > > fastutil project. > > >

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

I would have expected that aside from informing about general performance, one of the purposes for benchmarks would have been to create pressure for improvement of key features of the laguage, this seems to circumvent this, im not dure what they are trying to achive. Perhaps restrictions on only us

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

Hello, On Wed, Aug 31, 2016 at 08:44:41AM -0700, 'Eric Johnson' via golang-nuts wrote: > >The Java counterpart of this benchmark does not use the Java build-in > >maps, but imports a map implementation for fixed data types from the > >fastutil project. > I hadn't noticed that. That would seem to

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

On 8/31/16 2:04 AM, Harald Weidner wrote: Hello, On Tue, Aug 30, 2016 at 04:41:29PM -0700, 'Eric Johnson' via golang-nuts wrote: I looked at the k-nucleotide program, and was unable to figure out a way to make it faster. This is, of course, exactly what the test is suppose to be checking - th

[go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

Hallöchen! Peter Herth writes: > I am not sure I agree. Writing them in idiomatic might be good to > detect whether idiomatic works for getting fast code, but on the > other side, if I am writing a large application, I might use > slower, idiomatic code in 90% of it, and then optimize the hell >

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

I am not sure I agree. Writing them in idiomatic might be good to detect whether idiomatic works for getting fast code, but on the other side, if I am writing a large application, I might use slower, idiomatic code in 90% of it, and then optimize the hell out of the bottlenecks, throwing any elegan

[go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

Speaking of adoption, here's another awesome graph from OpenHub: :-)

[go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

Hallöchen! Harald Weidner writes: > On Tue, Aug 30, 2016 at 04:41:29PM -0700, 'Eric Johnson' via golang-nuts > wrote: > >> I looked at the k-nucleotide program, and was unable to figure >> out a way to make it faster. > >> This is, of course, exactly what the test is suppose to be >> checking -

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

Hello, On Tue, Aug 30, 2016 at 04:41:29PM -0700, 'Eric Johnson' via golang-nuts wrote: > I looked at the k-nucleotide program, and was unable to figure out a way to > make it faster. > This is, of course, exactly what the test is suppose to be checking - the > speed of the built in map. Anyone e

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

ay, August 30, 2016 at 12:15 PM *To: *golang-nuts *Subject: *[go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption On Tuesday, August 30, 2016 at 10:09:39 AM UTC-7, Scott Pakin wrote: Go 1.7 is faster than C on the mandelbrot test and faster than

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

> I looked at that this morning and sped it up a little. > *fyi "Contribute your programs" * -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving

Re: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

I looked at that this morning and sped it up a little. From: 'Isaac Gouy' via golang-nuts Reply-To: Isaac Gouy Date: Tuesday, August 30, 2016 at 12:15 PM To: golang-nuts Subject: [go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

[go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

On Tuesday, August 30, 2016 at 10:09:39 AM UTC-7, Scott Pakin wrote: > > > Go 1.7 is faster than C on the mandelbrot test and faster than C++ also > on reverse-complement? How did *that* happen? > mandelbrot -- look at the program source code.

[go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

Hallöchen! Scott Pakin writes: > On Monday, August 29, 2016 at 5:51:42 PM UTC-6, Eric Johnson wrote: >> >> Not that I think these account for much, but sort of fun to point at: >> >> https://benchmarksgame.alioth.debian.org/u64q/go.html (Short >> summary - now with Go 1.7, Go is faster for most b

[go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

On Monday, August 29, 2016 at 5:51:42 PM UTC-6, Eric Johnson wrote: > > Not that I think these account for much, but sort of fun to point at: > > https://benchmarksgame.alioth.debian.org/u64q/go.html > (Short summary - now with Go 1.7, Go is faster for most benchmarks.) > Go 1.7 is faster than C o

[go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

On Tuesday, August 30, 2016 at 1:01:51 AM UTC-7, Torsten Bronger wrote: > Obviously, C is on a steep decline in the OSS world, while Go (you > may switch off the C line to see it better) is gaining ground > steadily, and doing so faster than Rust. > Well, obviously, we find JavaScript on th

[go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

Hallöchen! 'Eric Johnson' via golang-nuts writes: > Not that I think these account for much, but sort of fun to point at: > > https://benchmarksgame.alioth.debian.org/u64q/go.html > (Short summary - now with Go 1.7, Go is faster for most benchmarks.) > > And then, for language adoption, the TIOBE

[go-nuts] Re: In case you missed it: language benchmarks for Go 1.7, and language adoption

Hi, Go1.7 is faster in most benchmarks, but still slower than Java in some benchmarks(like Go 1.6). GO Garbage Collector needs time to become mature like JVM. K-nucleotide, binary tree, Regex-dna are bad for GO(lack of fast GC and good standard libraries). But, for me, Go is an awesome substi