Microsoft responds to Google's EAS move, sidesteps issue
Linked by Thom Holwerda on Tue 18th Dec 2012 00:03 UTC
Microsoft Microsoft has just responded to Google's move regarding Exchange ActiveSync. Sadly, instead of addressing the very real problems consumers are about to face, Microsoft starts talking about switching to Outlook.com.
E-mail Print r 6   · Read More · 155 Comment(s) http://osne.ws/kjg
Permalink for comment 545985
To read all comments associated with this story, please click here.
RE[17]: Comment by shmerl
by lucas_maximus on Thu 20th Dec 2012 18:54 UTC in reply to "RE[16]: Comment by shmerl"
lucas_maximus
Member since:
2009-08-18

Well clearly you do because every point you've made has been definitive: "you absolutely should do this / should never do that!" blah blah blah.


No, it is simply that I like to do things properly, if I have to be pragmatic about it I will be.

All because you want to try and convince me that you know what you're talking about. Yet the ironic thing is, using such absolutes only makes you seem inflexible and inexperienced (which I'm sure you're not, but you're not helping your case).


You are not that precious to me.

Actually no. The reason why is because some developers are inflexible and only target webkit.

The whole bloody point of targeted code is that you're writing code to support other browsers outside of webkit.

If you're writing targeted code and still only supporting webkit then you're a complete fail of web developer.


Sorry I don't target a browser, I target features of a browser. Writing standards compliant code wins you half the battle.

I have seen so many people complain about IE7 not rendering a page correctly. After putting it through a validator and making them fix it rendered correctly.

I got the look of "Oh it renders correctly now".

Depends on the layout of the site. Some layouts don't scale well for smaller screens so it makes much more sense to have a mobile style sheet. (yeah I know about how sites should dynamically scale well, and in an ideal world all designs would do so. But in the real world it isn't always practical).

Also some sites are too content rich for mobile connections (eg 3G), so it makes sense to cut down on some of the content (and I don't mean remove important content, I mean remove the unimportant content such as have comments on a separate page to the article. I know OSNews does this on their desktop site, but most blogs do not).

Also some sites might have custom fonts or Javascript to handle mouseover events, both of which just adds yet more bloat for users browsing via 3G.


Maybe you don't share this view. Maybe you're one of the numpties who things dozens of separate javascript and CSS includes makes sense. But I prefer to write optimised yet highly manageable code that works well on all platforms. Which means occasionally [/q]

It totally depends what tools you are using and what you are trying to achieve. We have a separate mobile site because our slot games are flash which doesn't work on some smart phones. That is a show stopper.

If you load scripts in an intelligent way it doesn't bloat there are numerous techniques. Some are server side (WURFL etc) and others are Client side (Modernizer, YepNodeJS and Media Queries etc).

I still think that server side browser detection should be kept to a minimum.

Serving different markup to different browsers should be avoided.
I'd rather people worked around the limitations of browsers than limit their site because of one or two crappy browsers.


I believe in progressive enhancement.

Reply Parent Score: 2