[MeeGo-dev] browser engine and other big architectural decisions
Arjan van de Ven
arjan at linux.intel.com
Wed Mar 24 10:02:21 CDT 2010
On 3/24/2010 7:47, George Matveev wrote:
> this browser *engine* question was already touched upon many times
> here and it is certainly puzzling and deserves attention of those who are
> responsible for (architectural) decision making in this project
> (hopefully Intel team is reading this).
I'm reading ;-)
so from where I sit there are 2 separate questions, from an architecture pov.
1) The browser application
2) The "embedded web component" as used by various applications
for 2), there is no question for me that webkit is the right answer for this.
for 1), this is not really an architectural decision, it's an application that does not impact
other pieces around it per se... and this application is likely device class specific.
(phone, netbook, TV, etc all likely will use very different applications for browsing after all)
As such different device profiles in principle can have completely different technology for the implementation
internally to the application.
Having said that, personally I think that if you're doing a new browser or making a new decision, you pick
a webkit based implementation. But that's a personal opinion, not something that I feel belongs as an architectural
More information about the MeeGo-dev