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.
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.