4 ms·
Glad to see discoveryd is toast. That's a big win and hopefully it's a symptom that some manager on the OS X team is starting to notice how sloppy development h
by STRML 11y ago
Glad to see discoveryd is toast. That's a big win and hopefully it's a symptom that some manager on the OS X team is starting to notice how sloppy development has gotten in the last few years.
On a related note, how insane is it that a minor patch like preventing JS `alert()`s from clobbering the browser has to be rolled into a full OS update? When will Safari auto-update like a regular app?
- profmonocle 11y agoThe odd thing is that Safari usually does update separately from OS X. (Unlike Safari on iOS.)
- jblok 11y agoIt sounded like a pretty major bug to me. Essentially a website could hijack the entire browser before now, presumably forcing the user to restart the app. For quite some time, Chrome and Firefox have had that little checkbox on alerts, stopping the site sending any more.
- mikeash 11y agoMajor bug and minor patch can go together. Often a problem has big consequences but a small fix, and that's likely the case here.
- Eric_WVGG 11y agoThat is the parent poster’s point. If Safari were patched independently of the operating system, issues like this could be addressed independently of monolithic system updates.
- AdieuToLogic 11y agoSafari _is_ updated independently in OS-X. Maybe this update coincided close enough to the roll out of the OS update that it was included in this release.
- Eric_WVGG 11y agoSecurity patches don't count.
- mikestew 11y agoFor quite some time, Chrome and Firefox have had that little checkbox on alerts, stopping the site sending any more. For quite some time, Safari has had this option (though I don't know for how long). Too bad it doesn't work.