|
Posted by Mario T. Lanza on September 29, 2004, 11:57 pm
Please log in for more thread options
I have been authoring web sites for several years now and recently
come to value web standards (as touted by Zeldman and many other web
gurus). I have noticed with frustration that there are so many hacks
(tricks to take advantage of browser buggy-ness) and special rules to
be remembered in order to make sure that any one page displays
properly in the many popular browsers.
This leads me to...
Since the many programmers authoring their own browsers (IE, Firefox,
Mozilla, Opera, Safari, etc.) ultimately have to implement the same
W3C specs, why don't they all work together to develop one engine/DOM
for rendering web content and share it?
The browsers, could simply be differentiated by the
features/interfaces they offer. Wouldn't this shared effort result in
making the web a better place for every one -- both the users and
designers?
Am I missing something?
Sincerely,
Mario T. Lanza
Clarity Information Architecture, Inc.
2004.09
|
|
Posted by Leif K-Brooks on September 30, 2004, 6:34 am
Please log in for more thread options
Mario T. Lanza wrote:
show/hide quoted text
> Since the many programmers authoring their own browsers (IE, Firefox,
> Mozilla, Opera, Safari, etc.) ultimately have to implement the same
> W3C specs, why don't they all work together to develop one engine/DOM
> for rendering web content and share it?
All of today's rendering engines -- Gecko, KHTML, Presto, MSIE, Tasman,
etc. -- were created for what were perfectly sane reasons at the time.
You're right that it would probably make sense to merge them now, but
that would mean abandoning lots of code people have worked hard on, not
to mention the effort it would take to get it all working right. And
that's even assuming it's possible to get all of the browser projects to
work together, which seems a little far-fetched.
However, some merging does happen: Safari uses KHTML, an open-source
rendering engine created by the KDE project; Mozilla and Firefox share
the Gecko rendering engine; and WYSIWYG editors like GoLive and
Dreamweaver license Opera's Presto rendering engine for previewing web
pages. Even IE's proprietary rendering engine can be embedded in other
browsers with ActiveX without paying.
|
|
Posted by Mario T. Lanza on September 30, 2004, 9:41 am
Please log in for more thread options Yes, I realize that there is a great deal in the sharing of rendering
engines between certain product. Despite this, there are still
several engines and web developers must still go through the arduous
process of viewing their pages in several browsers to make sure all is
well.
Don't ask me why Star Trek: The Next Generation keeps coming to mind
-- I haven't watched it in years -- but I keep thinking how great it
would be if humanity (despite it's desire to compete in this
capitalistic world) would come together in some areas to work toward
the good of all. Yes, a little idealistic... but still I hope.
It just seems that web developers have to spend countless hours and
learn countless hacks if only to make websites available to the world.
Why should so many have to struggle to learn and solve the same
problems? The real blessing would be to have all web developers work
on their content and business solutions rather than browser hacks.
Long live web standards!
Mario
|
|
Posted by DU on September 30, 2004, 9:00 pm
Please log in for more thread options Mario T. Lanza wrote:
show/hide quoted text
> Yes, I realize that there is a great deal in the sharing of rendering
> engines between certain product. Despite this, there are still
> several engines and web developers must still go through the arduous
> process of viewing their pages in several browsers to make sure all is
> well.
>
> Don't ask me why Star Trek: The Next Generation keeps coming to mind
> -- I haven't watched it in years -- but I keep thinking how great it
> would be if humanity (despite it's desire to compete in this
> capitalistic world) would come together in some areas to work toward
> the good of all. Yes, a little idealistic... but still I hope.
>
> It just seems that web developers have to spend countless hours and
> learn countless hacks if only to make websites available to the world.
> Why should so many have to struggle to learn and solve the same
> problems? The real blessing would be to have all web developers work
> on their content and business solutions rather than browser hacks.
>
> Long live web standards!
>
> Mario
The MSIE 7 dev. team has a blog site and some people requested that MSIE
just adopt Gecko as their new HTML engine. It's not that a crazy idea,
after all, not that far fetched..
DU
--
The site said to use Internet Explorer 5 or better... so I switched to
Mozilla 1.7.3 :)
|
|
Posted by Mark Parnell on October 1, 2004, 10:48 am
Please log in for more thread options declared in comp.infosystems.www.authoring.html:
show/hide quoted text
> It just seems that web developers have to spend countless hours and
> learn countless hacks if only to make websites available to the world.
How else are we going to make money? If all browsers rendered everything
the same, anyone could do it!
--
Mark Parnell
http://www.clarkecomputers.com.au
|
| Similar Threads | Posted | | Simple Open Source CMS | January 23, 2006, 9:00 am |
| looking for open source forums..... | September 8, 2006, 5:48 pm |
| Which open source text editor to use | March 15, 2007, 2:25 pm |
| Help out at the first open source hospitality network | November 23, 2007, 10:49 am |
| Are there any open source ajax html editors? | September 27, 2006, 6:32 pm |
| open source PHP/MySql project desperate for volunteers | September 26, 2004, 7:34 pm |
| Open Source IDE, Windowing System and Desktop Environment (31kb)* | August 3, 2006, 2:11 am |
| Seeking open source web stats program - which does not report crawlers | February 11, 2009, 4:55 am |
| CFP -- International Symposium on Open Source Intelligence and Web Mining 2009 | March 17, 2009, 11:04 am |
| OASIS Symposium 2007 - eBusiness and Open Standards | March 1, 2007, 8:44 pm |
|
> Mozilla, Opera, Safari, etc.) ultimately have to implement the same
> W3C specs, why don't they all work together to develop one engine/DOM
> for rendering web content and share it?