4 ms·

Django fails, Ruby fails, Java is dead...what's next? sigh

• tvon 17y ago
  No offense but I'm getting the impression that you (and grandalf) haven't read past the title here. Nobody is saying "[Django|Rails] fails as a tool/project/framework", the topic here (and in the related submission about Rails) is how do the tools we use respond to error, how clear is the message we are given and weather or not these responses could be clearer or friendlier. In short, "useful error messages". I think it's an interesting and useful topic of discussion and I submitted this link to be complementary to the story about Rails (though I admit I probably should have just added it in a comment to that story), not to some how put Django against Rails (which seems to be a point of misunderstanding) or to put Django itself down (which wasn't anyone's intent).
  • jister 17y ago
    Yes I didn't read past the title because the title itself is a turn off to me.
    • andrewljohnson 17y ago
      Then please, don't comment. The cliche "don't judge a book by its cover" comes to mind. Do you often judge articles by their titles and then proselytize to your peers?
      • rbanffy 17y ago
        To be fair, he could ask if the article is worth reading because he felt turned off by the title. The title is at least a bit inflammatory and the article is the complete opposite of it.
      • jister 17y ago
        No I don't but titles like this are common these days. It would have read the whole article if it has a different title.