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

Go 1.6 is Released

blog.golang.org

Post reply on HN
Print view View original

361–367 of 367 posts

Re: Go 1.6 is Released

#361

Post by sacado2 »

randallsquared wrote: post #320
dilap wrote: post #308

Earlier quoted context omitted.

A reasonable attitude for client-side code, perhaps, ('oh it blew up, I'll reopen the app and try again/rerun the script'), but I think not so reasonable for server-side code.. There's element of personal preference here. The longer I program the more I favor systems and styles that minimize unexpected problems; explicit error handling is very much in that vein. Another complication is that the word "error" actually…

> A reasonable attitude for client-side code, perhaps, ('oh it blew up, I'll reopen the app and try again/rerun the script'), but I think not so reasonable for server-side code.. This seems like a response to something that wasn't my comment. I even went out of my way to state what I thought might be obvious: "pay as much attention as required to make things work". Handling errors is a given in this thread. The quest…

> errors of type (1) are not the purpose of your code. They're problems that prevent your code from fulfilling its purpose.

I don't really agree with that. In a module that checks whether a user has the right credentials to perform a given task, for instance by checking the used IP is correct and a correct password is given within 3 attempts (or else the account is blocked), dealing with errors (checking password is valid, checking IP is valid, checking account is not blocked, blocking it if needed) is the purpose of the module.

This is the same with any kind of automaton. Knowing when you go into an error state and how you get out of it is part of the problem you deal with.

Re: Go 1.6 is Released

#362

Post by sacado2 »

sriram_malhar wrote: post #343

Have been using Go since its release, and like the deployment experience, the feeling of solidity of putting together a tight system. The toolchain is great. 1.6 is yet another Solid release in that direction. Thank you all. However, the _language_ doesn't give me much programming pleasure alas. Since there is plenty of time for Christmas, here's my syntax wish list :) '?': C's if-then-else operator. Block-syntax for…

Sum types don't play well with zeroed values by default. What is the zero value of a sum type ?

Pattern matching doesn't work well without sum types.

So don't hold your breath.

Re: Go 1.6 is Released

#363

Post by krakensden »

paulddraper wrote: post #339
krakensden wrote: post #312

Earlier quoted context omitted.

Go was designed to make tooling easy, and that tooling has been written: https://github.com/nsf/gocode/blob/master/README.md And it's pretty trivial to get Vim super integrated with go: https://github.com/fatih/vim-go/blob/master/README.md

And you consider that an IDE, right? An Integrated Development Environment?

No, and nobody else does. There's a lot more baggage and feature check-boxes tied up in that name.

Re: Go 1.6 is Released

#364

Post by lowmagnet »

autoreleasepool wrote: post #338
d4rkph1b3r wrote: post #323

Earlier quoted context omitted.

Eh, most of my post was an emotional response because of my hatred of the java language. Your reasoning I mostly agree with. I do agree, the JVM is a solid language choice. I also don't think going with too esoteric of a language is a good thing. Probably a little early to bet a company on Idris or Ceylon. Still, I apologize for my tone. Let me give you purely anecdotal information about me, so you can at least see w…

> Still, I apologize for my tone. It's all good! I've had the same heat of the moment responses on here, so I get it. But thanks anyways. > If a startup is using java, I think to myself 'why java? why not Scala, F#, or C# at the very least?'. Usually the answer is 'scala/F# programmers are too hard to find', but that's not really true, what they mean is they're not willing to pay the 20% premium for them. That's a st…

Might I suggest starting with Java, but moving into Kotlin after getting the basic syntax of Java down? I have a good feeling about the language after translating a system of classes to it recently. About 60% of the code vanished, and working in it let me free up a few concepts for the resulting java code after doing my thinking in Kotlin.

Most of the stuff Kotlin does, absent much nicer functional syntaxes, I can do in Java 8 already. I think Kotlin does a better job at expressing it. I especially like the first-class nature of functions, and I know I'm just in the early days of understanding it.

Re: Go 1.6 is Released

#365

Post by twistedpair »

EugeneOZ wrote: post #311
twistedpair wrote: post #287

Earlier quoted context omitted.

As long as you don't want your queries parameterized/precompiled and inputs escaped, rolling your own SQL by hand should work.

Do you really think I use non-escaped queries? :) Really funny :) Read about prepared statements.

> "queries parameterized/precompiled and inputs escaped"

Yep. That's exactly what I was talking about. You know that's what prepared statements do, right?

Re: Go 1.6 is Released

#366

Post by EugeneOZ »

twistedpair wrote: post #365
EugeneOZ wrote: post #311

Earlier quoted context omitted.

Do you really think I use non-escaped queries? :) Really funny :) Read about prepared statements.

> "queries parameterized/precompiled and inputs escaped" Yep. That's exactly what I was talking about. You know that's what prepared statements do, right?

Yes, I know, and I use them in raw queries.

Re: Go 1.6 is Released

#367

Post by d4rkph1b3r »

lowmagnet wrote: post #364
autoreleasepool wrote: post #338

Earlier quoted context omitted.

> Still, I apologize for my tone. It's all good! I've had the same heat of the moment responses on here, so I get it. But thanks anyways. > If a startup is using java, I think to myself 'why java? why not Scala, F#, or C# at the very least?'. Usually the answer is 'scala/F# programmers are too hard to find', but that's not really true, what they mean is they're not willing to pay the 20% premium for them. That's a st…

Might I suggest starting with Java, but moving into Kotlin after getting the basic syntax of Java down? I have a good feeling about the language after translating a system of classes to it recently. About 60% of the code vanished, and working in it let me free up a few concepts for the resulting java code after doing my thinking in Kotlin. Most of the stuff Kotlin does, absent much nicer functional syntaxes, I can do…

Why kotlin and not scala? Kotlin is like Scala--, in addition to not really having a job market.
Post reply on HN