As far as a way to save character count to include a more accurate title, eliminating the “300,000-year-old” part seems like it would work.
2,032 karma · joined April 1, 2013
http://github.com/adnelson
As far as a way to save character count to include a more accurate title, eliminating the “300,000-year-old” part seems like it would work.
Well for one thing, sometimes projects are just for fun, or to explore uncharted territory, without thinking about a specific use case. For another, there are definitely use cases for proofs in code, as verified software appears in a variety of domains. It’s not likely to make its way into the average CRUD app any time soon, but that doesn’t mean it’s not useful.
> Haskell is barely used in the first place, and even less for highly safety critical software.
“Barely used” is relative. Compared to java or python, sure. But there are untold millions of lines of Haskell code running in production right now. Besides, in my humble opinion Haskell should be used more, whether or not it is (right now). And in any case Haskell has had a big influence on many other more popular languages, and/or libraries, and this could one day be another example of that.
Can you (or someone else) ELI5 what makes containers insecure? Not a low level Linux or security expert.
A low-speed broadband plan (or even dialup) would serve those customers fine, no?
> As for caps - which do you think would sell people better: "You have full access to anything on your email" vs "You can download 500 mb of data a month"
What if those emails link to some other site on the internet? Or contain photo or video links? Does it still count as “full access” if things slow to a crawl in those cases? With email being so small anyway, how does that differ in practice from just a low speed plan? It could still be marketed as “access to everything in your email.”
> And what will happen to their service when the grand kids come over and want to watch netflix?
This question itself seems to undermine your point. What would happen in that situation, on a plan like the one you’d like to sell?
However there's no way in Haskell (short of low-level type system tricks) to check that a function with an argument of type `Int` actually receives an `Int` when it is called. There's no need to, because it is guaranteed by the type system. The strength of these guarantees, coupled with the ability to define rich, expressive types, are what makes Haskell programs very robust. For example you can represent all possible results of a valid JSON parse:
data Value
= Object (HashMap Text Value)
| Array (Vector Value)
| String Text
| Number Float
| Bool Bool
| Null
Which variant of this type is actually encountered will not be determined until runtime, so the program is required to respond to the different cases; however a function which takes type `Value` will never need to worry that it doesn't actually receive one of the above variants at runtime.That said, I agree that the article doesn't spend a great deal of time explaining the concepts, whether blockchain itself or the category theory it's using, leading to a sense (for me) of being overly terse and coming across as a bit pompous. Although, I realize that for a certain audience there's nothing pompous about this at all and it might seem perfectly reasonable.
Well, is the bluetooth as good when your wife is driving the Rav4?
Reading this part sent chills down my spine. If anyone has seen the movie Antichrist, they might recall a particular scene that echoes (and was perhaps inspired by) this anecdote. I truly think losing ones mind is one of the most terrifying things to imagine -- the very fabric of reality coming apart at the seams.
EDIT: probably the only gripe I would make is to have comma-separated lists instead of having to use parentheses to separate non-atomic expressions.
This is might be seen as an instance of "pulling the ladder up behind you".
b) It's easy to remember
c) Many people are legitimately angry about this kind of thing and using profane language (such as it were) seems warranted
PBV and PBR seems to be a tiny distinction and yet, we have blog posts and interview questions and online debates about whether a language falls into the first or second category.
I hope this isn't taken as a frivolous or mean-spirited comment, but the code samples on the blog would be much more readable with some kind of syntax highlighting.