Drawbacks of including CSS and Javascript in HAML [closed]

Question

Closed. This question is opinion-based. It is not currently accepting answers.

Want to improve this question? Because this question may lead to opinionated discussion, debate, and answers, it has been closed. You may edit the question if you feel you can improve it so that it requires answers that include facts and citations or a detailed explanation of the proposed solution. If edited, the question will be reviewed and might be reopened.

Closed 9 years ago.

Improve this question

I need to change the design of various pages of a website developed in Ruby on Rails. I was thinking of modifying the HAML files to include CSS and Javascript to make the desining nicer and more responsive.

What could be the drawbacks of such an approach? I have came across such example here.

This question is either too broad, opinion based or requires discussion and so is off-topic for Stack Overflow. If you have a specific, answerable, programming issue, please provide full details. — Paulie_D
– Paulie_D, Commented Jan 21, 2016 at 9:55

max · Accepted Answer · 2016-01-20 22:38:02Z

2

The drawbacks are exactly the same well known drawbacks of including anything but content in HTML.

Your muddling content with presentation and behavior. This leads down quick path to a total mess of inline everything and generally poor development practices.
Your CSS and JS will not leverage caching properly between pages that might otherwise share components.
Your CSS and JS will not be properly minified.
You will not be able to use code quality tools properly on CSS or JS.
The execution order of your JS is going to be confusing.
Your code indentation and quality in general will suck. This especially applies to HAML.
Other developers will hate you.

Rails even generates per controller stylesheets and scripts by default to make separating views from assets easier.

But in general the idiom of "per page" styles and behavior should be avoided unless you are creating trivial brocureware, you get better code quality and reuse if you try to envision a set of reusable parts or modules - HTML class attibutes are cheap - parsing a huge document with a junk drawer of CSS/JS is expensive.

edited Jan 20, 2016 at 22:38

answered Jan 20, 2016 at 22:25

max

103k15 gold badges113 silver badges177 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

max Over a year ago

Take a look at Foundation or Bootstrap if you want some basic clues about how to create reusable parts for responsive apps.

Collectives™ on Stack Overflow

Drawbacks of including CSS and Javascript in HAML [closed]

1 Answer 1

1 Comment

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Linked

Related