Re: [-OP-] Opera轉向WebKit

看板Browsers作者t7yang (t7: 近 Opera 者赤)時間13年前 (2013/02/16 00:38)推噓8(8推 0噓 26→)

留言34則, 10人參與討論串2/3 (看更多)

http://alistapart.com/blog/post/opera-moves-to-webkit 選擇性的簡譯一些我覺得使用者會關心的問題，原文如上，有興趣請自行閱讀 ____________________________________________________________________________ We announced that Opera will switch its rendering engine to WebKit and JavaScript engine to V8 by building on top of Chromium (the open-source browser that powers Google Chrome). 透過在 Chromium（Google Chrome 的源頭開放原始碼專案）上的製作將成像引擎與 JavaScript 引擎轉向使用 Webkit 及 V8。 Opera 向 Webkit 提供了一個微小但具有象徵意義的貢獻給 Webkit——目前 Presto 引擎已實作的 CSS multicolumn。 \___________________________________________________________________________ Opera for desktops, Opera Mobile, and Opera Mini are all moving over to [Chromium] WebKit? 桌面版 Opera、Opera Mobile、Opera Mini 全部都會轉向 [Chromium] Webkit 嗎？￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣＼／￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ Eventually, yes. 是的，總有一天會。 \___________________________________________________________________________ The developer community seems pretty divided on this. Some say we’re moving towards an IE6-style “monoculture,” and some seem to think there’s enough diversity in WebKit implementations themselves that it’s a non-issue. What do you think? 開發社群的意見看起來很兩極。有些說我們正走向 IE6 式的獨佔文化，然而另一些人卻認為在 Webkit 的實作上本身有足夠的多樣性（t7：應該意指多個組織來貢獻與主導），所以這並非是個問題。你怎麼看？￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣＼／￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ I was initially worried, but it seems to me that WebKit has excellent diversity. And, of course, there is no monolithic WebKit. 一開始我也擔心過，但我覺得 Webkit 在多樣性方面非常棒。而且 Webkit 不存在所謂的的獨佔。 \___________________________________________________________________________ What impact will this have on web standards? Will this mean Opera has some say in Chromium’s roadmap, or are they more or less beholden to Apple/Google ’s decisions now? 這對網路的標準有甚麼影響呢？可以說 Opera 在 Chromium 的開發路線上或者說他們更多或更少的依賴 Apple / Gooogle 的決定？￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣＼／￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ We have independence to add (or remove) anything we like from WebKit or Chromium via our fork, but we aim to promote interoperability, not harm it. We have eighteen years of experience making browsers, and have participated in making many standards that are integral to the modern web (Media Queries, HTML5, native video, etc.) so we have lots of ideas to contribute. 我們有權力決定在我們的分支（t7：發行版）上對 Webkit 或 Chromium 做任何的異動，但我們的目的是推廣相互作業能力，而非破壞他。我們具有 18 年的開發瀏覽器經驗，而且參與制定過整合到現代網路的多項標準（Media Queries、HTML5、native video 等），因此我們有很多點子可以貢獻。 \___________________________________________________________________________ Can we expect radical changes to Opera products within the next version or two, or will it be a more gradual process? I can’t imagine a brand new rendering engine will just drop in clean. 我們可以期待下一個或兩個版本的 Opera 產品會帶來嶄新的變化嗎？還是你們打算循序漸進？￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣＼／￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ A new version for Android is being demoed at Mobile World Congress in Barcelona at the end of the month (come and say hello—I’m the guy with the pink mohawk, stuffed into a cheap suit and uncomfortable shoes). After that I can’t really speak to timescales as I simply don’t know yet. Android 上的新版本將會在二月底的 MWC 上展示。其餘的我真的不知道。 \___________________________________________________________________________ Will this free up Opera devs to work on new features, now that their primary concern isn’t just maintaining platform parity? 這是否會讓 Opera 開發團隊有更多時間去開發新的功能，目前他們最關心的就是是否只是僅僅維護平台一致性？￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣＼／￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣ I can’t comment on individual features of future products. But you can be sure that I’ll be fighting to get accessibility improvements in there, just as I’ve fought to get them added to specifications. 我無法針對未來產品中的某個單一功能做出評論。但你可以放心的是我著力於改善存取能力，就像我面對規格的態度一樣。 \___________________________________________________________________________ -- ※ 發信站: 批踢踢實業坊(ptt.cc) ◆ From: 140.113.73.123 ※ 編輯: t7yang 來自: 140.113.73.123 (02/16 00:40)

推

itsasemen

02/16 10:09, , 1^F

02/16 10:09, 1^F

→

itsasemen

02/16 10:10, , 2^F

02/16 10:10, 2^F

→

SicInfit

02/16 11:26, , 3^F

02/16 11:26, 3^F