Fwd: [sproutcore] Is SproutCore deprecated?

[Chad Eubanks]

Hi guys,

What can we do to move away from this impression?  I wholeheartedly believe that is in our communities best interest to move away from this confusion.  Having a mixed message on our main site and sproutcore meetup groups hosting ember meetups causes more harm then good. 

- Chad

Begin forwarded message:

From: Jiva DeVoe <jiva....@gmail.com>

Subject: Re: [sproutcore] Is SproutCore deprecated?

Date: May 10, 2012 10:35:55 AM PDT

To: sprou...@googlegroups.com

Reply-To: sprou...@googlegroups.com

Thanks.  Glad to hear it.  I like SproutCore a lot. I think you may want to evaluate the messaging on your website.  The impression given is, SproutCore 2.0 is Ember, and that people should look to move their SproutCore apps to Ember.

On Thursday, May 10, 2012 9:57:46 AM UTC-7, Banks wrote:

Hi Jiva,

Sproutcore by no means is dead or deprecated.   Ember and Sproutcore solve two different problems and cater to two different demographics.  

- Chad

On May 10, 2012, at 9:36 AM, Jiva DeVoe wrote:

I'm evaluating technologies for a new web app and I'm confused about the status of SproutCore.

Some say SproutCore is deprecated in favor of Ember.js.  Ember's docs are not nearly as complete, nor does the framework appear to have everything SproutCore had.  So I'm wondering, is SproutCore deprecated? Or is it still alive?  Should I use SproutCore for a new web app or should I suck it up and use Ember.js?  FWIW, Ember.js does not appear to have what I want, so it would be more likely I'd go find something else like Cappuccino or just straight up jquery/prototype/etc.

--

--
You received this message because you are subscribed to the Google Groups "SproutCore" group.
To view this discussion on the web visit https://groups.google.com/d/msg/sproutcore/-/J0AtOxb7kgcJ.
To post to this group, send email to sprou...@googlegroups.com.
To unsubscribe from this group, send email to sproutcore+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/sproutcore?hl=en.

[Dave]

Agreed, but not sure there's a whole lot we can do other than keep patiently answering questions.

There's a lot of confusion left over in the ecosystem from before.  What are the *current* sources of *new* confusion?  Is there anything on the main site?  If so it should be fixed.  Might be worthwhile updating old blog posts with a big message at the top ("SproutCore 2 has become Ember and is no longer associated with SproutCore") with a link to CJ's blog post.  Meetups?  Might be worth doing a search of SproutCore meetups to make sure that they're using the term properly.

[chad eubanks]

I know the NY sproutcore meet up group places a large emphasis on ember.  Ideally, there should be a ember.js NY meet up group as oppose to using the sproutcore NY meet up group for these events.

http://www.meetup.com/Sproutcore-NYC/events/64798132/

- chad

[Luke Melia]

As the organizer of the NYC meetup, this is something I've struggled with how to handle. My company, Yapp, uses both Sproutcore and Ember, so we have a vested interest in both projects have a thriving local ecosystem. I'm open to ideas about how best to accomplish that, and I'm not comfortable that my current ad hoc approach is the right way to go.

Before I inherited organizing the Sproutcore NYC meetup, it had had exactly zero events in the preceding 6 months and 2 in the previous 12 months. Of the two people responsible for organizing those events, one is no longer working with Sproutcore, and one moved to the West Coast. Basically, there wasn't an organized community to speak of.

As I've spoken to local developers, there is a lot of excitement and interest in Ember.js topics. The big topic on people's mind here is Backbone vs. Ember. People with Sproutcore experience have a leg up in learning Ember, because of the common heritage and KVO/object model primitives.

At our last event, we had a talk about the Ember.js StateManager with some references to Sproutcore Statecharts, as well as two lightning talks: one was a demo of a Sproutcore app and update on 1.8 from Tim Evans and one was an experience report from a new Ember.js user about issues he ran into on his first project.

I could split the groups into two. If I do, I think we would have a well-attended Ember.js meetup and an anemic Sproutcore meetup. It also is basically double the work and cost for me as an organizer to do that.

On the other hand, I understand that having the groups combined might be confusing to outsiders and am sensitive to the need for clarity.

I'd love to hear people's thoughts, especially from the New Yorkers on this list and from other people running active Sproutcore meetups.

Best,

Luke

-- 
Luke Melia

http://www.lukemelia.com/