Why is he called a Mozilla blogger? He doesn't work for Mozilla foundation or Mozilla corp as far as I can see (nor does he claim to). His linkedin states he associates with the "Mozilla community", but that's hardly an official representative of Mozilla as "Mozilla blogger" implies.
I still don't understand why they couldn't just introduce a new keyword that has the same meaning as a missing semicolon. Call it 'ret' or something as a 'lesser return'. Relying on ppl to be semicolon hunters is poor for readability.
It also means you can't put more expressions on the same line because doing so requires a semi-colon which then eliminates the special semicolon behavior. Having an explicit 'ret' keyword means you could accomplish that and have more expressions for a separate block on the same line if desired.
Oh good, now it only takes 24 people to design and implement a page with 'proper' HTML 4/5 + CSS 1/2/3 + JS that is 'responsive'.
I stopped reading A List Apart when it became rather apparent that they either delight in adding more tedious work to a web designers check-list, or just truly seem to think every project needs this many people working on it (or someone with insane mental capacity that can actually do half the stuff they recommend).
The mental overhead involved in modern web design automatically precludes the vast majority of either normal folks, or companies not big enough to have 24 people make a web page.
When we can reduce the effort needed to do this properly, then it'll be worth giving people a pat on the back. Not when it takes 24 people to make a page that works properly on a few devices.
I've met total posers that can whip up the little snippets that people have time for in an interview... and I've met great coders who crash and burn a live code session due to interview stress.
I've consistently found open-source code to be a much better sample since the person being interviewed is not under such pressure when writing it. And yes, the pressure from being in a room with 3 ppl watching you is very different from "deadline pressure" to complete a task when employed.
I don't think the github resume is going to be the standard for quite awhile, but I know it makes my job when hiring much easier when we can discuss code and techniques used in an open-source project the interviewee wrote, than arbitrary questions that only prove he's recently memorized an algorithm book.
The real thing developers should think about, is the competition. This is what made "has college degree" an easy filter for employers. If you have 800 applications, tossing the ones missing a github repo in addition to the college degree trims it down a bit more.
Will you miss some possibly great people? Absolutely. Same with the college degree filter. But you'll still likely end up with a bunch of "would like to hire" candidates and it'll be easier to see what their work actually looks like. If you're applying for a job, you should absolutely consider how to stay ahead of the competition, and I'm sure companies in the future when bombarded with so many applications will add things like this to the resume filter.
Love how there was obviously no testing of the site on Firefox, as clicking the video pause or volume buttons hides the entire video. Pause/volume works fine on Chrome/Safari of course.
Hate to rain on your parade, but ISP-level NAT is coming (it's already here on mobile) and it breaks P2P. Hole-punching doesn't work, you can't manually open ports, and they don't support UPnP. If everyone is behind a nat who is left to tunnel through? Why, a central platform! Skype already went down this road.
As a bunch of other people in the comments have noted, Firefox can take a huge amount of memory, the one thing they also have in common.... is the Firebug extension. It should come as no surprise to them then that Firefox is not actually leaking the memory... Firebug is. A quick Google search for "Firebug memory leak" will lead to multiple examples of massive Firebug memory leaks.
It's a bummer that Firefox gets the blame for Firebug's memory leaks. If people would like to avoid that, the best thing would be to use Firefox's multiple profile feature so that they activate/install Firebug in a Developer profile, and keep their general browsing profile without Firebug. It's rather amazing just how much, and how fast Firebug can leak memory as using a separate profile will make abundantly clear.
Since its fairly easy to composite multiple WSGI apps together, one could run a few different Python WSGI-based apps under a single multi-threaded process to take full advantage of the free quota. That would work with Pylons/Pyramid/Flask and other Python web frameworks that don't rely on a single set of module global settings (Django).
I think you missed the bit about Pylons being a 'glue' framework between other packages. Those packages have gotten quite a few new features over the years, and they continue to get new features regardless of whether Pylons users use them.
This is the kind of nice thing about using multiple open-source packages that are in heavy use throughout the Python world beyond just web frameworks (unlike web2py).
