4 ms·

Those are all client usability concerns, and none of them are stack intrinsic.

• mark-r 9y ago
  I think the point was that user doesn't care about your stack, but they care about the consequences of the stack you've chosen. It's a subtle but important distinction.
  • scott_karana 9y ago
    Of course. My point was that it's fairly common to write slow/unsuitable applications in spite of a stack's strengths, while stack limitations (or strengths) are generally overstated, depending on trends. Proper engineering and design are required no matter what you choose. No silver bullets ;-)
    • kerkeslager 9y ago
      There are no silver bullets, but there are wooden bullets that are totally ineffective.
• kerkeslager 9y ago
  Have you figured out a way to make a mature implementation of the JVM start up fast? Nobody else in the industry has. Is there some way I know of to package Flash games so that Firefox users can play them without downloading Flash? I get that done of the examples I mentioned are arguable, but some of these are pretty unambiguously stack intrinsic. Some usability concerns cannot be addressed in some stacks.