New blog domain: kula.blog

By K -
It's still work in progress but new posts will be published on  https://kula.blog/ Thanks to 11ty base blog RSS is working from the start so it should be easy to add to your reader if you still use any :) If now then I hope you can sign up to the newsletter where I'll be publishing new posts and interesting articles to it from time to time. Please use  kula.blog  from now on.
Post a Comment

Pollyfilling and Performance

By K -
Consider this post more like stream of thought, rather than complete manifesto, or whatever this looks like. 

Today I read http://www.impressivewebs.com/browser-performance-pickle/

This article is just about problem, maybe about problems our industry has with older browsers.
Progessive enhancement is awesome, but how in "real life" really make it working, how to convince you'r boss that this is good, how to convince customer? Sometimes You just CAN'T.

On the other side we have pollyfils, we make it working in older browsers. Add hacks, more html, even more CSS. Code is ugly but finally works everywhere! Everyone is happy besides You. After some time they want to change something on site, and You tell them ridiculously long estimation. Why, because this is nightmare to maintain, to test again and again if this little tiny images for shadows works as supposed in IE6. And what tell You them when this site is really slow in this old browsers? Impossible to fix. Google ranking is against any SEO specialist? Impossible to fix. (thanks Google BTW.)

This is stupid to make everything working and looking 'the same' in this older browsers. This make them slow to make site not useful to those old browsers anyway! I have seen this many times. Try to surf in IE6  on some "awesome" sites, this is no fun.

I recommend to read: http://www.impressivewebs.com/browsers-tvs/

How to we get here?

1: This site is best viewed in Netscape 4.
2: This is bad, site must be accessible for every browser.
3: Pixel Perfect... (we are here)
4: Progressive Enhancement

Progressive Enhancement will in my opinion will be "future" but for now we must educate to make it future! Like in times when there was sites created for one browser. Developers educate each other, and manages finally start to demand it... always, always the same. So now we are in opposite point.
We just need golden mean.

But for now we must educate, and see if big guys will help us educate users. I think about really big sites, that are pixel perfect now, despite it they announce that they are using progressive enhancement or not. Most of sites just look the same in every browser, and until we have something to prove our managers and clients that: They do that, You should want this too.

Consider this: http://yuilibrary.com/yui/docs/tutorials/gbs/
Can anyone point to me Yahoo! sites that really use it? I can't find any...

Pleas post any example sites in comments, or if there is already created list show me where.

Comments

Post a Comment

Comments:

Popular posts from this blog

How to simulate slow connection (developer proxy in Node.js)

By K -
Image
Update: If you use Chrome then you can use "Throttling" so simulate slow network for all your assets. This should be easier than proxy. Toggle device mode   Choose Network type. Refresh the page https://developer.chrome.com/devtools/docs/device-mode  Proxy: For some time I wanted to use some proxy for development and testing of eg. slow internet connection, but it was hard to find something useful and free. I know there is Charles but buy it to use it at most one in a month is not for me. I started thinking about Node.js, maybe I can write proxy for me? But fortunately I found one. https://github.com/nodejitsu/node-http-proxy With this module I can write really short code to create slow server: var http = require('http'), httpProxy = require('http-proxy'); httpProxy.createServer(function (req, res, proxy) { var buffer = httpProxy.buffer(req); setTimeout(function () { proxy.proxyRequest(req, res, { host:
Read more

Safari Mobile CSS VW and VH units bug.

By K -
Image
Recently we have created new version of mobil.aftenposten.no but soon after serving it to some users we spot this tweet:  https://twitter.com/Al3x4nd3rR/status/452047498111369216 . Basically titles were missing.... Then it started our effort to reproduce this bug. ... It was nightmare! First how to reproduce it: Open  http://krzychukula.github.io/vw_bfcache/  in Mobile Safari.  Click "Go to another page" link Leave phone for 60 seconds (longer is better) Click back button If you were lucky you should see some missing paragraphs and missing green boxes. How it looks: Bug: This one uses vw and vh for font-size. Both are 0 so we can see only 2 from 8 paragraphs. Those two are using only em for font-size. I was curious if it's only for font-size so I have added another test. I have added two boxes with width and height set in vw and vh with green background color. They parents have red background for contrast.  Most of t
Read more