mddw

Quality code ages well. Old is not an excuse for crappy or slow, neither you can so easily disclaim your own code.

Would you take fashion advices from someone with horrible and smelly clothes ?

I'm always amazed to see how people who give advice (and good ones in this case) are totally unable to follow them on their websites.

296 http requests. 1.85mb transfered. Yslow grade D.

So yeah, these are good advices. In fact, the OP should follow 'em if he wants to "survive".

At the begining, a responsive website was build around media queries.

Then it was media queries and a fluid grid.

Then it was media queries and a fluid grid and mobile first.

Now it's media queries and a fluid grid and mobile first and built around the content.

Tomorrow what ?

Meanwhile, responsive websites are as crappy as non responsive one, but 2x heavier because of the crazy CSS and all the async js.

If you can't detect the internet speed of your user, you can't make responsive websites, period. That's why the only good responsive websites are the text-content-only websites.

Come on, the linked post is nearly 2mb...

I know this is Hacker news, but hacking, bootstrapping or kickstarting are slowly becoming meaningless buzzwords.

Please please stop using them for anything.

Simply because my admin pages don't use a lot of JavaScript. Some Ajax, some image resizing... straightforward stuff, no need of a library.

When press is free, it's not free press anymore.

If a website is not behind some kind of paywall, he lives on ads and must enter the crazy linkbaiting/SEO dance.

TinyMCE have something like this, but yeah, it should be a easy-access function.

The only downer for me : it uses JQuery, which I often avoid in admin pages.

Clarke's lacks inline style and !important.

Sure, they should be used with care, but !important is actually really useful in responsive webdesign.

Show me some A/B testing showing a conversion increase when Retina proofing your website.

Old people with an iPad3 won't see the difference between a non retina and a retina website. They'll see which is the fastest and the easiest to use (because usually, pixel perfect guys are not too smart about UI.)

Retina-ready is a scam. We have neither the tools (SVG support too weak, no <picture> element, no good navigator.connection...) to provide a meaningful retina experience while respecting other users.

Speed trumps "beauty". Most often.

It should not.

An outdated computer/browsers sucks at resizing jpegs. A two year old high end Android smartphone too.

Minimizing HTTP requests, avoiding FOUC, using only one version of JQuery (or, even better, none), using CSS sprites... there are countless optimisations which are more important and seldom used.

Retina is a buzzword and a buzzword resolution. If you target the 0.1% rich hipsters, yeah, it's important. If you've real users browsing in 1024x768 on a four year old laptop and a 2Mbps broadband, it's not.

When Amazon'll use Retina img, that's when it'll be a standard practice.

Maybe better maps, but no street view, which is kind of a deal breaker for me as an "urban pedestrian".

French here. The man behind this "hacking" was interviewed here : http://www.pcinpact.com/news/74060-exclusif-pcinpact-intervi...

The 123456 pass was for a phone service dedicated to the Banque de France itinerant techies.

The "hacker", when asked a password, tried randomly 123456. He gained access to complex options (each being quite technical.) He tried one randomly, it triggered a kind of panic mode.

He only discovered it was a Banque de France telephone number when arrested by the police, four years ago.

What I can't figure is why 2D transitions needs to be hardware accelerated to be smooth in mobile Safari.

Neither why their mighty Nitro JavaScript Engine can't handle smoothly a setTimeOut based fade in/Out.

Google Chrome on 8 years old hardware (less powerful than actual iPhone hardware) renders the moving web better.

Safari is a poor mobile browser.

VideoJs is free (ass free speech), Flowplayer is not : it's a badgeware.

A 100% width <video> keeps its natural aspect ratio. Like an <img>.

Globaly, yes. But if you want, per example, to target China, IE6 is mandatory. http://www.ie6countdown.com/

(and even Japan is at 4.7% according to this site. 4.7% is significant enough.)

To make a <video> responsive, you only have to set its width to 100%... not a big deal.

But yeah, I love flowplayer, it has a nice js API. Too bad it's not IE6 compatible.

I don't know about the UK or the US, but in France, Bankruptcy don't always mean paying your company's debts. Small business often start as "limited responsability companies", where you can only loss your capital.

Yes, it does. Not linear larger files, but larger files at constant quality. His examples are conveniently chosen to sell his book. 20% bigger is 20% too much for a non essential asset.

Don't retinafy at all. You should not assume your user has LTE speeds on his shiny iPad. As long as webdevs won't have a better navigator.connection, retinafying should be avoided.

On the web, loading times trump beauty.

I agree.

There're some prefixed properties which work on all major browser since forever (on a web scale)... but there're still a draft. Reading the minutes of the CSS group is enlightening : everything is really really slow.

Moreover, lots of non-defined prefixed properties don't break pages at all. Rounded corners per exemple are nice, but not displaying them is not a deal breaker. Same thing for transitions : site using them often provide a javascript fallback for non webkit browser.

If Opera wants to support webkit properties, they have to spoof their UA : lots of mobile website are designed for iPhone and Androïd (yes, that's not ideal, but it's a fact). It's the 00's mess again...