1,394 karma · joined March 22, 2014
Computing fib with memoisation from 1 will certainly be faster than (parallel) recursion without memoisation and data sharing.
What makes you think that those are the same people? At first blush it seems like people in favour of easier access to vote and easier access for the disabled would be the same people that advocate for more inclusive access to shops.
When you write TS, you are (literally) writing JS, except that you are also writing miniature contracts (types) which are shared between components of the system and between authors of the code. This helps to ensure that the JS everyone is writing is mutually compatible, and that pieces of JS that should fit together actually do.
The idea that something's not part of the web stack if you can't throw it at a browser seems a bit weak; especially as, in this case, you can throw a subset of what you write at a browser and have it perform as intended.
We in Canada or the United Kingdom might not notice, but I'm pretty sure those in Texas or Nigeria will.
I wonder if the author has anyone heard someone make the reverse claim.
In this case you can think of a monad a bit like a computational context. If one is not present, you simply cannot[^1] instruct a Haskell program to perform those operations in a type safe way even if you give it a valid database connection identifier.
[1] Well, you can, but if you do you're explicitly taking away all the safeguards that Haskell introduces, and it would never pass code review.
- REPL ergonomics, where every action I could think of makes sense as a REPL command, leading to very small incremental pieces.
This is the only point I would dispute. The GHC interpreter `ghci` is very powerful and offers a lot of the same upsides. Beyond this, the language server offers in-code evaluation with "-- >>> expression" syntax, which is a cool new step towards fast looping UX. Clojure is certainly great at this, but I'd say Haskell is not far behind.
On the other hand, there are two "child" languages of Haskell for the job: Elm, which is a frontend-focused language, and PureScript, which compiles to JS and is designed for that use case.
Haskell has decent interop with C/C++ languages, but certainly nobody uses haskell because of that.
In fact, nearly all of the claims made about Clojure here can be made about haskell more strongly.
I've half a mind to do a direct comparison on every point. I'd be interested to hear the author's thoughts on the similarities and differences.
[^1] With the obvious exceptions of s-expressions, java/js interop, and "subjectively good design".
It will create a moat between "worthy" and "unworthy" scientific journals - those which the Indian government is willing to support financially and those which it is not. There may also be some risk that Indian government will give preferential treatment to journals that publish more from their own institutions.
Unless by "get rid" you mean "completely eradicate", which is not feasible under any system.
Computers, by contrast, do exactly what they are told and no more.
This is why it takes an engineer to craft a computer program, but a politician can craft a law.
It's very unhealthy.
Where it fails is in reporting the problem in a meaningful way. This is, of course, very difficult to accomplish, since there is no nice mapping from line-of-TeX to visual error. What's more, any tool which could provide such an error would be so constrained as to be useless for typesetting.