search

derbyjs / derby-examples

Example applications for the Derby framework
http://derbyjs.com/
283 stars 74 forks source link

Why are all the examples written in Coffeescript? #19

Closed flexd closed 9 years ago

flexd commented 11 years ago

I do not currently use CoffeeScript, but I am able to read it fairly well.

We were discussing this on IRC and I have the opinion that the examples should be in pure javascript simply because the majority of us most likely do not use CoffeeScript, which makes having all the examples in CoffeeScript another hurdle in starting to use Derby.

What are your thoughts on this?

I recently learned of Derby and I am exploring it, so far I like most of what I see.

I just thought that if you (as the creators of Derby) want to spread the word about Derby and get people to use it, you might want to make it as easy as possible for someone that only knows Javascript, or is learning.

Also, as I've mentioned on the mailing-list (a long with a few others), the version of Derby we can install from npm is broken.

I am getting the error below, 

Uncaught TypeError: Cannot call method 'apply' of undefined localhost:143
Uncaught ReferenceError: DERBY is not defined

Someone on IRC suggested this both has been fixed, and that it had something to do with Browserify.

If it has been fixed though, us newcomers to Derby would appreciate a new working version being released.

You also seem to have a lot of old and unread issues here on GitHub, which kind of makes me question if this is ever going to be read, or if the project is even active.

I see there is recent commit activity though. :-)

zenggongli commented 11 years ago

1:in the example dir,like hello,input "npm install" install need package 2.input"make",complie coffee to js 3.input" node server.js" to run

anthonybrown commented 11 years ago

try coffee server.coffee instead of node server.js

codingisacopingstrategy commented 9 years ago

Hello!

The DERBY is not defined is also mentioned in https://github.com/derbyjs/derby-examples/issues/20 but seems to be related to an older version. Maybe you can try the latest version and file a new bug if it doesn’t work?

Anyway, the main point of this issue is CoffeeScript—as also noted by @triplekdev. I agree that using CoffeeScript adds a level of complexity not very useful in the context of an examples repo. Also, the new 0.6 docs are written in plain JavaScript.

I would suggest converting the existing examples to JavaScript. CoffeeScript might be useful for an individual developer, or for a development team that agrees on using it, but it is not the mainstream.

To highlight Derby’s capacity to use CoffeeScript, a specific example could be developed?

Cheers,

enjalot commented 9 years ago

we do have a mix of coffee and javascript in the examples. We certainly believe that the libraries should be in JavaScript to reduce friction for the community. The examples have been the best vector for learning Derby to date, but we are working to change that.

Since the official guide for learning derby will be in javascript I think the only metric to judge the examples by is how many of them there are. For several of us coffee is much more convenient for quickly making things, we will continue to use coffee to whip up examples where it will be faster to do so.

codingisacopingstrategy commented 9 years ago

Would you consider Pull requests that rewrite existing examples to JavaScript?

enjalot commented 9 years ago

yes, we would.

On Tue, Feb 24, 2015 at 10:10 AM, Eric Schrijver notifications@github.com wrote:

Would you consider Pull requests that rewrite existing examples to JavaScript?

— Reply to this email directly or view it on GitHub https://github.com/derbyjs/derby-examples/issues/19#issuecomment-75812062 .

Ian Johnson - 周彦 http://enja.org