zw

6 ms·

1.
by zw 7y ago
This is a mind-boggling level of FUD. Content blockers have been noticeably superior on both macOS and iOS for years. They’re not “limited”, they’re rational. It’s abjectly absurd that traditional ad blockers can consume as much CPU as they
2.
by zw 10y ago
And then maintained it and fostered its growth while it became the foundation of modern computing…?
3.
by zw 11y ago
I think it's gotta come from the other direction, ultimately. They're working hard to push AppKit forward and bring it into the future, but I think UIKit will figure out the hard problems (menuing, keyboard navigation, pointer inp
4.
by zw 11y ago
"Native" being a really relative word here.
5.
by zw 11y ago
[Really easy to enable.]( http://internals.exposed/blog/dtrace-vs-sip.html ) But, hey, sure. Don't let that stop you from getting angry. Merry Christmas. There should be a bingo card for this thread. "#doomed&q
6.
by zw 11y ago
It seems like they do that on OS X as well.
7.
by zw 11y ago
Based on the warnings in the Console log back when I used Dropbox, Dropbox isn't using fsevents API appropriately but is instead reading from the raw fsevents firehose.
8.
by zw 11y ago
I have nothing to say about your other issues (I haven't experienced most of them; I'm quite happy with the service), but the banner at the top of the More (…) menu takes you to the album of a song, which then easily leads to the
9.
by zw 11y ago
Forget the "-ish". Actually, forget the "native". Their app is no more or less native than Rdio's was.
10.
by zw 11y ago
Not anymore; those methods are implemented in an extension on `String` that don't always involve bridging back.
11.
by zw 11y ago
Because you're making mistakes in those other languages? Because the world is not just English anymore, and "going through an i18n library" is all well and good until you need to accept literally any form of user input, which
12.
by zw 11y ago
But the definition of "character" is not generalized, therefore the use case cannot be generalized.
13.
by zw 11y ago
> obsesses a lot about not breaking backwards compatibility Lo, how times have changed. ;-)
14.
by zw 11y ago
iTunes on Windows is as much AppKit as it is on OS X; which might be to say, not much, maybe… but definitely a lot of ObjC and Foundation.
15.
by zw 11y ago
`WKWebView` has issues that made it untenable for use as a web browser last year, but there's nothing I'm aware of preventing its use for common in-app browsers.
16.
by zw 11y ago
The Swift standard library is not yet up to snuff for that, you still need to know Cocoa to do basically anything high-level. Thankfully I know Foundation better than I do straight-up POSIX, so that's tenable for me, but it's not
17.
by zw 11y ago
Trials and upgrades are niceties for the developer, not the user. The App Store isn't made for developers, it's made for users. If developers want access to those users, they should build businesses not oriented around extorting m
18.
by zw 11y ago
His Snow Leopard review was also in part a classic because the release was a classic. Nothing was left unturned in that OS, it was a goldmine for a guy like him. I hope a feature release will be of a similar caliber (i.e., "make ALL th
19.
by zw 11y ago
For something that foundational, you have to move as one giant, lumbering beast. Recall that Apple had at least one (that we know of) false start. A fair bit of the OS (CoreServices; Carbon, and the apps that still rely on it) still relies
20.
by zw 12y ago
If I remember correctly from an article many years ago, they want the C++ API to be high-level and fast-moving; the C API exists so that they can support low-level use and almost all clients while only maintaining one API well.
21.
by zw 12y ago
It's [Windows Installer]( http://en.wikipedia.org/wiki/List_of_Microsoft_codenames ).
22.
by zw 12y ago
As someone who has used it extensively, Auto Layout is not a cause for performance UI regressions. Not by a long shot.
23.
by zw 12y ago
The Finder and all its functionality was ported to Cocoa in 10.6. All related functionality has eventually made its way into Cocoa: NSWorkspace, NSURL, NSFileManager, and NSFileCoordinator. The Carbon file management APIs are long, and than
24.
by zw 12y ago
No, iOS has had tools for building apps with flexible canvases, that has very little to do with the resolution of the screen these days.
25.
by zw 12y ago
2009! They thought they could get it done in time for Snow Leopard GM!
26.
by zw 12y ago
Thrilled to see FastMail tastefully and respectfully grow their ecosystem. I can see that, at least for the iOS app, it's pretty much a web view wrapper; I'm willing to give it a pass for the most part because FastMail's weba
27.
by zw 12y ago
Yeah, they sell off-contract Verizon phones at the fruit store. They're unlocked GSM global phones, pretty sweet. I got one because they were all my store had and immediately popped in my T-Mo SIM.
28.
by zw 12y ago
> ... Facebook iOS apps make liberal use of web views (and code push) The Facebook apps absolutely do not use web code anymore. Their native code is conditionally enabled remotely.
29.
by zw 12y ago
As an example (I'm not the guy who you responded to), I've been frustrated in Castro a number of times while looking at an episode in show's feed because the native swipe-back gesture takes you back to the list of shows rathe
30.
by zw 12y ago
The "function trampoline" that's described looks more or less like the Block ABI. Some good learning is available in the source for `libclosure`, [Language Specification for Blocks]( http://www.opensource.apple.com&

More ›