Re:Self hosted uptime robot alternative written in go
by quaffapint on Wednesday November 11, 2020 @12:53PM
(#25060772)
It's funny when people post things here that are written in go, they always want to let you know that. Nothing wrong with that, I just don't see it as much with other languages.
[ Parent
| on HN ]
Re:Self hosted uptime robot alternative written in go
by bananadrama on Wednesday November 11, 2020 @11:02PM
(#25066301)
When I see "in Go", I infer:
* it's likely easy to build/package, since deep dependency trees don't occur much in practice. Alternatively, there could be a binary available on Github.
* it's going to behave similar to https://12factor.net/
* it's going to be working in 3 years time (since the language and library authors value backwards compatibility)
* I can contribute to it, and not expect it to use some obscure async/web library that makes contributions harder.
They're all important to me. I think Go is a bit uninspiring as a language, but maybe I don't need that.
Re:Self hosted uptime robot alternative written in go
by xyzzy_plugh on Wednesday November 11, 2020 @01:34PM
(#25061268)
I wish this kind of thing was more prevalent, actually. I'd probably avoid clicking through most links for projects written as node.js applications.
Re:Self hosted uptime robot alternative written in go
by weego on Wednesday November 11, 2020 @01:50PM
(#25061466)
Haskell, Rust and Go are the big 3 for name dropping at the moment.
Those come after being vegan but before crossfit in 'what I do is a personality' bingo.
Re:Self hosted uptime robot alternative written in go
by jamil7 on Wednesday November 11, 2020 @03:47PM
(#25062786)
Arch Linux is missing from your bingo card.
Re:Self hosted uptime robot alternative written in go
by drcongo on Wednesday November 11, 2020 @03:52PM
(#25062841)
And Nix
Re:Self hosted uptime robot alternative written in go
by 0xdeadb00f on Wednesday November 11, 2020 @06:03PM
(#25064073)
I honestly think Nix has gotten bigger than Arch in that way. "BTW, I use Nix" should be a thing too.
Re:Self hosted uptime robot alternative written in go
by agentwhy on Friday November 13, 2020 @03:20PM
(#25086983)
So, when can people say they really use nix? Can you just look in their github repos and call it a day?
Re:Self hosted uptime robot alternative written in go
by maxioatic on Wednesday November 11, 2020 @02:18PM
(#25061802)
Haskell? I feel like I haven't seen it much. Interestingly though I just started to learn it, so I would like to see it more.
Re:Self hosted uptime robot alternative written in go
by GordonS on Wednesday November 11, 2020 @02:24PM
(#25061862)
I know Rust and Go are at the peak of their hype-cycle here on HN, but I still personally appreciate the language being mentioned in the title - if it's a language I use, I will naturally be more interested.
Re:Self hosted uptime robot alternative written in go
by edoceo on Wednesday November 11, 2020 @02:36PM
(#25062009)
Same filter works the other way too for the skip operation
Re:Self hosted uptime robot alternative written in go
by laptop-man on Wednesday November 11, 2020 @01:18PM
(#25061058)
op here, I only put the language as when I self host anything I like knowing how to extend the program and be comfortable with the lang
Re:Self hosted uptime robot alternative written in go
by cle on Wednesday November 11, 2020 @01:33PM
(#25061251)
We see it with whatever is trendy, lately it's been Rust. I don't see anything wrong with it, usually people are proud of it because they used the project as a way to learn a new technology, which is why it's in the title (I don't know if that's the case here).
Re:Self hosted uptime robot alternative written in go
by ikkah on Wednesday November 11, 2020 @01:08PM
(#25060952)
part of the reason could be to emphasize that single binary would be easy to operate
Re:Self hosted uptime robot alternative written in go
by mekster on Wednesday November 11, 2020 @06:07PM
(#25064104)
You'd expect it to be easy to deploy if it's written in go. I don't see a problem mentioning it.