Just had an interesting conversation with a collegue about the future of HTML.
It's function is clearly shifting from a markup language (well, language... i'm not sure) to an XML variant which will be used to position components and plugins.
After all, what more do we need than the basis of the HTML DOM with some includes of your preferred Ajax Framework or an EMBED tag to startup the Flex application? Programmers hardly type HTML anymore, all HTML snippets and components are generated by frameworks! The only reason why some of us do type HTML is because the framework just isn't supporting these few features we would like and we need to do some working around... But that will end when the frameworks are at their 2.0 version.
I think in a few years the meaning of HTML will move to some kind of configuration thing, like we used to have in the settings.ini file of your classic Windows application.
Thursday, 14 June 2007
Subscribe to:
Post Comments (Atom)
Labels
- Agile (10)
- SCRUM (10)
- management considerations (6)
- methodology (6)
- usability (5)
- Business Value (4)
- ria (4)
- flex (3)
- marketing (3)
- user centered design (3)
- Transition (2)
- application design (2)
- distributed SCRUM (2)
- maturity (2)
- microsoft (2)
- offline desktop applications (2)
- AIR (1)
- CSS3 (1)
- Firefox (1)
- HTML (1)
- HTML5 (1)
- International teams (1)
- PET design (1)
- Twitter (1)
- adobe (1)
- advertising (1)
- browsing (1)
- copy (1)
- customer experience (1)
- demo (1)
- design guidelines (1)
- filesystem (1)
- generations (1)
- incremental (1)
- iteration (1)
- maths (1)
- online applications (1)
- optimization (1)
- people (1)
- popularity (1)
- progress (1)
- projects (1)
- raking (1)
- ria projects (1)
- rounding (1)
- silverlight (1)
- social media (1)
- teams (1)
- time boxing (1)
- usability testing (1)
- web 2.0 (1)
- website design (1)
- website development (1)
No comments:
Post a Comment