My intro to LESS - If you're not using it, you should be. (austinkpickett.com)
Hope most of you are using LESS or something similar (SASS). I've found it to be a dramatic boost in productivity.
Let me know what you think. Thanks.
Let me know what you think. Thanks.
43 comments
[ 4.1 ms ] story [ 68.3 ms ] threadBut I'm looking towards learning SASS to write a follow up to this.
But if you're referring to my overall background being black and then the content BG (white) coming in a bit late-- Sure I was a bit lazy on the code but merely wanted to get this up and running asap.
And no, I don't think you should take my advice because you apparently don't need it. I was simply sharing my post in an effort to expose myself for criticism or web nerds to talk to.
Cheers.
http://i.imgur.com/KVk82.jpg
I thought it was some new hipster theme where you would have to highlight the text to read it. Thankfully I was wrong. :D
Using something like Livereload (or Compass.app) is pretty amazing. Watched folders (automatically compiles SASS > CSS, changes instantly reflected in the browser.
And a lot of other reasons. One of those is Bourbon. Do yourself a favor and stay away from Compass though. It's very bloated and... just not good.
Good luck going forward!
http://nylira.com/stylus-the-revolutionary-successor-to-css/
http://designshack.net/articles/css/sass-vs-stylus-who-wins-...
-g = highlight the particular string that's been found by the last search command
-M = verbose prompt
-R = all control characters, 'R' for Raw
-x4 = tabs take 4 spaces
-X = don't reinit the screen when the pager exits
-f = force open any kind of file
-F = end the pager when the end of the file has been reached
-z-1 = use 1 less line for a screen's worth of content
Couple of minor points:
-F is actually 'quit immediately if the input is less than 1 screen-worth of text'. It means you can just pipe any old thing into it, and if it's only a couple of lines, you don't have to quit manually.
-e/-E is the 'quit when reaching input EOF', with a nice little trick that -e only quits the second time you reach EOF, so you can go right to the end of the file, and to quit just hit space or whatever to seek further.
The other thing is:
whereas you're describing -r. I'd definitely recommend big-R if you don't enjoy periodic symboljunk terminal confusion.I'd expect an article about the pre-Christian era world to include similar references like "BC_ENV_ARGS="-q $(echo ~)/.bc"
In addition to displaying ordinary text files, most can also display binary files as well as files with arbitrary ascii characters.
[1]http://incident57.com/less/
It is an essential piece of software in my workflow.
The only downside is probably I never get to use my favorite CSSEdit again.
My toolchain is currently...
python/apache pure json apis server side
knockoutjs/jquery/less client side
This is very powerful, but the semantics of programming are pretty crazy. I have variables and "functions" in my css, data bindings in the HTML, and a massive ammount of js. The js is sometimes hard to structure.
I almost wish there was a single lightweight coffescript style language to replace the big three (HTML/CSS/JS). The "HTML is for documents" idea is already long gone in most of my code.
http://code.google.com/p/closure-stylesheets/
"Closure Stylesheets is an extension to CSS that adds variables, functions, conditionals, and mixins to standard CSS. The tool also supports minification, linting, RTL flipping, and CSS class renaming. "
I'm curious about this. Is it more than just a minor performance hit?
Compiling and running LESS on the fly in production might, besides the extended load time, increase the chances for a flash of unstyled content. If this makes you nervous, don't run LESS on the fly in production.
See the @extend section here: http://css-tricks.com/sass-vs-less/
(Disclaimer: none. I use both, depending on project.)
I'm never going to write raw CSS again.
I grabbed CodeKit, so I might try SASS the next time I'm building something on the web. I haven't really seen anything in the SASS vs. LESS shootouts that makes me go "dang I wish I could do that"; my CSS is relatively straightforward. Just having named colors, a couple color mixing functions, mixins, and nested syntax helped a LOT.
It's true selector inheritance that will change the way you author styles.