News for hackers. Stuff that matters.
Re:SproutCore 1.4 has been released by chc on Monday September 20, 2010 @06:01PM (#1710657)
Dav's experiment is interesting, but I don't see how these static pages come anywhere near touching "we do web applications not websites so we don't have to bother about non-javascript". A rich interface simply will not work with its interactivity taken away. Even something as simple as a selection rect fails under such a system. It would require a separate interface, and now we're back to where SproutCore gets us.

That is the dilemma of progressive enhancement. If you choose to do it, you must either limit your enhancements or support two separate interfaces.

Re:SproutCore 1.4 has been released by Isofarro on Tuesday September 21, 2010 @02:04AM (#1711651)
"It would require a separate interface, and now we're back to where SproutCore gets us."

That's precisely the downside a JavaScript library or application development platform should be seeking to avoid: forcing developers to write two versions of their service - one with SproutCore and one without.

In a startup world, I'm surprised that someone on a tight budget can afford this approach and still have a viable minimum product at the end of it.

Re:SproutCore 1.4 has been released by chc on Tuesday September 21, 2010 @02:27AM (#1711697)
But there is no library or application development platform that avoids the dilemma. It's a very hard problem. It seems unfair to fault SproutCore for not solving a problem that nobody else has made any real headway on.
Re:SproutCore 1.4 has been released by Isofarro on Tuesday September 21, 2010 @04:07AM (#1711872)
There is a significant difference between refusing to support progressive enhancement and not getting in the web developer's way of this best practice.