search

laravel / framework

The Laravel Framework.
https://laravel.com
MIT License
32.42k stars 10.99k forks source link

Request: Add coffeescript to Laravel by default #1027

Closed ghost closed 11 years ago

ghost commented 11 years ago

Well I just don't like javascript, since it's not possible to extend other classes properties. In coffeescript it's possible and the syntax is so much cleaner.

https://github.com/vtalbot/coffee

robclancy commented 11 years ago

No.

xtrasmal commented 11 years ago

It's like watching the Naked Gun

spencerdeinum commented 11 years ago

There is no "default" in Laravel, aside from including js files.

Coffeescript is great, but theres no reason to include it for every Laravel user. It is perfectly fine as a composer package.

machuga commented 11 years ago

@and-ers while we are working on a simple way for people to manage their assets, I don't think we're looking to handle CoffeeScript/Sass/Less/Opal/etc as defaults in the framework at this time.

ghost commented 11 years ago

spencerdeinum, why including js files at all? Javascript is awful language that I think we should move away from.

machuga, goodgood! It's actually quite simple now as it is now(just edit 2 files), The hard thing is that you have to find a laravel-suitable 3rd party asset and look at documentation from different sites. I still think that modularity is good and I like the decentralization we get with composer.

JoostK commented 11 years ago

Just use the package if you want. When you say something isn't possible with JS, but is with Coffeescript, remember that Coffeescript compiles to JS. Everything you can do in CS is also possible in JS.

xtrasmal commented 11 years ago

@JoostK I think he ment incorporating functionality like this by default: https://github.com/vtalbot/coffee Machuga already gave a complete answer : "while we are working on a simple way for people to manage their assets, I don't think we're looking to handle CoffeeScript/Sass/Less/Opal/etc as defaults in the framework at this time. "

xtrasmal commented 11 years ago

This is complete madness!

@and-ers Coffeescript is only nice for the person writing it. At the end it really doesnt matter, because it WILL be compiled into javascript anyways. So what does it matter? Either you compile it into JS or the package does. Either way you need to include something which ends up as javascript.

So your workflow would be one of these two:

You do it

Put an automatic build tool that listens to changes and compiles coffee to javascript

  1. Write coffeescript
  2. Upload the javascript
  3. Include it in the header of your site

Framework does it

Put an automatic build tool that compiles coffee to javascript

  1. Write coffeescript
  2. Upload the coffeescript
  3. Include it in the header of your site

So tell me.. what's the difference other than you, in your room, writing something else than javascript?

radmen commented 11 years ago

Maybe take a look at Basset ?

andrewryno commented 11 years ago

-1. Same reason why LESS/SCSS/etc. shouldn't be included. Not every developer uses it and everyone has their own workflow on using it.

bencorlett commented 11 years ago

Hmm, no.

duellsy commented 11 years ago

:-1:

vtalbot commented 11 years ago

You can't force every developers to a new language, even if it's awesome. But you could fork laravel and modify it to your needs.

billmn commented 11 years ago

:-1: