bdash

17 ms·

121.
by bdash 13y ago
The whitepaper at http://msdn.microsoft.com/en-us/library/windows/hardware/gg4... indicates that Windows timer coalescing requires an application to explicitly opt in. The article describes OS X Maverick
122.
by bdash 13y ago
SpiderMonkey uses JavaScriptCore's regular expression JIT, YARR (Yet Another RegExp Runtime).
123.
by bdash 14y ago
The Qt port of WebKit uses JavaScriptCore, not V8.
124.
by bdash 14y ago
Speaking as someone that has spent time working on a web browser, that would be a fantastic policy, both for browser developers and for web standards in general.
125.
by bdash 14y ago
Nitro is Apple's marketing name for JavaScriptCore, so UIWebView and Safari both make use of Nitro. The difference you're thinking of is whether a JIT compiler is used. That difference has nothing to do with the age of the version of WebKit
126.
by bdash 14y ago
I'm not sure what you mean by UIWebView being an "older implementation of webkit". UIWebView uses the same version of WebKit as Safari on iOS, which is essentially the same version of WebKit as is shipped with Safari on OS X.
127.
by bdash 14y ago
Is it safe to assume that any bugs that you're running in to are being reported to the browser vendors?
128.
by bdash 14y ago
> Webkit isn't "Chrome in a box" either. The Chromium Embedded Framework ( http://en.wikipedia.org/wiki/Chromium_Embedded_Framework ) isn't too far from that. I'm not sure if Opera is using this project in particular, but they do mentio
129.
by bdash 14y ago
And their first contribution is already attached to https://bugs.webkit.org/show_bug.cgi?id=15553 !
130.
by bdash 14y ago
Yes, I'm sure. The same core rendering engine, known as WebCore, is shared between both WebKit1 and WebKit2 on OS X. WebKit1 is used by most applications that use a WebView to display web content, while WebKit2 is used by Safari. The differ
131.
by bdash 14y ago
At http://my.opera.com/ODIN/blog/300-million-users-and-move-to-... they state they're switching because they feel it is a waste of resources to maintain their own rendering engine. I'd be surprised if the JavaScript engine was a big facto
132.
by bdash 14y ago
WebKit2 is a new API layer on top of WebKit, not a new browser engine. It has been used by Safari since v5.1.
133.
by bdash 14y ago
The press release notes that they're using the Chromium port of WebKit, so it's very likely that they'll be using V8 as a JavaScript engine.
134.
by bdash 14y ago
In an email to the WebKit development mailing list[1] Håkon Wium Lie, the Opera CTO, mentioned that they've had engineers working on WebKit for a while now, and they'll soon be contributing their work on multi-column layout to the WebKit pr
135.
Opera moves to WebKit(my.opera.com)
938 points by bdash 14y ago|282 comments
136.
by bdash 14y ago
That is incorrect. As the article you link to states: > Webkit takes a very different approach, and very intentionally. They believe it's better to keep the text invisible until the font is ready. This way, there is no moment where the
137.
by bdash 14y ago
My guess would be that data detectors are used to detect and format links in incoming messages.
138.
by bdash 14y ago
> WebKit was open sourced roughly a week (June 7, 2005) before Nokia announced the port to their phone (June 13, 2005). That means that Nokia was able to do the port in less than a week with (presumably) a few competent developers. Whil
139.
by bdash 14y ago
This matches my recollection of things as someone that followed WebKit from shortly after Safari was announced, and became actively involved when the open source project proper started up in 2005.
140.
by bdash 14y ago
If that is the logic involved then why is iOS not affected?
141.
by bdash 14y ago
The major difference is that Microsoft wasn't actively working with the various web standards groups to standardize its various proprietary features. The majority of the non-standard functionality that's added to WebKit and Gecko is done wi
142.
by bdash 14y ago
WebKit is constantly moving forward, and is not stagnant like IE6 was. Many of its initially-proprietary web features have been standardized and adopted by other browser engines. The primary challenge is convincing web authors to support th
143.
by bdash 14y ago
Another post[1] on the same website suggests that DMA is also disabled for Thunderbolt when the machine is locked. [1]: http://www.breaknenter.org/2012/02/adventures-with-daisy-in-...
144.
by bdash 14y ago
As the article notes, OS X is only vulnerable to this issue when the machine is unlocked as DMA access via FireWire is disabled while it is locked. If your machine is left unattended and unlocked then anyone with the ability to plug in a Fi
145.
by bdash 14y ago
It's the underlings you have to watch out for.
146.
by bdash 14y ago
Yup!
147.
by bdash 14y ago
Apple still owns and uses the entirety of 17.0.0.0/8.
148.
by bdash 14y ago
v38. You'd not see it with v48.
149.
by bdash 14y ago
The 7th is the first day of the second week of the year.
150.
by bdash 14y ago
The majority of the other scrolling performance issues discussed in the article are things that browsers can and will improve over time. For instance, the version of WebKit used by Safari uses a combination of tiled rendering and multithrea

More ›