1,394 karma · joined March 22, 2014
- Social priming does not replicate;
- Social psychology has a replicability rate of 25%.
IMO Haskell remains as the go-to language for teaching functional programming and for experimenting with PL concepts. Long may it remain.
That said, I'm not convinced that giving it a name is enough to make people consider it dangerous.
I am disputing your random assertion that, if advertising became less effective (say by removing targeting), the quantity of advertising that people see would go up significantly.
The amount of adverts that people see currently is not based solely on their economic value - it is based on their value relative to how much people are willing to put up with being advertised to. If advertising becomes less valuable, that doesn't mean people will suddenly put up with more of it.
Indeed, if the value of adverts went down, I would expect to see fewer advertisements, not more, since the value of showing them to people is now less relative to their willingness to put up with them.
> Ergo - unless you are willing to pay for apps - you might now see 10x more ads appearing on pages than otherwise.
I'm afraid that this is nonsense. If the economic value of selling bread went down by 10x, do you think people would start offering you 10x as much bread?
fib = \case
0 -> 0
[...] let f lst = lst
& map normalize
& filter (\x -> x > 0)
& average
Which is barely different from your second presentation. (EDIT: just in case you think I'm ass-pulling here, this is fairly idiomatic code that I'd certainly write in prod! See another comment I posted earlier this week...) xs =
5
& (\n -> take n [1, 2, 3])
& filter (/= 1)
& head
& (\n -> take n [1, 2, 3])Anti-mask-wearers and anti-vaccinators have conclusively shown that this cannot happen in practise.
Indeed, I think the ideal mode would be to introduce a 'protected' flag, similar to Wikipedia's, and for which particular care is taken when constructing and assessing definitions. This will allow UD to act as a reference for the topics where it is most relevant, and not yet another vector for abuse.
[1] https://www.wolframalpha.com/input/?i=10+furlongs+in+attopar...
I'm only saying in relation to the idea of "reading Haskell code", it is possible to understand how they work (at the shallowest level) by analogy to `forEach` and to shell syntax.
Shell syntax also doesn't explain important constructs like currying, partial application, etc. But it's good enough that someone can read "boring" haskell code without being intimidated and turned off.
If you've written shell scripts before, you understand how Haskell functions calls are written.
If you've used `forEach()` in imperative languages then you understand functors.
These two things alone are half of the groundwork you need to read basic Haskell code! Of course, the fundamental underpinnings of the language will not appear just from a surface reading of the code, but if you're a person who learns by example then the above two are more than good enough.
If you're more of a linear learner then Learn You A Haskell [1] is an excellent, if earnest, introduction to the language. Depending on your confidence level you may be able to skip a decent way in.
Sadly I am unconvinced of this. If it were true, there would not be an immediate and significant push to make `haskell-language-server`.
Having tried many times to get `hie` working, I can say that it's a pain in the bum.
Suppose I have 12 projects, one made every month for the last year. Each of these 12 will be using a different stack resolver, possibly with different ghc versions. As a result, I will need to compile and use up to twelve different versions of hie, and make sure that the correct one is on my $PATH depending on which project I have open.