Live data from Hacker News

Go version 1 is released

blog.golang.org

131–140 of 168 posts

Re: Go version 1 is released

#131
post #113

Earlier quoted context omitted.

Essential question: what makes it fun?

I can answer just for myself. I don't like to spend time on irrelevant things like "why the binary does not link", "in which shared library this undefined symbol is located" or "how to parse XML", or even plain "why it does not work". With Go I _usually_ have a predictable process of writing a program, when simple things are simple and complex things are reachable. It makes me happy.

Isn't that just because parsing XML in Go is difficult bordering on impossible? Or are you saying there's some other language that forces you to think about XML when you don't want to?

Re: Go version 1 is released

#134
post #125

Earlier quoted context omitted.

I've been putting together a small blogging application with Go just for fun on the side to pick up the language and work on my web design. Its a great language, I'm not using it for half of its capabilities but it very much feels well thought out and the community is very helpful. Key pieces: -My code isn't much more complex than my ruby or python. -The stdlib is pretty fantastic. -Right now tutorials and 'blogs' ar…

Do you know of any recent tutorials on writing web applications in Golang? I saw a slideshow from two years ago, but the content seemed to be fairly abstract for a framework.

It really depends on your needs and the type of application you're making. For example my applications, apart serving a few static html, css and js files, just answer to JSON or JSONP queries. That can be done in a dozen lines of code, all the remaining code will be related to your application logic.

So you just need to look at the net/http API, and at a few code samples. I cannot find the the old golang wiki codelab sample (has it gone away with Go1 ?), so here's an example of a JSONP server that you can reduce to a few lines if you remove the specific application logic and the profiling hook : https://github.com/Canop/braldop/blob/master/go/src/braldops...

EDIT : I found an example on the golang site. If you're not interested in JSON, it will be more suited to your need : http://golang.org/doc/effective_go.html#web_server

Re: Go version 1 is released

#135
post #90

How good is go compare to c/c++ ? ( in terms of speed especially ? ) Can we now say that Google Chrome can be written in Go and it will be faster and/or stable ? ( not saying it is not already. ). Congrats to the team, just started using go yesterday and loving it.

Chrome could not be written in Go, due to the stop-the-world GC. 200ms GC pauses are completely unacceptable for a web browser.

I see a lot of very good reasons for Google not to lose time rewriting Chrome in Go, even without thinking about webkit, but do you have a reference to support this "200ms" assumption ? I never observed this in my programs (which doesn't have the kind of brutal allocations that a browser must have) so I'm curious.

Re: Go version 1 is released

#136

There's something intangibly nice about the main golang.org website. It feels more like a consistent self-contained unit than a lot of such sites do. Well done to whoever does the design and content.

And it's self-contained in the sense that when you code you may simply launch it locally :

    godoc -http=:6060
Of course this will be less needed now that the API are stable but that what really useful those last months, when my go weekly was almost never exactly like the one described at golang.org nor tip.golang.org. I'll still use it in planes and trains though.

Re: Go version 1 is released

#137
post #113

Earlier quoted context omitted.

I can answer just for myself. I don't like to spend time on irrelevant things like "why the binary does not link", "in which shared library this undefined symbol is located" or "how to parse XML", or even plain "why it does not work". With Go I _usually_ have a predictable process of writing a program, when simple things are simple and complex things are reachable. It makes me happy.

Isn't that just because parsing XML in Go is difficult bordering on impossible? Or are you saying there's some other language that forces you to think about XML when you don't want to?

Parsing XML in Go is easy: https://gist.github.com/2234273

My point was that with Go, I have consistently predictable experience. Its standard library is still not the most powerful across the Zoo, but if it has support of something, I know that I can use it w/o a book "libxml2 for dummies".

Re: Go version 1 is released

#138
post #16

Anyone care to share their experience writing something in go? I've toyed with it but not built anything in production. FWIW, the go dashboard ( https://godashboard.appspot.com/ ) has a number of interesting projects.

Tinkercad, http://tinkercad.com, a cloud based solid CAD runs Go for the cluster component. We have a dozen or so different services running in the cluster. Most are distributed for performance and fault tolerance. All the distributed code is written in Go, there is some C for performance critical inner loops.

Re: Go version 1 is released

#139
post #70

Earlier quoted context omitted.

I've said it before and I'll say it again: Somebody really just needs to clone Apple's input method on Linux and Windows. Then you don't need to copy and paste — "é" is just one more keystroke than normal "e", option-e-e. This alone solves probably 95% of the international issues I encounter to the satisfaction of everyone involved.

On X11, the keymap can be set to "US International" which is the same as a stock US layout but with deadkeys and an AltGr key. I find it to be even easier than Apple's input method.

Actually that's my configuration of choice, being Spanish, I use a UK keyboard + AltGr and it's perfect. I find the UK layout more comfortable for programming, and still can type Spanish when needed.

Re: Go version 1 is released

#140
post #70

Earlier quoted context omitted.

I've said it before and I'll say it again: Somebody really just needs to clone Apple's input method on Linux and Windows. Then you don't need to copy and paste — "é" is just one more keystroke than normal "e", option-e-e. This alone solves probably 95% of the international issues I encounter to the satisfaction of everyone involved.

Have you tried to use a Compose Key on X servers? You can use it as follows: Compose-Key e ' => é Compose-Key e ` => è Compose-Key e " => ë Compose-Key e ^ => ê I wonder how this is done on Mac?

  Option-e e => é
  Option-` e => è
  Option-u e => ë
  Option-i e => ê
Post reply on HN