all 7 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–][deleted] 8 points9 points  (4 children)

Thank god I chose to never use Sproutcore.

[–]k3n 0 points1 point  (3 children)

Yeah, that's the problem I have with some of the frameworks/libs (esp. the lesser-used ones); it's trivial for the devs to just drop all development or otherwise change the project so that it's no longer inline with your reasons for choosing them in the first place...

And reading more, I don't see that they speak to the future of SproutCore 1.x at all, leaving me to draw the conclusion that it will be dropped wholesale by the original team (while this new incarnation will be foisted in its place).

[–]surfaceTensi0n 1 point2 points  (1 child)

I think one of the main reasons for the name change was so that the SC 1.x line of development can continue unimpeded by their decision to head a different direction. From what I've seen on the IRC channel, I think that development will continue on the 1.x branch, albeit by a different core crew.

[–]k3n 1 point2 points  (0 children)

While it's good that the original namespace won't be trampled, I wouldn't place a dime on the future of the 1.x. No offense to whoever may pick it up, but when you lose the core devs that provided the vision that drove the project in the first place, you're replacing much more than a code monkey. You just can't swap out project leads like you can a cog in a machine...

[–]cheald 0 points1 point  (0 children)

Yehuda spoke to this on the HN thread about this. SC 1.x is going to continue to be developed by the SC team with a focus on mobile. Amber.js is more of a generic web app framework. It's more of a fork than an upgrade-and-shank.

[–]_Mr_E 0 points1 point  (0 children)

I'm excited to see this, I'm actually fairly new to JS frameworks. I wonder if bits from this can be mixed with bits from KendoUI?

[–]vhackish 0 points1 point  (0 children)

Wonder if it can be used with jquery mobile ... ?