Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Go version 1 is released

blog.golang.org

Post reply on HN
Print view View original

121–130 of 168 posts

Re: Go version 1 is released

#121

Post by makecheck »

I'm disappointed that after starting from scratch they created a "modern" language that requires a module import just to print (and corresponding extra syntax for that namespace when making the call).

How could this not have seemed incredibly clunky after using it for just a little while? It's the same frustration one feels when simple print-outs fail in C++ because you forgot to "#include ". Sometimes you just want to print stuff no matter what file you're in. Languages should make it almost impossible to fail at extremely common tasks. It's these little things that make Python and Perl enjoyable to program in, and these little things that every new language should begin with!

Re: Go version 1 is released

#122

Post by jesstaa »

TylerE wrote: post #60

Well, they got (at least) one thing exactly right: Doing away with the "toolchain". Having one command that can figure out how to build your code, including downloading external dependencies, is really nice. Pity about the whole "not having generics" thing though.

Apparently there is a generics prototype in the works, it was too much of a big change for Go1. It will probably be in Go2.

Re: Go version 1 is released

#123

Post by nakkiel »

chc wrote: post #70
huhtenberg wrote: post #59

Earlier 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.

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?

Re: Go version 1 is released

#124

Post by enneff »

makecheck wrote: post #121

I'm disappointed that after starting from scratch they created a "modern" language that requires a module import just to print (and corresponding extra syntax for that namespace when making the call). How could this not have seemed incredibly clunky after using it for just a little while? It's the same frustration one feels when simple print-outs fail in C++ because you forgot to "#include ". Sometimes you just want…

One of the design goals of Go is that the language is small. There's nothing so special about string formatting that it should be part of the language proper, and it would add a lot of complexity to the spec if it were.

With that said, there are built-in print and println functions that write to stderr, which are useful for debugging. That would seem to address your complaint. The fmt package is a lot more fully-featured than the built-ins though.

http://golang.org/pkg/fmt/

Re: Go version 1 is released

#125

Post by lhnn »

peregrine wrote: post #25
mace wrote: 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.

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.

Re: Go version 1 is released

#128

Post by makecheck »

enneff wrote: post #124
makecheck wrote: post #121

I'm disappointed that after starting from scratch they created a "modern" language that requires a module import just to print (and corresponding extra syntax for that namespace when making the call). How could this not have seemed incredibly clunky after using it for just a little while? It's the same frustration one feels when simple print-outs fail in C++ because you forgot to "#include ". Sometimes you just want…

One of the design goals of Go is that the language is small. There's nothing so special about string formatting that it should be part of the language proper, and it would add a lot of complexity to the spec if it were. With that said, there are built-in print and println functions that write to stderr, which are useful for debugging. That would seem to address your complaint. The fmt package is a lot more fully-feat…

Thanks for pointing it out. I wish they used that in their "hello, world" example because 'println("hello, world")' leaves a much better first impression of simplicity.

I generally like to see things kept simple. But formatting is a common need and they've actually made things less simple by providing both fmt.Println() and println(). It means the same program will inevitably contain both, depending on who did the editing. There are times when a feature is so basic that it really should have exactly one way to do it, and I think printing is in that category.

Re: Go version 1 is released

#129

Post by enneff »

makecheck wrote: post #128
enneff wrote: post #124

Earlier quoted context omitted.

One of the design goals of Go is that the language is small. There's nothing so special about string formatting that it should be part of the language proper, and it would add a lot of complexity to the spec if it were. With that said, there are built-in print and println functions that write to stderr, which are useful for debugging. That would seem to address your complaint. The fmt package is a lot more fully-feat…

Thanks for pointing it out. I wish they used that in their "hello, world" example because 'println("hello, world")' leaves a much better first impression of simplicity. I generally like to see things kept simple. But formatting is a common need and they've actually made things less simple by providing both fmt.Println() and println(). It means the same program will inevitably contain both, depending on who did the ed…

Your position is not very pragmatic, and taking such a hard line is rarely productive.

The fmt package does a lot of stuff. Check out the link I provided above. To put all that stuff into the language spec - and then foist responsibility of writing and maintaining that code onto every implementation of the language - would be crazy. So it seems a good idea that the fmt package should exist and that it should be written in Go.

On the other hand, it's nice to be able to print when working on low-level libraries where fmt is not available (syscall, os, etc). The print and println functions service this need, and that's really all they're used for apart from temporary debugging prints.

It would be a mistake to use the built-in println in the hello world example because it would demonstrate precisely the wrong use of the built-in functions. Hello world should print to standard output and it should use the standard means of formatting strings. In Go, that is fmt.

There are a few of such compromises in Go (not many, though). Sometimes you need to put your ideals to the side in the name of simplicity and pragmatism.

Re: Go version 1 is released

#130

Post by krasin »

huhtenberg wrote: post #99
maaku wrote: post #63

Earlier quoted context omitted.

Learn how to use your ALT-keys.

Do tell how I would enter Ж with my Alt-keys. Or better yet, tell me how to tell apart 'e' and 'е' (one of them being a Cyrillic letter.)

A popular Russian CRM (1С) has a scripting language where the code looks like:

СпрСотр = СоздатьОбъект("Справочник.Сотрудники"); СпрСотр.Новый(); СпрСотр.Наименование = ФИО; СпрСотр.Должность = Должность; СпрСотр.Оклад = Оклад; СпрСотр.ДатаПриема = ДатаПриема; СпрСотр.Записать();

It's not surprising they were not able to expand to the Europe market.

Post reply on HN