HTML, JavaScript and CSS are the worst things that happened to mankind right after C++ - the language which most browsers are written in - horrible, rotten, bug ridden things.
Looking from the top of todays technology some can observe subtle transition from desktop to mobile to wearable electronics (intelligent clothes). From this point of view Web becomes obsolete. Everyone prefers native apps on mobiles. Honestly I can't see bright future for Web in wearable electronics world now. I'm almost 100% sure there won't be HTML inside.
Web was designed with desktop in mind. The further form desktop the less Web. The future is not on desktop. C forever? Low memory footprint and small executables are still there.
It is Haskell spam wave. Every time there is something about FP lots of Haskell bigots jump out. Well, you could ignore this movement, but you cannot because beneath all of this at its core Haskell is pure immutable BS and actually it is first language with built in bugs because it wouldn't even run without them.
Of course you can leak space in every turing complete language even on purpose, but in case of languages with lazy evaluation (like Haskell) you are no longer able to trivially reason about your programs behavior until execution on real data in real environment.
I agree that Haskell has some good (old) ideas and it is pleasant to Sunday programmers.
Unit test will not detect everything. You need real data under heavy load for Haskell. This is a _fact_.
Most of you here should stop writing BS about Haskell and how it is going to save the world.
> I never said that. Your argument was that this is specific to Haskell which is not.
It is specific to lazily evaluated languages, especially Haskell. To test Haskell program you will need a real environment under heavy load - maybe Google or Amazon could afford it. Tiny unit tests which are perfect for strictly evaluated languages won't detect these kid of bugs.
How can anyone seriously code in a language which introduces new kind of bugs which cannot be detected by any test until running in production on real data when it is already too late?
I'm able to hack fully working UI without restarting my app in minutes while you are still clicking at your first 'button' in XML. Startup time is very slow, but Android nature makes it 'faster' next time, because Android does not terminate applications on exit by default.
So don't lie that 'it is not suited'. There are some fools that actually use it.
First rule of maintanence: readable code. I should be able to read code after short introduction. I remember it took me 1h (after Sussman lecture video) to read Lisp. It is several weeks now since I'm reading Haskell tutorials and docs and still have problems to understand code advertised as "what real world Haskell looks like".
It is the only language I know of which makes trivial problems hard and hard problems impossible.
Because of its syntax you have to write 10x as much documentation, as experiment shows and I can confirm this from my own experience. Haskell is full of BS.
Haskell's code is not far away from APL. Lots of Haskell code uses single letters instead of descriptive names. This makes it a lot harder to read and forces lengthy documentation:
reverse (PS x s l) = unsafeCreate l $ \p -> withForeignPtr x $ \f ->
c_reverse p (f `plusPtr` s) (fromIntegral l)
People who write code like this should be banned. Code should be written in a way to be easily read by people, not a compiler. This is not a coincidence that there are 500 lines of documentation. This is how typical Haskell code looks like.