> Until then I reserve the right to consider the current Haskell/FP craze the biggest amount of bullshit since the Java/OOP craze.
You make it sound as if the consensus following the 'Java/OOP craze' was that the naysayers had it right all along, and we should all go back to C/ASM. Well, it wasn't. Even though it was overhyped, I bet most developers (myself included) would still choose Java over C. Of course this means we would take a performance hit, but for the vast majority of jobs it wouldn't matter one bit.
At the tail end of most of these 'crazes' (Java, Python, Ruby, etc.), once the dust settled we ended up with something that is in many ways far superior to what came before it (certainly when compared with C).
You make it sound as if the consensus following the 'Java/OOP craze' was that the naysayers had it right all along, and we should all go back to C/ASM. Well, it wasn't. Even though it was overhyped, I bet most developers (myself included) would still choose Java over C. Of course this means we would take a performance hit, but for the vast majority of jobs it wouldn't matter one bit.
At the tail end of most of these 'crazes' (Java, Python, Ruby, etc.), once the dust settled we ended up with something that is in many ways far superior to what came before it (certainly when compared with C).