3 ms·
There's a reason it's called a demo. No one is actually suggesting that you use this as a proper stopwatch. Everybody already understands the limitations you sp
by talmand 14y ago
There's a reason it's called a demo. No one is actually suggesting that you use this as a proper stopwatch. Everybody already understands the limitations you specified.
- Stratoscope 14y agoAnd an impressive demo it is. But I'm fairly certain that not everybody understands the limitations I mentioned. You and I and hopefully most of the folks here, sure. But spend some time on the css-discuss mailing list [1] for an eye-opener. Many of the members of that list seem to favor CSS-only solutions even when the user experience is inferior to what you could achieve with a sensible blend of CSS and JavaScript. And they're not just talking demos, they put this stuff into production. I don't understand that point of view at all. I want the best solution for the user, and I'll use whatever tools are necessary to build it. [1]: http://www.css-discuss.org/ http://www.css-discuss.org/
- talmand 14y agoWell, in the situation you are describing I most certainly agree. CSS-only solutions tend to be quite lacking in real-world terms. But this was a demo and I saw no indication it was anything other than that. If you were meaning to aim your comment to people that think the way you describe then I apologize, but I didn't get that from your comment.
- Stratoscope 14y agoNo apology needed! I appreciate your pointing out that the intent of my comment was unclear. That is valuable feedback indeed.