We talked about this in a CPR class once. The biggest reason paramedics don't run is to avoid injury, which would obviously impede their ability to help.
This is the key that I missed when I first read the article. Mixins will always be repeated when compiled. Placeholders result in combined selectors so the styles aren't repeated in the compiled CSS.
In many ways, it seems like placeholders would almost always be preferred to mixins. Though, I'm sure there are exceptions.
I have a Brother Laser that did the same thing... however, it has a setting in it's web admin called "Replace Toner" with the options of Continue or Stop. All I had to do was select "Continue" and it kept printing until the toner was actually gone. No cartridge modification required!
This looks great. It's awesome that we can make sites like this that theoretically allow us to serve the same pages to desktop and mobile browsers. I'm curious though, is there any significant overhead to having mobile clients parse 1600+ lines of HTML, or is that a non-issue these days? Anyone have any data points on this?
I hear these sorts of things regarding hosting all of the time. However, in my experience, if you are working on an app that is large enough to warrant using a framework like Symfony or Zend Framework, you are probably going to also be using your own server. People don't build large expensive applications and then deploy to GoDaddy or something :)
I have traditionally used honeypot fields in this manner. Recently, however, I have noticed some false positives because of autofill features in browsers (especially Chrome). To work around this, I would add to the above that it may be useful to remove the field with the submit event on the form and then test for it's presence on the backend. Alternatively, just use the timestamp approach.
There was some interesting discussion about the current state of the hg-git plugin on the Changelog show last month (episode 0.4.9) when they interviewed Scott Chacon from Github.
It isn't too hard for someone who is already familiar Apache. On OS X, mod_php is not enabled by default, requiring new users to dig in and learn about apache config files and document roots. I'm not saying it is difficult, and it is obviously important to learn, but it would be nice to be able to have a 1 page "get started with PHP" tutorial.
Seems like the built in server would be most useful for newbies to get an application running. Think if how much easier it is to get a basic Rails app running to start learning compared to configuring Apache and PHP together.