inkel
Joined 15 years ago
Karma
49
Submissions
31
Member since
Jun 22
[ my public key: https://keybase.io/inkel; my proof: https://keybase.io/inkel/sigs/u-xVggkDB_Za1WflnYMWSZNOnSb_gHMhFUuMqabhG4Q ]
View on Hacker NewsRecent submissions
Comment · 4 years ago
You configure with Remote Write [1] to the Mimir instance. Then the Prometheus agents will send the metrics to Mimir.
1: https://prometheus.io/docs/prometheus/latest/configuration/c...
Comment · 10 years ago
I'm pretty sure we haven't lost that many libraries, and I have even seen new ones in recent years.
Comment · 11 years ago
Very interesting... as far as I've read. I've saved it for later reading in my Pocket account. I wonder what the author thinks of me.
Comment · 11 years ago
As long as its performance is not orders of magnitude slower than HAProxy/Nginx, I think it's great that is not your top priority :)
Comment · 11 years ago
Thank you for the explanation. I think it makes sense somehow, however, and high likely because I've never dealt with errors in that way, the _encounter error, crash, restart, continue_ workflow seems a bit awful to me :)
The Haskell solution seems really nice. I've only used Haskell for pet projects and it's one of my favorites languages (though I don't have any proficiency with it,) so thank you for teaching me something else about it.
Comment · 11 years ago
Ok, verbosity I agree. That doesn't have anything to do with being easy or not, I think. I might be wrong. Verbosity can be a pain. Even after reading Rob Pike's article on "Errors are values" [1], I agree with you that the solution is still verbose.
Those numbers you gave, even when you said they're estimates, still seems like made up numbers. I've never used Elixir, so if you could point me to an example so I can be more informed, I'll be grateful :) but also I've read some Go programs (not many, I'm not an expert) and it didn't seem to me that 70% of the code is dedicated to error handling.
Note that I'm not defending Go's position on error handling, I'm asking about error handling in general, what does people mean with "easy way to do it".
Comment · 11 years ago
I've never really understood the "no easy way to handle errors" complaint. I'm not saying it is easy, nor that it isn't verbose (hell, it is super verbose!) but I'm seriously asking: what would be an easy way to handle errors? I'm not asking about how to do it in Go, just how to do it in any programming language.
To me errors are very special constructs, is not a typical return value, as for example a method returning true or false whether the arguments are valid or not, so I expect errors to be something similar (at least semantically) as exceptions in other languages, and in that case, that is, return values that should be deal with in a certain special manner, so I don't expect to deal with them in an "real easy way"™, but in a very conscious and deliberated way.
Comment · 12 years ago
They deserved a better storytelling: https://github.com/inkel/ruster/blob/90f7da1c281bfc1a5fe01cc...
Comment · 12 years ago
As the commit author here, I must confess that it was so painful to write that story that I had to stop coding and go out for a walk. I was devastated...
Comment · 13 years ago
I use it as the only database in most of the projects I've work at my company, using Ohm [1] as our ORM. Usually we don't have use cases with ad hoc queries like `name LIKE '%Smith'`, so it serves our purposes very well. When we need something like that, we integrate with something like Elasticsearch.
Comment · 13 years ago
That won't work as it is with `w.Write`, as it returns two values, but yes, the idea is perfectly valid.
Comment · 13 years ago
Please add plain DOM documentation. I use jQuery, but I also use other libs or none at all, and having access to the DOM API would be wonderful.
Comment · 13 years ago
What was their reaction when you sent them this feedback? Assuming, of course, you did send them this feedback.