News for hackers. Stuff that matters.
Re:Show HN: Run SSH and HTTP(S) on the same port by hardwaresofton on Wednesday January 21, 2015 @04:44PM (#8925974)
Another interesting and enabling lower-level system tool written in Go.

I don't know if it's because I surf HN , but a lot of really cool "ops" and system stuff seems to be written in Go lately.

Re:Show HN: Run SSH and HTTP(S) on the same port by vertex-four on Wednesday January 21, 2015 @05:55PM (#8926363)
It's generally the sort of thing that would be written in C a few years ago, except C is a horrible language, and Go is the first semi-reasonable replacement. Personally, I dislike coding in Go (far too much of my code ends up being manual error checking), but Rust is on the horizon which might subsume a significant part of this space.
Re:Show HN: Run SSH and HTTP(S) on the same port by vertex-four on Wednesday January 21, 2015 @06:40PM (#8926546)
A showdead comment says:

> I'm fairly amused that you want Rust after whining about Go's error handling.

Fact is, Rust's error handling story is quite nice, with plans to get nicer. It has the try! macro which can automatically convert errors into my own error type with the boilerplate outside the function (thus successfully separating success and error paths to a large extent), and chainable Options and Results for when I need those.

With Go, nearly all of my code revolves around handling errors manually, generally repeating how to handle errors several times over, interleaved with the success code, when 99% of the time it's "return an error".

EDIT: Another comment: I'm well aware of Option and try!, etc in Rust. But overall, Rust doesn't mean that you don't have to think about error handling, it just has different mechanisms for reducing the noise in your code.

Indeed, and I said "most of my code is error handling". I didn't suggest I don't want to think about it - I'd just prefer that I can read what a function does without 2/3rds of the lines in that function being error handling, and thus obscuring what the function does in the success case.

Re:Show HN: Run SSH and HTTP(S) on the same port by IgorPartola on Wednesday January 21, 2015 @09:11PM (#8927113)
I'm sorry you don't like C. I find it to be a great language for the kinds of things it's good at. I always have a lot of fun when I program using C. No, it's not the most productive language to use, but in some cases you'll be hard pressed to find an alternative; think memory constrained embedded systems, or even VM's, where you are not allowed to use malloc.
Re:Show HN: Run SSH and HTTP(S) on the same port by adnanh on Thursday January 22, 2015 @09:26AM (#8929245)
You might want to read [1] :-)

[1] http://blog.golang.org/errors-are-values

Re:Show HN: Run SSH and HTTP(S) on the same port by AceJohnny2 on Wednesday January 21, 2015 @04:50PM (#8926012)
That's kind of the segment to Go was aiming for (systems/scalable)
Re:Show HN: Run SSH and HTTP(S) on the same port by hardwaresofton on Wednesday January 21, 2015 @05:39PM (#8926290)
Right, except the other comment ("it's trendy") is casting some doubt on whether it's just because they needed a systems language, when I made my original comment I was kind of wondering out loud which force was really driving Go adoption...

I personally am using Go on some big projects and am enjoying it, but I personally noticed so much awesome systems stuff being made in go

Re:Show HN: Run SSH and HTTP(S) on the same port by ams6110 on Wednesday January 21, 2015 @04:49PM (#8925998)
It's trendy.
Re:Show HN: Run SSH and HTTP(S) on the same port by vhost- on Wednesday January 21, 2015 @06:37PM (#8926530)
Or it's handy.
Re:Show HN: Run SSH and HTTP(S) on the same port by stock_toaster on Wednesday January 21, 2015 @07:46PM (#8926806)
Or both! Trendy and handy are not inherently mutually exclusive.