Whats with the hype over html5 when the standard is not even complete yet.
-
I have developed web apps in multiple techs asp .net, asp .net mvc, jsf etc. Also I have used jquery and the multiple frameworks. All of which are pretty cool. I also see alot of promise in HTML 5 which of course is the future standard. But my question is this. Different browser will implement different features of html5 so we as devs are still going to have to be concerned and code according and check to see if the html5 feature we need is implemented so this aspect wont change from html 4.01 Now for business apps my company has used silverlight which works the same across all browsers. We dont have the tablet requirement yet as this is a desktop web app. And development was alot less painless as my team are all .net software engineers. What do you guys think about this debate. I just got a feeling JS and HTML5 wont solve 'everything' like alot of people think. Cheers
-
I have developed web apps in multiple techs asp .net, asp .net mvc, jsf etc. Also I have used jquery and the multiple frameworks. All of which are pretty cool. I also see alot of promise in HTML 5 which of course is the future standard. But my question is this. Different browser will implement different features of html5 so we as devs are still going to have to be concerned and code according and check to see if the html5 feature we need is implemented so this aspect wont change from html 4.01 Now for business apps my company has used silverlight which works the same across all browsers. We dont have the tablet requirement yet as this is a desktop web app. And development was alot less painless as my team are all .net software engineers. What do you guys think about this debate. I just got a feeling JS and HTML5 wont solve 'everything' like alot of people think. Cheers
Its a bit like Wireless-N. It was in mass use years before it was ratified. Early adoption almost ensures a successful protocol or product. The early adopters help to iron out the issues, so when it is finally ratified, it should be a pretty damn robust spec.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
-
Its a bit like Wireless-N. It was in mass use years before it was ratified. Early adoption almost ensures a successful protocol or product. The early adopters help to iron out the issues, so when it is finally ratified, it should be a pretty damn robust spec.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
Except that it's web browsers so we end up with a bunch of none spec specification sites that need more browser specific hacks.
I'm not a stalker, I just know things. Oh by the way, you're out of milk.
Forgive your enemies - it messes with their heads
-
Except that it's web browsers so we end up with a bunch of none spec specification sites that need more browser specific hacks.
I'm not a stalker, I just know things. Oh by the way, you're out of milk.
Forgive your enemies - it messes with their heads
Pete, that is very true, but without risk takers and evolution where would we be today? Still hundled in caves grunting at each other. (okay, we maybe still do that in scotland or the smoke room offshore, but thats another story :) )
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
-
Pete, that is very true, but without risk takers and evolution where would we be today? Still hundled in caves grunting at each other. (okay, we maybe still do that in scotland or the smoke room offshore, but thats another story :) )
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
-
Just making the point tho that the spec for html5 wont be finished for at least another couple of years and even then we are going to have to deal with the cross browser issues.
Yep, can't disagree. Thats why I think it is important to have an agressive product lifecycle, like Chrome, compared to the relatively slow cycle of releases like MS, and somewhere in between like FF.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
-
I have developed web apps in multiple techs asp .net, asp .net mvc, jsf etc. Also I have used jquery and the multiple frameworks. All of which are pretty cool. I also see alot of promise in HTML 5 which of course is the future standard. But my question is this. Different browser will implement different features of html5 so we as devs are still going to have to be concerned and code according and check to see if the html5 feature we need is implemented so this aspect wont change from html 4.01 Now for business apps my company has used silverlight which works the same across all browsers. We dont have the tablet requirement yet as this is a desktop web app. And development was alot less painless as my team are all .net software engineers. What do you guys think about this debate. I just got a feeling JS and HTML5 wont solve 'everything' like alot of people think. Cheers
The thing with HTML5.0 is that the browser vendors are talking to each other now and trying to out compete each other on implementing the standard as it reaches various levels of complete. It's not really about the monolithic adoption of a giant standard, but the process each vendor is going through to implement, verify and change the standards for each feature. Each browser starts with extensions, in their own custom namespace usually as a first pass in implementing the standard. That is fed back into the standard. Once there is agreement on the standard and it is flushed out unambiguously then the implementations are moved out of the namespaces into the actual api/name. Once a feature goes through that process for the browsers, it's pretty safe to use. As far as one technology to rule them all goes, that will never happen. However you can do some pretty amazing things with a little bit of js and html these days.
Curvature of the Mind now with 3D