Rust

So the concern of being able to cache the CSS (and delivering a smaller amount of data in subsequent requests) is now a non-factor when it comes to maximizing your page speed (or minimizing paint time, or however you want to describe it)?

Yet it remains, sadly, all too accurate. Newer tools like SASS and LESS help a little, but not enough.

I would lean towards 'no'. Adding letters to a common word is currently much less common than removing vowels or combining consonants, so will be slightly harder for people to remember.

The exception might be if you have social curating, in which case a play on Digg might work out - vidd.io would be a good domain for that :)

Personally I would look for a word that is related to video, but is not a direct step from misspelling it.

Helpful answer: Python is a programming language. It can be used to create scripts, making it a scripting language as well.

More or less by definition, a scripting language is a programming language.

In a practical sense, and as stonemetal says, there is no real-world difference between a programming language and a scripting language.

In a technical sense though, one might consider a programming language to have a compiler and linker and debugger and able to create stand-alone executable files. Most scripting languages can also do that these days.

Perhaps the best guide then is intent - if a language is intended for script tasks (Windows/DOS batch files, for example, or even PHP), it is a scripting language. If the language supports a wider focus, it is a more general purpose programming language (Python, C, PERL, Java, etc.).

Ultimately, the best tool for the job, selected from the tools you know :) If you're writing a web application, there are a few languages either explicitly designed for that (PHP is a good/bad example), but many other languages can do it as well (Python, C, PERL, Java, etc.). If you're writing a desktop application, PHP would not be your best bet, but Python might not be either. Ditto mobile apps.

You, sir, are looking for the More Fields plugin (http://wordpress.org/plugins/more-fields/), and possibly the More Types plugin (http://wordpress.org/plugins/more-types/).

MF lets you add custom fields to any existing post type, and MT lets you create new custom post types (like, say, Music Events) that you can attach fields to using the MT plugin.

I've started doing DDP Yoga (http://www.ddpyoga.com/ - warning, autoplaying video) along with push-ups, squats and a bunch of stuff with a pile of dumbbells. With the help of an in-home personal trainer, I've gone from weighing 265 pounds (and getting shin splints going up a steep flight of stairs) to 215 pounds in 7 months. I took January off to rest up and give my ankles some time to relax (I broke both of them in 2000 and they sometimes hurt), and only gained 5 pounds.

Now I've added the yoga to my routine, I'll be going pretty strict on the diet starting this weekend (yes, I still drank pop and alcohol and ate chips and occasional McDonald's during those first 7 months). My goal is 190 pounds by June 1 - here's hoping!

So good luck to you, sir! It can be done :)

Hitchhiker's Guide to the Galaxy first, and Nightfall (both the short story and the later novelization) second.

True enough. But all they'd have to memorize is one hard password (or even a pattern like 102938), and one modifier pattern based on the URL of the site.

A simple example, using 102938 as the base password would be taking the main name part of the url (eg. www.google.com would just be "google"), converting each letter to a number (g = 7, o = 15, o = 15, g = 7, l = 12, e = 5), adding them all together (61), divide that by the number of characters used (61 / 6 = int(10.16) = 10), then add that result to every pair of numbers in the original password (10 + 10 = 20, 29 + 10 = 39, 38 + 10 = 48), giving you a password of 203940 for that site :)

EDIT: forgot to make this hard to crack. Again, the pattern approach can work - 203948 for "google" could easily and predictably become "go20og39le48@mycompany" or some such.

My brains alone. Over the years I've developed a pattern I can remember easily, and apply another pattern to it based on the site or app's name. It's a simple math formula that changes the entire password instead of just applying a suffix or prefix to an existing strong password.

Ironically, the only site this fails on is my banking site which has wish-it-was-2-factor authentication and a limit of 8 characters for the password. Stupid.

There's a min()/max() polyfill at https://github.com/indyarmy/jquery.cssMinMax.plugin right now. Someone with more patience might be able to extend it to support calc() as well.

Recently, I'm all about Python and Flask (or Web2Py for simpler things).

I seem to remember having a 30 minute bus ride to school through elementary school, and if I missed the bus, it was an hour's walk (though I could do it in about 10 minutes by bike if the swampy bit was mostly dry).

I guess I'm fortunate that my parents not only trusted me to do that, but encouraged it.

That said, I have a face for radio - they probably didn't think anyone in their right mind would even attempt to try and steal me...

I've used http://www.merchant-accounts.ca/ in the past and been happy with them.

In your example, if both developers are using TABs instead of spaces, why would it matter that one sees it as 5 spaces and the other as 8? It's still just a single TAB character either way.

Plus, each developer has the freedom to choose how many spaces a TAB is - I like 8 when I'm using my big monitor, but I prefer 4 on my laptop. With TABs, I can see it both ways depending on the machine.

On the off chance that I'm ever actually editing in a smaller window, I can even set it to 2 characters instead, but when I open that file again on another machine, I can see it as 4 or 8 characters.

