akdetrick

This is a good (and fair) question. Sequence doesn't appear to do a ton of stuff the box, without applying a theme from the site or one of your own design.

That is, however, why I love this idea. It looks like this provides a good foundation for creating a slider; a nice interface, well documented options and callbacks, and nothing more.

I feel like I can actually build something of my own with this instead of clobbering an existing slider plugin with my own code until it does what I want. This is a much sharper tool than a widget pre-bundled with style defaults.

"One principle of development is D.R.Y., also known as don’t repeat yourself. Within CSS this principle can speak volumes as it is easy to continually write the same styles over and over again. Don’t. CSS was designed in a way to allow you to cascade styles and use classes so that you easily apply and inherent styles."

This is wonderful, useful advice to beginners and seasoned developers alike. In fact, anyone who works with CSS, regardless of how they write it (raw, sass, less), should be force fed this advice. At the end of the day, CSS is a declarative cascading language, and you must leverage it as such in order to optimize code reuse, performance, maintainability, etc.

Aside from this tutorial being beautifully designed, the notes about semantics and best practices are enough to make me feel good about recommending it to anyone who wants to learn more about HTML & CSS.

The "dumbing down" argument almost seems to assume that a web of curated/unoriginal content can not coexist with a web of content creators.

Creating new ways to interact with content on the web doesn't seem to me to be a bad thing, especially when it's usable enough for anyone to participate.

Creating and leeching are not mutually exclusive.

I recall reading about this event in Erik Larsons "Thunderstruck". The book includes a pretty interesting account of the fits and starts of wireless technology, if not overly embellished.

The tuning issue is one of many snags that Marconi ran into, and with a government contract on the line, he made no small effort to keep the technological troubles under wraps until solutions could be found.

Duplication is probably the easiest mistake to make with CSS, and using authoring languages like LESS and SASS won't necessarily help. Duplication not only causes bloat, but it can lead to specificity wars and poorly performing selectors. Worse yet, it becomes more difficult to trust the code already in place, and easier to write your own styles to perform tasks that some other code already handles.

This is the death spiral of CSS, and it's refreshing to see someone take on this problem directly (aside from teaching a methodology for writing CSS).

Automated documentation for CSS is a fantastic idea, and this looks well executed.

In all of the news and outcry surrounding SOPA, this is the most puzzling thing. I would be surprised to learn that the lobby of those in support of this bill is stronger than of those against.

Unless I'm wrong about the relative strength of these opposing lobbies, it hardly makes sense that SOPA seems to have so much traction among legislators.

I'd venture to guess that the choices you mention did not always carry the sort of consequences they do today.

You're right, policy decisions don't cause more people to have kids at a young age. They do however, have an effect on joblessness [1], just to name one facet of the economic environment that now exists in the US.

[1] http://www.google.com/publicdata/explore?ds=z1ebjpgk2654c1_&...

Negatively judging someone for dressing poorly is as bad as judging someone for dressing well. For that reason, I can't agree completely with either side of the argument expressed in this thread.

With that said, it would be nice to wear a jacket/tie over jeans without feeling overdressed and negatively judged as a "suit" among developers. I agree with the sentiment that developers should wear whatever the fuck they want, but does that not include dressing well?

I don't subscribe to the notion that you can write code faster with less keystrokes (vi/emacs, anyone?). I do however, understand that a cleaner syntax would lend some readability and simplicity to your code once you learn said syntax. Ultimately, I find that the problems that CoffeeScript solves, and solves quite well, are not really that big of a deal for me given that I've been working with Javascript enough to get used to the quirks. I'm not sure if I'll ever use it myself, but I can't blame anyone who would; this article does a good job explaining some of the benefits.

Sticks may be fine, as long as you don't use it to play fetch with your dog later: http://www.google.com/patents?id=hhYJAAAAEBAJ&zoom=4&...

You beat me to my reply about Andy. I almost regret taking his blog off my reading list, because he's a fantastic designer that has a special skill for teaching design fundamentals by example. Unfortunately, I couldn't tollerate slogging through all the political grit to get to any design points he had to make in his posts.

Every problem in computer science can be solved with blaming the programming language.

The "end result" approach with a diminished focus on clean markup doesn't make sense. The "end result" is not going to be the same for every user - for starters, people use different clients, and not everyone is sighted.

Of course, this is also based on the premise that code is bad because it's not human readable when it reaches the browser. Maybe I'm getting hung up on the details when it seems like the article was written only to defend the use of WebForms.

The "language is language" argument has shifted my thinking a bit from my initial reaction to this project.

In that line of thinking, it's also raised a new question in my mind. CoffeeKup seems to be optimized for baking logic into the template. It is not too different, but too much like most "templating" languages for me to completely get behind it.

This is however, a really cool project that's well executed. I'm just hoping that the idea of further separating logic from templates takes hold (something like mustache, perhaps).