On 11-06-2014 03:01, Frank Tellefsen wrote:
2014-06-10 0:36 GMT+02:00 Ryan Bigg <[email protected]
<mailto:[email protected]>>:
> Why would the community do that? What are the benefits? Why is
Sprockets bad?
...
- Live reload in development mode
I'm curious (mostly afraid of, actually) about what this mean. Are you
talking about automatically refreshing the page when the assets change?
If so, I hope this is not enabled by default. I wouldn't use something
like this while developing my application.
...
> While I can see how Sprockets is not a good enough solution, I don't
think that forcing users to convert their libraries in a RequireJS
module is a good thing.
I'm not a big fan of this either, but what are the alternatives?
Well, I was never really very fond of RequireJS and haven't used it yet
as I much prefer the approach taken by the Rails Asset
Pipeline/Sprockets (this and automatic code reloading are the main
reasons I prefer Rails over other alternatives). I think Sprockets
directives a much better alternative to overcome the lack of a
require/import statement in JS. RequireJS (and similar approaches) seems
like an unnecessary complication from my point of view.
I haven't spent any fair amount of time thinking about alternatives, but
I'm pretty sure a better solution than using AMD exists until we target ES6.
> I'd love to see some solid integrated JS dependency management tool
to play well with Rails but I'm not sure if this is gonna happen any
time soon.
It's already here, and it's staring you right in the face.
I must be blind then as I can't see it ;)
--
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.
