Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Sproutcore 1.5 released

blog.sproutcore.com

Post reply on HN
Print view View original

11–20 of 28 posts

Re: Sproutcore 1.5 released

#11

Post by jmathai »

patrickaljord wrote: post #3
jmathai wrote: post #2

I'm sure it's got its merits but the Sproutcore site does a horrible job explaining what it excels at. For example, on the Demos and Sample Code page it has me install a ruby gem. http://www.sproutcore.com/demos/ What the hell? You lost my interest at ruby and the command line.

> What the hell? You lost my interest at ruby and the command line. I install all my dev stuff with the command line (npm, gem, easy_python etc). What's wrong with that?

This is a client side (100% JavaScript) library. I love the command line, but shouldn't invoke it to learn more about a JavaScript library.

Re: Sproutcore 1.5 released

#12

Post by jmathai »

tomdale wrote: post #4
jmathai wrote: post #2

I'm sure it's got its merits but the Sproutcore site does a horrible job explaining what it excels at. For example, on the Demos and Sample Code page it has me install a ruby gem. http://www.sproutcore.com/demos/ What the hell? You lost my interest at ruby and the command line.

I'm sorry that you were turned off by the Ruby build tools. Many people see the build tools and assume that you need to know Ruby to use SproutCore. This isn't true. SproutCore apps are written 100% in JavaScript, and Ruby just happens to be the language we used to create the tooling needed to build serious web applications. For example, the build tools will automatically concatenate your JavaScript and CSS files, mi…

Thanks for the response. I wasn't annoyed by any means. It's just really confusing and I think sending mixed signals (hence, "what the hell?").

Most need to be sold on what's possible before I can be sold on organization and architecture. If that's not your target audience then I don't think this is a big deal. But if you want to get your hard work out to the masses then show them what's possible and worry about the organization and architecture later :).

Re: Sproutcore 1.5 released

#13

Post by jmathai »

ColinCampbell wrote: post #10
detst wrote: post #7

Earlier quoted context omitted.

I would encourage you to make that a priority. Every time I see something about SproutCore, I'm interested but end up not doing anything with it. I keep hearing about the demos being out of date. Things like this: "we have a great new default theme called Ace 2.0" Sounds great, how about a screenshot or two, if not a demo? And this: "looks at home on ... mobile operating systems" More info please? I'm interested but…

Fair points all around; I agree wholeheartedly. Here's what the problem has been thus far: do we focus on making the framework better, or do we focus on selling it? Personally, I'm much more comfortable with making sure we deliver the goods before we try to sell it. That's what SproutCore 1.5 is about. This is the first smoke signal of where we want to head with the framework, and people can take that for what it is.…

Good to hear. The way I (and most people) decide which frontend libraries to use are by seeing them in action. Then I can decide after evaluating it technically if it's something I want to use or not.

Looking forward to doing that with SproutCore.

Re: Sproutcore 1.5 released

#14

Post by joegaudet »

We (matygo) use SC for our client side app, and once we got over the learning curve we came to really enjoy it. The reason I posted this was there is a lot of great stuff they put into 1.5 that should lower the barrier to entry for a lot of people :)

Re: Sproutcore 1.5 released

#15

Post by divtxt »

gourami73 wrote: post #5
patrickaljord wrote: post #3

Earlier quoted context omitted.

> What the hell? You lost my interest at ruby and the command line. I install all my dev stuff with the command line (npm, gem, easy_python etc). What's wrong with that?

...the problem is that there is no reason that a demo for a web framework should require an install in the first place--I mean you're already on a web page to look at it aren't you?...sure it's easy enough to install (i did it)...but it seems lazy especially if the intent is to promote usage of the framework.

I wanted to try the demo many months ago, and had to stop at the first line:

    gem install sproutcore
There's no way I'm polluting my desktop ruby install. Please document a way to set up a standalone folder.

(if had been python I could have hacked it myself. i dont know ruby)

Re: Sproutcore 1.5 released

#16

Post by bradgessler »

jmathai wrote: post #2

I'm sure it's got its merits but the Sproutcore site does a horrible job explaining what it excels at. For example, on the Demos and Sample Code page it has me install a ruby gem. http://www.sproutcore.com/demos/ What the hell? You lost my interest at ruby and the command line.

Backbone.js (http://documentcloud.github.com/backbone/) is a great alternative to SproutCore if you're turned off by the gem install.

Re: Sproutcore 1.5 released

#17

Post by tomdale »

bradgessler wrote: post #16
jmathai wrote: post #2

I'm sure it's got its merits but the Sproutcore site does a horrible job explaining what it excels at. For example, on the Demos and Sample Code page it has me install a ruby gem. http://www.sproutcore.com/demos/ What the hell? You lost my interest at ruby and the command line.

Backbone.js ( http://documentcloud.github.com/backbone/ ) is a great alternative to SproutCore if you're turned off by the gem install.

We've also created a build of SproutCore that fits into a single, http://amber-todos.strobeapp.com/ (demo)

https://github.com/wycats/experimental-amber-todos (source)

Re: Sproutcore 1.5 released

#18

Post by karterk »

tomdale wrote: post #4
jmathai wrote: post #2

I'm sure it's got its merits but the Sproutcore site does a horrible job explaining what it excels at. For example, on the Demos and Sample Code page it has me install a ruby gem. http://www.sproutcore.com/demos/ What the hell? You lost my interest at ruby and the command line.

I'm sorry that you were turned off by the Ruby build tools. Many people see the build tools and assume that you need to know Ruby to use SproutCore. This isn't true. SproutCore apps are written 100% in JavaScript, and Ruby just happens to be the language we used to create the tooling needed to build serious web applications. For example, the build tools will automatically concatenate your JavaScript and CSS files, mi…

I had a similar reaction when I saw the mention of Ruby. I think it's a subconscious thing. It would help if you put this explanation up on the site in a prominent place as well.

Re: Sproutcore 1.5 released

#19

Post by cubicle67 »

jmathai wrote: post #2

I'm sure it's got its merits but the Sproutcore site does a horrible job explaining what it excels at. For example, on the Demos and Sample Code page it has me install a ruby gem. http://www.sproutcore.com/demos/ What the hell? You lost my interest at ruby and the command line.

for a bunch of hackers on hacker news, there's an awful lot of prissy "ew, might get my hands dirty" feedback going on here

sorry, but it's been a long day and I'm sick to the back teeth of people bitching about other people's hard work because it's not exactly to their liking

Re: Sproutcore 1.5 released

#20

Post by user24 »

We're seriously considering sproutcore for our next web project. Personally I'm a little uneasy about investing so completely. I mean it's nothing like jQuery or other libraries where you just sprinkle it here and there, it's an entire development methodology. It'll be interesting to see how it goes.

Would be really great to see some feedback from other users.

Post reply on HN