<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><blockquote type="cite"><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">The most recent effort from our side is to provide WebRTC support.</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"></blockquote></div><br><div>Great. Features, like performance improvements and bug fixes, are a great way to contribute to WebKit. </div><div><br></div><div><blockquote type="cite">As it was pointed in the first email of this thread and by Hugo's<br>email, Nix "targets whoever wants to have a hardware accelerated<br>WebKit2 port on UNIX-based devices, with a minimum effort”.</blockquote><br></div><div>Yes. I read that email. Then I asked who “whoever” was, and the answer was “nobody”.</div><div><br></div><div>My position is simply this: Every port has a cost, so every port needs at least a prima facia explanation of its corresponding benefit.</div><div><br></div><div>If the NIX port is what gets you guys excited about WebKit, and the end result is a great implementation of WebRTC, that’s great.</div><div><br></div><div>But, six months from now, if the NIX port still has no adopters, and the only activity it brings to WebKit is the occasional rude email from Ossy, that’s not so great.</div><div><br></div><div>Geoff</div></body></html>