The State Of Web Development Ripped Apart In 25 Tweets By One Man
1–10 of 28 posts
Re: The State Of Web Development Ripped Apart In 25 Tweets By One Man
#2I disagree that the app stores are successful because of superior APIs, they are successful because you can charge for apps and make money.
But he is correct about Microsoft and web standards committees.
Re: The State Of Web Development Ripped Apart In 25 Tweets By One Man
#3A great rant by a practitioner who wants progress to go faster, ideologies and committees be-damned.
But, a little revisionist about why browser innovation slowed. It wasn't Microsoft yielding to standards demands that slowed their pace; it was Microsoft's de facto victory in (for a time) neutralizing the business possibilities of competitive browser development.
It took a while for alternate models that could sustain further browser evolution -- the Google placement payments to Mozilla, Apple's sponsorship as a complement to their other platforms -- to grow to take the place of the original Netscape dreams.
Hewitt's prescription seems right, though: a bit of healthy disdain for waiting for standards bodies before deploying new things, and some added respect for even those proprietary offerings -- like Flash -- that kept expanding capabilities and user expectations when browsers didn't.
Re: The State Of Web Development Ripped Apart In 25 Tweets By One Man
#4I know for a fact that my grandparents would find it a big deal to have to launch different browsers for different sites, and I'd venture to suggest that the majority of web users feel the same.
Re: The State Of Web Development Ripped Apart In 25 Tweets By One Man
#5> So launch a different browser. Not a big deal.
> […]
> As someone who has tried to do both cutting edge native and web iPhone apps, iPhone Safari is a joke compared to iPhone Cocoa
What he is basically saying is developing natively instead of for the web can give a better result, and he would prefer to drop cross-browser compatibility and just have users launch whatever browser he developed the app for.
The question is why develop for the web at all if your apps only run in a certain browser? He seems to make the assumption that while his app can’t run in all browsers, the browser it does run in is available “on all platforms”.
I think he needs to rethink what the purpose is with HTML, semantic markup, and having a standard.
Re: The State Of Web Development Ripped Apart In 25 Tweets By One Man
#6> So launch a different browser. Not a big deal. > […] > As someone who has tried to do both cutting edge native and web iPhone apps, iPhone Safari is a joke compared to iPhone Cocoa What he is basically saying is developing natively instead of for the web can give a better result, and he would prefer to drop cross-browser compatibility and just have users launch whatever browser he developed the app for. The questio…
>The question is why develop for the web at all if your apps only run in a certain browser?
This is a mental block. You're thinking about it from a developer's perspective. He's talking about how to make the web better for users.
Re: The State Of Web Development Ripped Apart In 25 Tweets By One Man
#7A great rant by a practitioner who wants progress to go faster, ideologies and committees be-damned. But, a little revisionist about why browser innovation slowed. It wasn't Microsoft yielding to standards demands that slowed their pace; it was Microsoft's de facto victory in (for a time) neutralizing the business possibilities of competitive browser development. It took a while for alternate models that could sustai…
The revisionist history stood out to me as well. We're supposed to believe that MS stopped developing IE6 because "the DOJ and web standards commies intervened", and it was just coincidentally at the same time they killed of Netscape in market share?
We're supposed to believe that the W3C (founded in 1994), and the Web Standards Project (founded in 1998), had to work for years and just coincidentally managed to browbeat MS into stopping development on IE at the same time MS beat Netscape? That they were even capable of "bullying" a company like MS into stopping development on one of their products?
My own exposure to web standards was Zeldman's first "Designing With Web Standards" book, published in 2003. My experience has been that the standardistas have spent most of their time trying to push MS to further develop IE to support standards (which it still lags at), not trying to hinder innovation.
Re: The State Of Web Development Ripped Apart In 25 Tweets By One Man
#8I think the real solution is not to provide more advanced features in the browser, but to provide more primitives. Lots of programming languages over the years have, at least for a while, compiled to C. C is an almost universal primitive. The web doesn't have a universal primitive. HTML, CSS, and JavaScript are high level languages. If you try to use a high level language without ever accessing lower level functions, you will eventually run into something you can't do. The web has hit that point. We need a way to fall back to lower level languages when the abstractions become too leaky. The web needs a C: a language which can do anything if you put in the time and energy to make it work, which is blazing fast, and which is available everywhere.
Re: The State Of Web Development Ripped Apart In 25 Tweets By One Man
#9A great rant by a practitioner who wants progress to go faster, ideologies and committees be-damned. But, a little revisionist about why browser innovation slowed. It wasn't Microsoft yielding to standards demands that slowed their pace; it was Microsoft's de facto victory in (for a time) neutralizing the business possibilities of competitive browser development. It took a while for alternate models that could sustai…
My impression of IE is that Microsoft stopped developing it right at the point when they realized "Oh shit! If this gets any better, it could replace Office!"
Re: The State Of Web Development Ripped Apart In 25 Tweets By One Man
#10As long as most sites don't require ie, because i don't have windows.