Yeah, my statement is confusing, but think of it this way, Microsoft forces its customers to upgrade to their new OS by killing of support of their previous OS, so its the same if we kill of IE6 users by forcing them to upgrade to IE7 if they want to use our website or make a popup which says get Firefox and never have to worry about browser incompatibility ever again.

I don’t care about IE6 or 7

Good luck keeping customers.

Opposed to what was said before, allowing for clean semantic code is the strength of Sproutcore and Ruby. Hiding unnecessary, repeating and redundant code from the developer is the way to go…

@Johans the controller never really updates the view. The controller updates a stored value and that’s all. The label_view element just happens to be bound to that value, but the controller is unaware of that.

That’s what I was trying to demonstrate — the wiring up of interface elements without having to write any DOM manipulation code. I thought it was pretty neat.

“Because it doens’t work in IE” is a terrible reason not to use it.

Why? Why should we as developers handicap our business by telling our clients that we’re not going to support one of the most used browsers out there?

Sounds like a good way to kill a business personally.

>The demo is badly designed since the Controller updates the View - the view should be bound to the Model.

Er, that’s the whole point of the Controller in MVC, to synchronize data between the view and model.

@everyone else

“Because it doens’t work in IE” is a terrible reason not to use it. Let’s push the state-of-the-art, not wallow in the status-quo.

there is no way I am chaining myself to IE6 for another 2 years waiting for System 7 to come out and people start upgrading.

And there is no way anyone will use your framework until it supports IE6 or the years pass and no one uses IE6 any more.

Get your head out of the sand! This isn’t a developer request. If developers had their way, they’d all use the very latest technology. It’s the users - a market which can’t be controlled.

As long as users are using IE6, developers will (have to) support it. I can’t see any framework being successful when it dictates that it can’t be used on one of the most popular browsers out there.

It seems a lot of web programmers are missing the point, because this isn’t your grandma’s web programming. This is application design. Once there is a good IDE for this (please please Apple make me something in xcode with Interface Designer) we will see an explosion in great web apps.

As far as support for IE goes - I have had to drop it for one project that needs IE 6 support, but I have another app where people are going to drop IE6 to use it… It’s time for the web to grow up - there is no way I am chaining myself to IE6 for another 2 years waiting for System 7 to come out and people start upgrading.

The demo is badly designed since the Controller updates the View - the view should be bound to the Model.

As for not working in MSIE - do I really want to spend my time doing cross-browser testing when I could be workgin on the application? Not me!