I would like to make one suggestion: Allow combining multiple .less files in the config file before the .less files are parsed. The reason would be theming. For example, I might want to have three different themes and just have 3 different declaration files (e.g. in one theme, @textcolor: black, but in another @textcolor: white). I would combine each of the declarations with a common .less file containing the actual css rules. If there’s a way to do this already, please let me know. Or there might be a better way to achieve the same result.

(less-than sign) img src=”../images/page-peel.png” (greater-than sign)

Works in HTML:

Doesn’t work in CSS: background-image: url(“../images/page-peel.png”);

However, is there any “real” documentation? I’m specifically looking for examples of using the “mashing” functionality with the FOLDER element but what’s in the links on CodePlex appears to be VERY out of date (especially when compared to the source code). I’m trying to mash together files from throughout our project.

The problem I seem to be having is that it’s trying to mash the mash file (e.g. recursively mashing the file into itself to the point of having to kill my VStudio process). Almost seems like there needs to be an exclude option. Anyway, documentation would be a good thing.

Thanks,
BR

Hey I didn’t notice the date on it; I came in via reddit. I should have worded the reply differently, but it was those headings.
Lessons for me. And thanks for publishing.

One could argue that exposing IQueryable lets better programmers write concise code since you can now compose your logic.
a) some-query-getting-customers.Select(a -> a.Id) //If you just wanted the IDs, quite common
b) query.Where(other-conditions) //If we already have a query and you just wanted to filter some more.

Or consider Sorting and Paging. The post you linked to (from Justin) introduced new patterns for functionality that is already built-in. And never mind that those new classes (Sortable, Pageable etc) wrapped the IQueryable within it. Sometimes people do this because they fear it just wouldn’t be “N-Tier enough” if the Queryable got out of the middle tier. It doesn’t really matter though.

I don’t care about code quality, standards or best practices. I am happy if it works, happier if it is also concise.

Thanks.

I’m not solving an imaginary problem here. Check out the Reddit conversation from today.

It’s very simple. One year after writing this post, folks *still* don’t realize that a call like this:

var q = context.Users.AsQueryable();
var e = q.AsEnumerable();
e.First();

will select and return ALL of the user records in your database.

That’s not a “contrived” rule. That’s a serious problem that needs to be documented and addressed.

Also, I appreciate your three rules (the first of which is to avoid rules), but I find them to be a bit presumptuous. You don’t have me as pegged as well as you think you do.

Cheers,
E

Once upon a time, I used to believe in these patterns and ideals. I used to make similar rules for myself and others (Don’t do this, don’t return that, this should always do that etc). I wisened up after that. For all the pain, my rules had achieved very, very little.

When I look back, I laugh at all the juvenile bullshit I spewed out.

Here is my advice:
1. Don’t worry about rules which solve an imaginary problem.

2. Learn some other programming languages: Such as Python, Ruby or LISP/Clojure. Most people who obsess over trivial details know only Java or C#, and rarely stray out of their Windows IDEs.

3. Use Linux for a bit, even if you don’t use it for your job. Read up on computing history, the culture, the Jargon File, the AI Koans, ESR’s books, SICP; there’s a whole lot of good stuff out there.

Nothing will happen to your dog. Or your wife.

If you have for example “stylesheets1.chirp.css” and also a “stylesheets1..michaelash.css” the second file won’t get a minimized version. Suggestion is to show a popup.

Thanks anyway!