Live data from Hacker News

Drop jQuery as a dependency from Rails

github.com

61–70 of 123 posts

Re: Drop jQuery as a dependency from Rails

#61

Omakase implies a certain level of excellence in all the individual choices. I believe Rails is In-N-Out Burger. While it offers few choices, it's reliable and the hamburger is very good. The fries and frontend framework are acceptable but no one goes to In-N-Out for the fries.

animal fries dawg

Re: Drop jQuery as a dependency from Rails

#62
post #27

Earlier quoted context omitted.

You're missing the central point of default rails stack. http://david.heinemeierhansson.com/2012/rails-is-omakase.htm...

Sure, except in this case the Rails defaults are totally at odds with how the larger JS ecosystem has evolved. CoffeeScript was basically the logical complement to Haml (Ruby-like syntax for HTML) and Sass (Ruby-like syntax for CSS) -- although Sass has since dropped its original syntax and moved on with the CSS-like SCSS. Since then CS has lost a lot of popularity outside the Rails community. Babel and TypeScript pr…

Sass has not dropped it's namesake syntax. They just recognized that the CSS-like syntax is easier for newcomers to parse and so enabled it by default.

Re: Drop jQuery as a dependency from Rails

#63

There was an article about a week ago that makes the claim that Rails is tailor-made for Basecamp. This single comment absolutely confirms that point of view: https://github.com/rails/rails/issues/25208#issuecomment-222...

Sure, DHH said it himself. Rails is for basecamp like apps. Whats the deal?

But is it "for Basecamp like apps". Or is it "for the Basecamp app"?

I honestly can't believe a back end framework has minimum supported browser requirements that are basically "use the latest or GTFO".

Re: Drop jQuery as a dependency from Rails

#64

Omakase implies a certain level of excellence in all the individual choices. I believe Rails is In-N-Out Burger. While it offers few choices, it's reliable and the hamburger is very good. The fries and frontend framework are acceptable but no one goes to In-N-Out for the fries.

Animal Fries tho

New on Medium: Rails is Animal Fries

Re: Drop jQuery as a dependency from Rails

#65

Omakase implies a certain level of excellence in all the individual choices. I believe Rails is In-N-Out Burger. While it offers few choices, it's reliable and the hamburger is very good. The fries and frontend framework are acceptable but no one goes to In-N-Out for the fries.

Now I'm hungry ;)

Re: Drop jQuery as a dependency from Rails

#66

Omakase implies a certain level of excellence in all the individual choices. I believe Rails is In-N-Out Burger. While it offers few choices, it's reliable and the hamburger is very good. The fries and frontend framework are acceptable but no one goes to In-N-Out for the fries.

Cut fresh from actual potatoes right in front of you. Just sayin..

Re: Drop jQuery as a dependency from Rails

#67

Omakase implies a certain level of excellence in all the individual choices. I believe Rails is In-N-Out Burger. While it offers few choices, it's reliable and the hamburger is very good. The fries and frontend framework are acceptable but no one goes to In-N-Out for the fries.

Cut fresh from actual potatoes right in front of you. Just sayin..

While true, I find that they kind of tasteless, overall. And I love me some good fries.

Re: Drop jQuery as a dependency from Rails

#69

Earlier quoted context omitted.

Rails philosophy is a full stack framework. Not having to make decisions about your first web app is a huge draw to the framework.

> Rails philosophy is a full stack framework. Not having to make decisions about your first web app is a huge draw to the framework. But you still have to make a lot of decisions. How do you handle user management ? ACL in a Rails app ? AFAIK Rails doesn't come with a default solution to these problems. What do you think is more important for an application ? User management or turbolinks by default ? The former woul…

[deleted]

Re: Drop jQuery as a dependency from Rails

#70

Rails should stop messing with Javascript all together. Drop JQuery, CoffeeScript, TurboLinks and what not and let the users decide what to use, make it optional. Rails shouldn't require a JS engine in order to run.

I feel like the rails-api built into Rails 5 solves a lot of this. None of these will be installed when you `rails new project --api`. Doesn't help if you're just trying to do static HTML though.
Post reply on HN