Miles Johnson

You shouldn't mask your errors with @, that's bad practice. Just write your code correctly.

So you're complaining about syntax differences between languages? In other news, water is wet.

Toolkit is far easier to customize and integrate. http://titon.io/en/toolkit

It really depends on how many dependencies you have, and how many sub-dependencies those have. Had too many issues on micro instances because of low memory, it's easier just to upgrade to a small.

The problem with using @extend is that your selectors grow to be insanely long, which in turn increases the file size of the compiled CSS file. We recently tried using this extend approach on a previous project and it was a nightmare. CSS selectors within Firebug/Dev tools would sometimes be around 30 long, extremely verbose, and difficult to debug. There's no reason to use @extend in this matter.

You could always try Foundation, or my own Toolkit. http://titon.io/toolkit/

I agree with most of what's stated here, excluding using UUIDs. When I set off to write my own model/DBAL/ORM system, the primary goal was to not use any kind of join internally. This allows for the ORM to hit DBs in other shards, other servers, hell, even other DB engines (as long as the FKs match). It even supports result set query caching so that every record is cached by ID and pulled in, allowing everything to populate and refresh the cache relatively quick. I like to think of it as a lightweight alternative to Doctrine.

https://github.com/titon/model

2 is wrong. 3 is just terrible practice. This isn't really anything cool.

When ever I read stuff like this, I just think to myself "Why would you ever use jQuery or a large framework to do such easy stuff like element creation.". At least some frameworks make it easier (MooTools for example) than jQuery.

I agree with @hpoom. Doing it at the company level is a much better approach, as not every rule should be followed. I have a hard time agreeing with a lot of the FIG style guide rules as it is.

That seems pretty standard now a days, just the syntax is horrendous. Why the need for underscores?

.module
.module--modifier
.module-element
.module-element--modifier

And another. This however, is the MooTools equivalent of Twitter Bootstrap or jQuery UI. Still in beta though.

https://github.com/titon/Toolkit

Does it work in FF? Animating transitions using max/min-width/height was always really choppy for me in FF. Chrome seemed to be the only one doing it correctly.

I had to fall back to using height/width and JS.

@vfalconi @napotopia - It may be deprecated, but splitting the text into two heading tags is still the correct approach.

This is far more elegant than either of those approaches.

document.body.grab(new Element('div').addClass('spinner'));

You semantics are wrong, so this approach is invalid. You have 2 headings, so they should be different heading tags.

<hgroup>
    <h2>This is the main label</h2>
    <h3>Secondary label</h3>
</hgroup>

Yeah, I agree with the others. You don't really need the scrolling Javascript, simply the resize one.

Outside of that, I do agree about the other properties.

h1-h6 should be using em scaling. This will allow for easier use and font scaling wherever the tags are being used. Simply increase the font percentage on the parent or the context.

This is fantastic. Would of never thought of this, cheers!