509 karma · joined September 20, 2013
8 years experience. I like a lot of different languages, but I've mainly worked with Ruby and Python.
Often when I've rationally examined the underlying anxiety it becomes much easier to accomplish things.
Remote: Yes
Willing to relocate: Maybe Amsterdam next year
Technologies: Python, Ruby. Would love to work with something more functional.
Email: kevin@kevinmahoney.co.uk
I wasn't aware of 'throw' and that certainly weakens my argument. You could maybe argue it is an escape hatch in the same vein as unsafePerformIO, but I don't know how it is viewed by the community.
You could argue I'm playing word games here, and I have some sympathy for that argument. What I wanted to get across is checked exceptions ala. Java (although they are too commonly bypassed in that example). Maybe moving it to the documentation section is a good compromise.
I don't even use Idris! I learnt it a couple of days ago for the purpose of this article.
If Idris looks good it's not my fault :)
The most common error I make myself is typos, but those are often (but not always) fixed quickly. The most common mistake I see getting to production is not handling a return value or an exception because it was assumed it couldn't happen.
Types can help with both of these things, and tests less so - because often if you're making an assumption about the return value of a function, it's because you haven't considered the possibility and you don't write a test for it.
A dynamic language can certainly be good enough, but in my opinion never ideal.
I don't think escape hatches added as a practical concern should count against the language, as long as they're used appropriately by the community. You can defeat Rust's guarantees by using an `unsafe` block, and you can defeat Python's memory safety by adding a C extension.
Like I say at the start, if I were going to be strict about this it would be a very short blog post!
You're right about the bottom input. I'll add it to the article.
Although it does 'flatten' the bindings. Defn a, Defn b… is the same as let a = … in let b = … in …
The problem is the further away you go from lists of symbols, the more complicated the AST is to edit and to present to the user, and the more complicated the interface is for the user. It's not an insurmountable problem though.
You can always get instant feedback (types, errors) because your code is always a valid AST. No ambiguous braces etc.
Also things like markdown comments and inline evaluation.
My attempt: http://sediment.io
Also there's another downside to this approach: you lose the ability to do atomic transactions on the application's data.
https://github.com/umermansoor/microservices/blob/master/ser...
N+1 HTTP requests. Ouch. Wouldn't it be nice to be able to do a database join?
Something to bear in mind is that a slight above mediocre film can have a 100% rating if it has wide appeal.
One is a lot easier to unit test than the other, for example.
I haven't written a Prolog program of any complexity myself, but it seems a common complaint is that the programs can be hard to reason about and debug. Your solutions are always running on top of a unification algorithm.
I think my point stands that it doesn't make sense to test for extremely rare diseases because of a self diagnosis.
Testing like that seems pointless to me.
Working: (0.9 * 0.00054) / (0.9 * 0.00054 + 0.1 * 0.99946)