I'm no Python expert, but the only reason I can think of is a combination of developer inertia and tradition.

In most IDEs, a TAB can be displayed as any number of equivalent spaces (8 being the common indent size), so if I switch back and forth between my big monitor (8) and my laptop screen (4), I can view the code with an indent relative to the width of the screen.

If that code uses spaces, I'm usually stuck seeing an indent of 4 on the big screen monitor - something I find irritating because it makes it harder to visually scan and parse code quickly.

So, even in Python, I always use TABs whenever I have the choice. It's just more flexible.

I should be noted that XQuartz (http://xquartz.macosforge.org/) is required in order to install Python on Mountain Lion (and possibly Lion as well).

The driver for not paying attention, same as now. A road painting might be a distraction, but it will only panic you if you see it at the last moment - which should only happen if you weren't watching where your speeding, multi-ton, flammable transportation machine was going on a residential street.

Still one of the best SF shorts ever written.

I just received my retina MBP, and it's magnet is actually substantially stronger than the one in my old MBP. I do hate the "T" design, though.

I've never identified a strong correlation between my music playing and coding, but I've learned guitar, bass, saxophone, sousaphone, trumpet, piano, ukelele and drums over the years, and I know enough about violin, cello, upright bass and flute to not sound like a complete tool.

I guess I'd equate that to the ability to write in specific languages (PHP, Python, ASP, Javascript, C) and the ability to read other languages (Perl, Ruby).

I've no doubt that being able to effectively and efficiently learn at one (coding or playing) is incredibly helpful when learning the other one.

Setup costs - PHP has a low barrier to entry in the sense that Apache's mod_php5 is a simple "a2enmod php5" command away. Even PHP-FPM with Nginx is only a few well-documented configuration options away from working.

Currently, no other language can match that. They either require a VM running (Java, Ruby, etc.) or at least have a compile/build step (Python).

UWSGI has a lot of promise, but until it's as easy to get configured as PHP-FPM, PHP is still way easier than everything else.

Requisite link to http://appwithphp.com/ - some basic minimal knowledge and stuff to make sure what you write is written as right as possible :)

One way might be to run the audio stream through a speech-to-text engine and parse the resulting transcript.

A video recognition system could also be used to identify faces, landmarks and common objects.

A web developer needs to understand the entire chain of technology, from his text editor or IDE all the way to the browser. You don't need to be able to build a server from scratch (although you probably should be able to), but you need to understand how the pieces fit together (WSGI, mod_php, PHP_FPM, CGI, for example) and that includes which pieces of that chain can cache, might cache, will cache, and how they cache.

The front-end developer needs to be more concerned with browser-related issues, but doesn't need to know anything about the server stack (typically). The back-end developer likewise doesn't need to concern him/herself with browser issues, but needs a solid grasp of everything behind the browser.

A web developer has feet in both worlds and needs to understand much more than the front-end and back-end developers.

As an analogy, a gynecologist might be a front-end developer. He has a basic understanding of the entire human body, but specialized in this one area and everything related to it. People like to hang around him, hoping something will rub off.

A neurosurgeon might be more of a back-end developer (not what you thought, eh?). He's concerned with the code running things and how it will react with everything else. He can be hard to talk to, but always interesting.

The dermatologist is your UX guy. Presentation is his game, and nothing else (but he still understands the pieces that interact with his domain). His home is always awesomely decorated, but not always functional or obvious (the three shells on the toilet).

A general surgeon is the web developer. Solid understanding of everything, great at finding and solving problems, but knows when to leave something to the specialists. He lives in the home you wish you had, and his pool table always has great action.

I got carried away with that, but the tl;dr is: the web developer needs to understand the entire chain of his/her domain. There is no piece too small that you don't need to know something about it - like how it works, or how to fix common problems with it. From editor to browser, you need to understand how it all fits together.

"fragrant abuse" is sadly one of the better grammatical issues with this post. I might use it somewhere...

I would say that any good web developer should know how caching works - not just in browsers, but also proxies, firewalls, and every other link between your language parser (which may also cache) and the user's browser. It's "domain knowledge".

I always use the integer representation. I believe (no testing) that it is faster due to the lack of a conversion step, math is always in seconds, and as long as the number you store is based on UTC (or GMT), there are no timezone issues.

For @gregjor's answer (having the DB create the date for you), it seems that if you actually need to know the timestamp of a newly inserted or updated record, you will actually need to make 2 SQL calls, since the record itself is not returned by UPDATE or INSERT.

Click: http://www.coderegator.com/

If they say no, I'd suggest Milles Bornes - a French card game from the 50s I used to play and love until I lost the cards back around the turn of the century :(

I consider this to be a UX failure: visit page, adjust one slider, select something from a pop-up, re-adjust the same slider, and when I hit the Back button nothing happens. Click Back again, nothing happens. Long-click the Back button and see 20 or 25 entries for the site even though I never left the front page or obviously loaded new content.

If they dump the JS that obliterates my browser history that way, then I would agree that it is indeed slick.