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.
Go version 1 is released
101–110 of 168 posts
Re: Go version 1 is released
#102What happened to the ebnf package?
Re: Go version 1 is released
#103Anyone 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.
I have written a bit of Go. It strikes me as sort of the Unix of programming languages. It's very opinionated, takes some overarching concepts, mostly channels and interfaces, then proceeds to thoroughly not care what you think about it: refuses to have generics, lambdas and tail-call recursion like a pro. The polar opposite of design by committee. It even enforces a True Brace Style to keep the parser simple! Techni…
Go does have lambdas: foo := func() { ... }
Re: Go version 1 is released
#104I've been using Go for 2 years now. It's been a lot of fun. It certainly brought fun back into programming for me. Very happy to see the 1.0 release hitting the public. Congratulations to the Go team and contributors for a job very well done!
My god. Go is _so_ much fun to program. Apart from it's technical pedigree this is its most remarkable feature.
Essential question: what makes it fun?
Re: Go version 1 is released
#105Anyone 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.
I've built a production entity resolution system using 100% Go. It implements a map/reduce model with many workers and multiple (for failover) masters. All data is held in memory for speed purposes. Things that are amazing about go: fun and fast to develop in; beautifully designed (rockstart founding team, than you!); RPC, net channels, and maps and strings, to name a few. The ability to quickly create servers to host business logic. Interfaces and "inheritance" model are both very elegant and clean. Compile times rock. Everything was built with the standard Go (pre 1) install; not a single other package was needed--the very complete standard lib is a blessing.
Two "could be better" points. Go has a hard memory limit per instance of ~ 15 GB; bad when you want to pin lots of data in memory. Russ says this issue is being tracked (2142) and will get fixed after Go 1 gets out the door. So patience will fix this one.
Second, there needs to be more examples of Go code out int the wild for others to share and look at. Using the template package got me stuck, for example, and seeing code cleared up my issue but that was hard to find. This we can all help with by using Go and talking about it. Again patience takes care of this issue as well.
Other than these items, do yourself a favor and start using the magic that is Go!
Re: Go version 1 is released
#106Anyone 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.
I have written a bit of Go. It strikes me as sort of the Unix of programming languages. It's very opinionated, takes some overarching concepts, mostly channels and interfaces, then proceeds to thoroughly not care what you think about it: refuses to have generics, lambdas and tail-call recursion like a pro. The polar opposite of design by committee. It even enforces a True Brace Style to keep the parser simple! Techni…
Why would you move from Haskell to Go? There's a night-and-day difference between them. I don't understand why you'd switch to a language because of the features it's lacking, unless you think those features are a bad thing (and I have yet to see a reason why generics and TCO are a bad thing).
Re: Go version 1 is released
#107Earlier quoted context omitted.
The day Androïd will be written in go, we will see a significant performance boost and battery lifetime extension. I don't program for Androïd just because I can't bare eclipse. An IDE as simple and efficient as QtCreator would generate a conversion tsunami.
Nonsense. You would hate Android written in Go, because of the GC pauses. Dalvik has a concurrent garbage collector; Go has a stop-the-world one.
Only because that's all that's been implemented. They're well aware of GC and compiler optimizations being a target for future versions of Go.
Re: Go version 1 is released
#108Earlier quoted context omitted.
répertoire Never gave much thought to Go's UTF8 support, but this makes me think that it might've been better limited just to the string literals. The last thing I want is to patch other person's code by copy-pasting original variable and function names, because all I have is a standard US keyboard locale.
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 Lion and later, it's even easier. Just hold down the e key and you get a list of the various accented versions.
Granted, it doesn't work in the Terminal, or certain other apps that don't use the standard text edit widgets (e.g. MacVim, TextMate), but in those apps you can continue to use the old ⌥e+e trick.
Re: Go version 1 is released
#109There'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.
[deleted]
Re: Go version 1 is released
#110There'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.
Thanks! :-)