Google also shows javascript-only content in search results now.
613 karma · joined August 11, 2010
Google also shows javascript-only content in search results now.
At the bottom of that post you can see that rendering the errors in rails can actually be much simpler using respond_with
http://www.which.co.uk/consumer-rights/regulation/distance-s... for more info.
Still, it's very possible to be almost entirely semantic with a few minor exceptions using a css preprocessor.
[1] http://compass-style.org/reference/compass/utilities/general...
i.e. if you have:
.column {
width: 100px;
display: inline-block;
}
And you do: .cool-sidebar {
@extend .column;
}
Then the generated css will be something like: .column, .cool-sidebar {
width: 100px;
display: inline-block;
}
[1] https://github.com/twbs/bootstrap-sassAs demonstrated in the article you can trivially make an element 6 columns in LESS (or SASS, which has a bootstrap port also)
https://github.com/jimweirich/wyriki/commit/d28fac7f18aeacb0...
Point 1: You will almost always be transpiling your javascript. In any serious project, you will want to have lots of small files to ease development, and then concatenate into larger files to ensure optimal http loading. If you don't already do this regardless of modules, you probably should.
Point 2: If you are intentionally or serendipitously relying on script execution order, that is your bug. The module loader has helpfully exposed a bug in your code for you.
Point 3: If you have lots of modules, it is simpler to deal with a module system than mashing together a load of scripts.
This complaint should come with a severe disclaimer that it only applies to trivial applications, because as soon as you start building something complicated the arguments are just plain wrong.
Software engineering is hard, and robust software engineering practices usually only pay off once you get beyond trivial examples. The ones that work, however, pay off massively once you do use them for more complex use cases.
In addition, I found it to be slower, less flexible, and prone to permanent repository corruption - yes, in git you do see repo corruption but because of the cryptographic nature of git objects you know immediately. HG will (did?) happily let you work away at a corrupted repo for weeks until a fresh clone was attempted and the dreaded repo corrupted message killed development for days until the problem was painstakingly manually fixed.
This is just personal experience and a lot of it comes down to taste, but IMO if you are already proficient with git there is absolutely nothing about mercurial that is preferable and some considerable downsides I have been subjected to.
Disclaimer: This was a few years ago now, perhaps the project is more mature than it was.
Relevant link: http://metaskills.net/2012/02/27/too-less-should-you-be-usin...
Now I learnt a bit about typing skills and ergonomics I am fine on a regular keyboard, but I would have kept on with the datahands if not for its massive lack of practicality.
Basic typing was great, but using it on a mac for programming was not so great - all the modifier keys were wrong, and the PS2-USB connection was flaky. Not to mention carrying it around with a laptop was basically impossible without a dedicated case...
Or Trigger...
http://www.frequency.com/video/only-fools-horses-truth-behin...