The State of Go

#1

Post by crawshaw » Wed, May 27, 2015, 2:40 AM UTC

Re: The State of Go

#2

Post by melling » Wed, May 27, 2015, 3:25 AM UTC

Nice little change in syntax.

    m := map[Point]string{
        Point{29.935523, 52.891566}:   "Persepolis",
        Point{-25.352594, 131.034361}: "Uluru",
        Point{37.422455, -122.084306}: "Googleplex",
    }

may now be written as:

    m := map[Point]string{
        {29.935523, 52.891566}:   "Persepolis",
        {-25.352594, 131.034361}: "Uluru",
       {37.422455, -122.084306}: "Googleplex",
    }

Re: The State of Go

#3

Post by giaour » Wed, May 27, 2015, 3:28 AM UTC

Shared libraries? I thought "no DLLs" was one of the major design philosophies of Go.

Re: The State of Go

#4

Post by vezzy-fnord » Wed, May 27, 2015, 3:30 AM UTC

giaour wrote: post #3

Shared libraries? I thought "no DLLs" was one of the major design philosophies of Go.

I was surprised too given the Plan 9 culture's rejection of dynamic linking.

However, this will probably deprecate or diminish the RPC and code generation techniques for implementing plugin architectures.

Re: The State of Go

#5

Post by acomjean » Wed, May 27, 2015, 3:32 AM UTC

Pretty neat, go is now written in go "Go 1.5 has no C code in the tool chain or runtime.", go shared libraries interoperable with c.

I'm really a go tinkerer, but I like the langauge.

I didn't realize Garbage Collection was so expensive that the goal is to only have it run 20% of the time. But its a good goal.

"Run Go application code for at least 40ms out of every 50ms."

Re: The State of Go

#6

Post by nkozyra » Wed, May 27, 2015, 3:33 AM UTC

"Go 1.5 provides support for Android and experimental support for iOS."

Tell me more ...

Re: The State of Go

#7

Post by nogostill » Wed, May 27, 2015, 3:37 AM UTC

Still no generics, nor real type inference.

Re: The State of Go

#8

Post by ecnahc515 » Wed, May 27, 2015, 3:41 AM UTC

giaour wrote: post #3

Shared libraries? I thought "no DLLs" was one of the major design philosophies of Go.

One of the major design philosophies was ease of deployment, DLLs generally complicate that process, but for many purposes, they're a necessary tool.

Interop with existing libraries is certainly a worthy enough feature to add to the Go toolchain, and it's an optional feature, so ease of deployment is still a primary concern, but if you need DLLs, this is available.

Re: The State of Go

#9

Post by chenzhekl » Wed, May 27, 2015, 3:41 AM UTC

giaour wrote: post #3

Shared libraries? I thought "no DLLs" was one of the major design philosophies of Go.

This feature may be prepared for building shared libraries for C. After all, Using shared libraries is popular in C world.

Re: The State of Go

#10

Post by nickysielicki » Wed, May 27, 2015, 3:44 AM UTC

melling wrote: post #2

Nice little change in syntax. m := map[Point]string{ Point{29.935523, 52.891566}: "Persepolis", Point{-25.352594, 131.034361}: "Uluru", Point{37.422455, -122.084306}: "Googleplex", } may now be written as: m := map[Point]string{ {29.935523, 52.891566}: "Persepolis", {-25.352594, 131.034361}: "Uluru", {37.422455, -122.084306}: "Googleplex", }

I came into the comments to say that I very much dislike this change. I much prefer the extra syntax to not really knowing what '{29.935523, 52.891566}' actually means.