The video is painful to watch, but impressive. I think my regular Griffin case would also protect an iPhone from such falls, but the difference is that the case itself would probably break in the process.
God damn you, PNG color correction! God damn you to hell!
But the change many OS X users will really welcome is the capability to show the date in the menu bar, using the new Show Date option. Unfortunately, you can’t customize that date’s format; you’re stuck with Aug 28.
Oh, for crying out loud, Apple…
(I’ve set up the excellent iStat Menus to replace the OS X clock, and the part of the date I check most often is the day of the week.)
Unfortunately, [text substitutions] don’t (yet) work in all apps; for example, they work in Pages, TextEdit, and iChat, but not in BBEdit or Word. Developers need to add the right hooks in their software to gain this feature.
Huh. That kinda sucks. Pro: in the apps where it works, it’s going to be (well, I assume it is) so much more efficient and reliable than TextExpander. Con: it’s awfully confusing for the user to have such a basic system feature available in some apps and not others. (But then, it’s mostly for geeks, and geeks will quickly get used to knowing where they can and can’t use it.)
Another minor change from Leopard’s International pane: the Input Menu tab is now called Input Sources. And within that tab, there’s a new option that lets you select a different input source for each document.
And I have no idea what that means.
I need to repost this here. "I wouldn't trust MobileMe to sync my boat." OMG I'm so witty I can't believe I breathe the same air as you.
Warming up to the thought that there might still be room for the idea of a Twitter client I'd had. But the API is a moving target right now.
Oh, good — I didn't know -webkit-border-radius now worked with <img>s.
Looks like I sold for roughly $120 of iPhone apps this month. (Won't bother calculating exactly, Apple makes it too hard.)
For the record: it is idiotic bordering on insane to suggest that Apple might release different tablets running different operating systems.
Flickr user 3e actually verified that Flickr really doesn’t check the names on these notices. 3e just submitted a claim to take down one of his own pictures with a "once-off email address, using the name ’Joe Blow’ and giving no identifying information other than an obviously fake address ("Anytown, USA")." Flickr happily obliged and 3e’s photo was gone within hours.
That’s just insane. And there are people paying for this service. Nobody should accept that.
And doubly insane is:
As of now, Flickr doesn’t even have the capability to restore an image after it has been deleted.
Which goes against the DMCA (well, I’m sure the idea of accepting any anonymous email as a valid DMCA takedown also does), as it states the content poster should be allowed to deny infringement, in which case Flickr would reinstate the image and be cleared of any legal responsibility.
It’s unclear whether rumors are true that Snow Leopard includes several internal features designed to prevent attacks that Vista and Windows 7 have, known as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) on that platform.
By randomizing the location of key pieces of data, ASLR makes it much more difficult for attackers to predict where data is going to be in order to execute their code or the code resident in the process. For exploit code that gets past the ASLR barrier, DEP will try to block it from running, recognizing that it is data and not a legitimate code.
I’m confused as to why anyone would focus on that kind of stuff when the real threat nowadays is trojans, and trojans are essentially just regular applications that rely on the user double-clicking them.
I mean, I’m sure it would be better for OS X to have ASLR and DEP and what have you, but it’s ultimately a moot point, not just because the Mac isn’t much of a target, but because viruses aren’t the bigger threat these days. Are they? (I’m not sure, I don’t follow security too closely.)
Not particularly impressed with the way Facebook 3.0 works. That "mosaic" button just isn't very tactile; users want to swipe!
I bought this because I live in a tiny room, my bed is half a dozen feet away from my desk, and yet I can’t spend my time lying on the bed and controlling my computers from there, because there’s no Remote Desktop client for the iPhone, VNC sucks on the Mac, and Bluetooth peripherals are too expensive.
I’m not going to spend a lot of time over the app itself, you can check out their description — the interface is pretty, and works mostly well (except for anything that uses the accelerometer, as always), but… it’s incompatible with OS X’s zoom-in feature.
Chances are you don’t even know that you can zoom into the screen on any Mac (I think it’s since Tiger?); many people don’t. But, if you activate the right settings in the Universal Access preference pane, you can zoom in at any time, by Ctrl-scrollwheeling with your mouse (or Ctrl-two-finger-swiping on a trackpad, or using a bunch of customizable keyboard shortcuts). That was great for zooming into text or images or videos before Safari had full-page zoom, and it’d still be awesome for controlling my iMac from ten feet away — being able to read what’s in my Adium chat window and all.
But, like I said, Mobile Air Mouse isn’t compatible with it: first, you have to change OS X’s setting for how the zoomed area follows the mouse, otherwise the pointer just goes out of the screen; second, even after you’ve done that, clicks don’t register where the pointer is — depending on which area of the screen is zoomed in, clicks will happen closer or farther from where the pointer appears to be.
I contacted technical support (who, to their credit, replied within 24 hours), and they told me they were aware of the problem and couldn’t find a way to fix it. What’s worse, Teleport (which is essentially the same thing, only from Mac to Mac) works perfectly fine with Universal Access zoom, so it makes me wonder how inelegantly Air Mouse Server might be programmed. (It doesn’t seem to be too stable, either.)
As it stands, this application is useless in pretty much all cases, unless you have a Mac mini hooked up to a big-ass 720p television (and not a 1080p, because then you’d be back to pixels being too small for you to control the Mac from your sofa). Or unless you’re using another media player than iTunes (on your PC or Mac), in which case you can’t use Apple’s iTunes Remote and need Air Mouse’s integrated iTunes shortcuts.
As for me: uninstalled. Guess I’ll still be waiting for Apple to release a Bluetooth keyboard with integrated trackpad. (And how much of a fucking no-brainer is that? If only Steve Jobs was — ever, like, once in his lifetime — a couch potato.)
For fuck's sake, just playing Whitney Houston's new album in a 200x50-pixel audio applet takes 100% of my CPU. Die! Flash! Die!
That's peculiar. Everything survived the power outage just fine, except... a USB hub.
Didn't wanna risk turning my computers back on too soon after power came back, couldn't resist more than ten min. Or two that felt like ten?
…and I’m not gonna be able to enjoy the upgrade anytime soon, so I’ll have to be content with looking at the reviews.
Does Snow Leopard feel faster than 10.5?
Apple continues to rely on the honor system for Mac OS X. Not only does Snow Leopard not require the entry of any serial numbers, but the standard version of Snow Leopard is a bootable “full install” disc that doesn’t actually check for the presence of Leopard in order to install.
When MacBreak Weekly discussed the upgrade procedure — just earlier today, but under NDA — I thought: “Come on, Apple hasn’t gone so evil yet that they’d check whether Leopard is installed on the drive, has it?” …but I wasn’t quite sure. I’m glad to see I was right.
Rosetta, the technology that enables code compiled for PowerPC chips to run on Intel chips, is available—but is not installed by default. Rosetta only takes up a few megabytes of drive space […] I can only assume that making Rosetta optional is an attempt by Apple to goad users to upgrade their apps and to shame developers who still haven’t recompiled their apps to run on Intel chips.
That is an odd choice. I guess, more than shaming developers, they really want to make it painfully clear that it isn’t Snowy’s fault that a certain application doesn’t feel any speedier than before.
By default, Snow Leopard still minimizes windows the same stupid way Mac OS X has for the last ten years. For us complainers, though, there’s a new alternative: A Minimize Windows Into Application Icon checkbox in System Preferences’ Dock pane.
Oh. Em. Gee.
But then, I’m not sure it’s quite usable, either: on Windows, when you minimize a window, you still see it appear in the taskbar, just as before (not sure how different it is in Vista/7 with some taskbar options). On Snow Leopard, though, if you turn this option on, minimizing a window will really make it all but disappear — and I can easily imagine having a bunch of forgotten Safari and Finder windows, all open on the same sites and folders. I never look at an application’s Windows menu, or its Dock icon’s menu.
Even better, this feature works with Exposé: When you invoke Exposé, all minimized windows line up together at the very bottom of the screen.
Okay, maybe it’s not so bad then. Although many people don’t use Exposé. (I don’t care, I do. And I love that it’s getting tidier, too.)
Several programs, including TextEdit, Mail, and iChat, can take advantage of a new systemwide Substitutions service that can autocorrect common mistakes (think teh to the), convert straight quotes to curly and vice versa, and turn double-minuses and triple-periods into em dashes and ellipses, respectively. Even better, a tab in the Keyboard pane of the System Preferences app lets you add shortcuts of your own.
I’m confused by this: A week ago, I read an article mentioning, like this review, that substitutions only worked on most of Apple’s applications. On the other hand, Andy Ihnatko’s review (linked further down) calls it systemwide — and it doesn’t make any sense for that functionality not to work in almost every third-party app, because the systemwide rich-text editor that’s provided “for free” to developers is one of the OS X SDK’s most touted qualities. So how could susbstitutions not work with all apps that use it?
I guess we’ll have to find out.
Apple’s QuickTime Player, long a stalwart tool for playing back audio and video, has been completely revamped for Snow Leopard. […] Every time I wanted to make my video louder or quieter, even via a keyboard shortcut, that floater appeared—and then remained for a second or two until finally fading away.
I’m quite glad to see I’m not the only one hating overlay controls. Emphasis mine on the particularly stupid behavior. And I also agree with the writer that having the player’s titlebar disappear when you’re not using it is completely ridiculous. But I guess there’s some strong-headed designer in the QuickTime Player team who won’t let go until he’s left his fingerprint on something ugly or impractical.
The changes also means that you can’t do quick’n’dirty edits [in QuickTime Player] by copy-and-pasting anymore (a favorite of Engadget editors)
Wow, I’m surprised not to see that mentioned more — video geeks will always tell you that being able to edit by using copy-and-paste in QuickTime is the basic skill any would-be editor needs to start practicing. And it is a really efficient way to do a quick-and-dirty edit when you need to.
But then I have nothing against the option of reinstalling QuickTime Player 7, I guess.
I don’t remember seeing Perian mentioned in any of the reviews, however. Can’t imagine that it’s 64-bit–ready, and I’m afraid updating the codecs might not be as simple as recompiling the bundle.
But if you click on a third-party preference pane that hasn’t yet been upgraded to a 64-bit version, System Preferences will tell you that it has to quit and reopen itself in 32-bit mode in order to open that preference pane.
Oh, gee, I’m sure it was so very important that System Preferences take full advantage of the speed of 64-bit computing. I mean, counting all those icons and stuff, that’s advanced computation.
(Okay, for all I know there may be a valid need for some of the preference panes to work in 64-bit. But, in that case, the correct workaround was definitely not to have System Preferences reopen every time you change panes. I’ve got 14 third-party panes in my iMac, some of which almost abandonware that I don’t expect to see updated for a while. How hard would it have been to have a second application bundle, called “System Preferences 32-bit,” launching separately when you wanted to activate a 32-bit pane?)
In Snow Leopard a mechanism was added to check for known malware signatures and display a user alert dialog. In these cases, rather than just advising the user that the file is an application, Snow Leopard provides a warning that the file contains known malware and suggests that the user move it to the Trash.
Uh-huh. The key words here being “
added” and “
just”: as in, judging from all the reviews, the new, secret anti-malware tool doesn’t dispense us of the goddamn warning when opening a file downloaded from within Safari. (I answered a tweet today about why use Safari rather than Firefox. I’d forgotten that this stupid dialog box — which only appears when a file has been downloaded from one of Apple’s apps — could just be reason enough for some to switch away from the system browser.)
The biggest compatibility-breaker is the demise of InputManager plugins in 64-bit apps. […] We also noticed problems with old standbys like Growl, GrabUp and Skitch […] There were some other head scratchers we saw on various systems, too. On a 17-inch unibody we were putting through the paces, the WiFi inexplicably has gone out and we have yet to get it working again. On a 15-inch, older generation MacBook Pro (3,1), Spotlight will only fetch search results in the dropdown – results in a Finder window come up empty. More annoyingly, on two other, newer models we were testing with, Safari crashes out when booting into 32-bit mode – meaning even Apple’s workaround doesn’t seem to… er, work.
Oh well, I suppose — well, I know — that every update has its horror stories. I’m always amazed that some people manage to concentrate so many of them. What the hell are they doing with their computers over there?
And, in conclusion: I want the new Finder! In fact, I simply demand that Apple release a Leopard version of the rewritten Finder for PowerPC users!
Also: god, this blog layout is unreadable when I intertwine quotes and reactions. Good thing I intended to redesign.
I can't decide whether it's okay for most Snow Leopard reviewers not to bother with typing the é in Exposé.
he literally put the passwords on a floppy disk in the form of paper glued to the magnetic film. for those that still have some floppy disks around, this is a zero cost hack. we wouldn’t recommend this for state secrets, but for those prolific forum registrations it’s a great idea.
I want to launch a web 2.0 service with a mascot just so I can tweet for it in the first person. Wouldn't fit @webispink so much.
The first augmented-reality app for the iPhone is French, made for Paris, and... I still don't have a 3GS.
I see how Regator could be interesting, but pushing me to choose between you and Google Reader? You can't win this.
Fake retweets by spammers are all the rage this week. Are retweets finally dying? Just let favorites show up in our timelines, @twitter!
Sony Computer Entertainment boss Kazuo “Kaz” Hirai has confirmed that the company will continue to lose money on each of the $299 PS3 Slim consoles they sell.
What a surprise.
Wow, I'd forgotten how thin my iPhone was without the protective case.
This idea (not new, I know) makes me so horny. Especially right now as I’m considering how much it would cost me (in several ways) to sell my iMac and buy a used MacBook.
Gift horse in the mouth, I know, but god the repeated install processes for DAZ Studio 3D are such a goddamn mess.
My source did not (and would have no reason to) lie to me. He was wrong. What happened is that his source for the information, who had direct knowledge of Apple’s decision, told him, more or less, simply that Apple did not reject the Google Voice app.
What interests me about this — if true — is that it would mean Apple may not have been splitting hairs when they told the FCC “we didn’t reject it, we’re still looking at it.” That, maybe, they sincerely think there’s nothing wrong with holding an app in the review process for months while they decide whether to publish it, it’s just part of the process.
Which is kind of scary.
SmillaEnlarger is an open-source and portable application designed to help you intensively massage an image enlargement to keep it from looking jagged and filled with artifacts.
Old, I know, but I had saved it for when I’d bother to try it out.
Much of the process consists in hiding the enlargement artefacts with a bunch of filters (rather than the pure algorithm magic Hollywood likes to invent), but the point is that, by just adjusting a couple parameters depending on each picture, you can get very easily a quite more usable result than Photoshop would give you using its best algorithm.
And, since it’s free, there’s no reason not to download it. (Except for the fact that… when do you ever need to enlarge an image anymore, anyway?)
iTunes Connect is like the lottery: every day you check your numbers, thinking "maybe this is the day that my app suddenly started selling."
Gruber did not respond to our emails, but so certain did the well-connected indy blogger sound [of AT&T ’s guilt] that we can’t help but wonder if he wasn’t snowed by Apple itself. The company would not necessarily have anticipated that a swift, aggressive and public FCC investigation into the Google Voice incident would have proven AT&T blameless. And it’s not like the company’s flacks haven’t been down this road before.
Perhaps the most encouraging sign is that Apple seems to actually be going back through rejected apps and contacting develops to resubmit their app (without any changes, mind you) for an "expedited review."
Huh. Maybe I was wrong to doubt Phil Schiller’s public commitment to improving the review process. (Well, no matter what, I wasn’t wrong to doubt it.)
For example, on an iPhone, the “Phone” icon that is always shown at the bottom of the Home Screen launches Apple’s mobile telephone application, providing access to Favorites, Recents, Contacts, a Keypad, and Visual Voicemail. The Google Voice application replaces Apple’s Visual Voicemail by routing calls through a separate Google Voice telephone number that stores any voicemail, preventing voicemail from being stored on the iPhone, i.e., disabling Apple’s Visual Voicemail. Similarly, SMS text messages are managed through the Google hub—replacing the iPhone’s text messaging feature.
That’s interesting. In other words, according to this official response (which could still be bullshit, mind you), what happened is that Steve Jobs (to be so anal, it would have to be him) decided the app was not acceptable because, if you started using it, your voicemail and text messages wouldn’t reach the iPhone’s Phone app anymore.
(I’m elaborating on this because it can easily be misinterpreted — if you follow the wording of the answer, the problem is not that it offers an alternate interface that replicates the system functionality of the iPhone. Even though that stupid “reason” has been used so many times for other apps, you’d expect Apple to stick to it.)
Interestingly, that’s exactly the kind of reasoning that the FCC might object to, and act upon: Apple just very officially declared that it wanted to stifle innovation and competition in the mobile space… and it’s so funny that they would have done it with AT&T not even knowing about it.
One still has to wonder whether — or how much — the recent evolution of the relationship between Google and Apple influenced that decision. But the sad thing is that, yes, you can absolutely imagine Jobs being outraged that an application would make users completely bypass his iPhone’s precious, original visual voicemail system and the SMS/MMS application he lovingly offered the world.
In addition, the iPhone user’s entire Contacts database is transferred to Google’s servers, and we have yet to obtain any assurances from Google that this data will only be used in appropriate ways.
If the app does this without asking you first, then it’s reason enough to reject it. (But if it does ask, it’s a moot excuse.)
Google is of course free to […] provide its “Google-branded” user experience on other phones, including Android-based phones, and let consumers make their choices.
Leave us the fuck alone and go play with their crappy handsets if you don’t like ours. Jobs oversaw the writing of this letter, didn’t he? (Well, of course he’d have to.)
From time to time, AT&T has expressed concerns regarding network efficiency and potential network congestion associated with certain applications, and Apple takes such concerns into consideration.
Apple does not know if there is a VoIP element in the way the Google Voice application routes calls and messages, and whether VoIP technology is used over the 3G network by the application.
If the app has been stuck in “requiring unexpected additional time for review” limbo for several months, shouldn’t Apple have an idea by now about whether Google Voice uses VoIP? (Especially when everybody knows it doesn’t?)
There are more than 40 full-time trained reviewers, and at least two different reviewers study each application so that the review process is applied uniformly.
Oh, that’s interesting. I wonder how long that policy has been in place. It does explain why I saw someone log into Web is Pink from Apple HQ a couple of days after I submitted the app, yet it took one more week, and another login, before they approved it.
(Now that you mention it, that could have seemed obvious at the time. But you know how it is about hindsight. And I did figure that it must have been two different reviewers; I just never thought they would have instituted that as a policy.)
Apple also established an App Store executive review board that determines procedures and sets policy for the review process, as well as reviews applications that are escalated to the board because they raise new or complex issues. The review board meets weekly and is comprised of senior management with responsibilities for the App Store.
That’s also very interesting: so maybe the dreaded “Your application is requiring unexpected additional time for review” isn’t complete bullshit after all — it’s just that your application has been flagged for the executive review board, and like any board of executives they’re not in a great hurry to deal with each and every case, because they’re already busy enough with other duties. And, when they have prominent applications from Google to debate week after week, you can’t expect your own app to be processed right away… or within your lifetime.
Oh, shit, I looked at the ImageMagick source for help with Snap Filters, but didn't think of the Gimp.
Jesus-Christ, you have to hack XCode in the Terminal in order to test your apps on an iPhone running 3.0.1.
We’re gearing up to launch a new feature which makes Twitter truly location-aware. A new API will allow developers to add latitude and longitude to any tweet.
I don’t think I personally want my tweets to be geolocated on a general basis, but I think this is a great idea, and great for Twitter. Oh, but wait:
It will be off by default and the exact location data won’t be stored for an extended period of time. However, if people do opt-in to sharing location on a tweet-by-tweet basis, compelling context will be added to each burst of information.
The emphasis on tweet-by-tweet granularity is absolutely awesome; I’m impressed. (Also, I like every step towards adding more metadata to tweets, making room for real content within the 140-character limit.)
And, today more than ever, it boggles the mind that Facebook still hasn’t shown any interest whatsoever in geolocation.
If New!Palm is really clever (which is possible), they might have astroturfed the internet freakout themselves.
Finally watched a couple of Palm Pre ads on YouTube and... what the fuck is everybody freaking out over?
[Adium] 1.3.6 also features an updated version of the Facebook chat plugin, fixing a number of issues, which were present in Adium 1.3.5 including unwanted email notifications, dropped messages and missing contact icons.
Emphasis mine. People seemed to think me crazy when I told them I’d quit using Adium to access Facebook chat because it still lost messages sometimes.
Do we need that many blogs to post screenshots of Facebook 3.0 for iPhone? We're all gonna get it on our phones in a week anyway.
I’m not sure what to think. I’ve always assumed that the development had to be somewhat advanced if they were suddenly announcing it — unlike many people who accused it of being vaporware — but the bits around the browser window scare me: they look ugly and temporary (a minimal, vestigial system tray? why the hell would you want that?) but the worst part is that Google is perfectly capable of releasing an OS that looks like this.
What I find really interesting, though (and unless you’ve always thought it would work that way, which I hadn’t, I’d say the cleverness makes it unlikely that it would be a fake) is the way tabs are roaming free on the desktop. Meaning, essentially, that there is no such thing as “tabs” anymore: each page is in its own window (and process, as we all know), and it just so happens that windows can be docked together. That looks like a great interface for geeks and regular users alike. (I had stupidly imagined that all pages would display in a full-screen window with tabs on top — but that’s unworkable on today’s web, as there still are legit uses for popups.)
You’ve got to wonder: had they planned this from the start? Is that why Chrome looks so different from every other browser, with its tabs on top and embedded blue background? Did they always intend for Chrome to be perceived as a little slice of Chrome OS on your desktop?
I’m not sure that Google itself did, but I’d bet the Chrome devs had it in mind.
iPhone blogs that still haven't figured out a way to make stable video of the iPhone lying flat on a table… (when it doesn't need tilt, duh)
Wouldn't you say it's time merriam-webster.com got a little cleaned up?
(Did I ever tell you how much it annoys me that '@' has become part of Twitter usernames when it's just supposed to mean talking to s/o?)
Would you kindly do me a favor and follow @unicodeapp so it doesn't look so much like a spammer on the follow notices?
Wow, the Twitter captchas are tough today.
A bit of Twitter follow-spam. Let's see if that works. (Damn, I knew I should have created a Twitter account for Unicode.)
That interface is actually very nice. I’m quite impressed by the way they play with typography — reminiscent of Flash animations of a few years ago, but in a good way. Classy, and quirky. Yes, it is intentional that the’ e’ on” marketplace” is cut off, and I like that kind of ambition from a designer.
But… it’s still just a media player. The iPod touch is a PDA.
Ten good dos and don’ts of password security, with a nice (inevitable) conclusion:
I regularly break seven of those rules.
I only break six; wonder how he does worse than me. (I was very conflicted about typing my ISP password while on my parents’ computers last week — actually, I wouldn’t have if VNC had worked.)
I so don't want Twitter to endorse retweets. There are faves already goddamnit.
Having a conversation in that tiny Facebook chat thing is horribly claustrophobic.
It's funny that Google Voice is exactly the way I wish modern IM systems worked.
Um, I assumed I'd be able to go to my FriendFeed follower list one day and follow them back if I wanted to?
Je loue des serveurs chez un hébergeur qui génère des factures PDF en 100% Comic Sans.
I need to get into follow-spamming. Qwitter doesn't seem to work anymore anyway, so there's no consequences.
You'd think AdWords would let you say "spend that much money on this campaign" and be done with it. But that would be too much control.
I was just gonna test-drive a Front Row clone, and here I am rewatching Firefly.
After going back to Ninjawords’s developers and conferring with some trusted sources within Apple, I believe what Schiller says here is genuinely the case — that what the App Store reviewers wanted for Ninjawords was a 17+ rating, not for Matchstick Software to filter its dictionary listings.
Well, then maybe you could have employed the same basic researching and critical thinking just a bit earlier, like right before you wrote in your previous article:
“Someone from Apple called Dave to tell him that we were being rejected again for illicit content [..] and no matter what we did to our dictionary, it will have to be 17+ to make it to the App Store.”
In other words, not only must the dictionary be censored — a dictionary — but even after being purged of “objectionable” words it would only be considered with a 17+ rating.
…even though the rejection e-mail, which was quoted in its entirety, helpfully provided the following (I wasn’t so lucky with my gay chat app):
Parental Controls have been announced for iPhone OS 3.0. It would be appropriate to resubmit your application for review once this feature is available.
It doesn’t seem like it would be too hard, for a cold-blooded high-profile blogger who’s supposed to be super clever and analytical, to figure out that nothing in what was quoted here implied that Apple wanted to apply both censorship and parental controls (whereas you can understand how the developers took the rejections quite personally, and overreacted a bit).
One would think such a blogger, and one who regularly touts their high-placed sources within Apple, would try and check their facts before posting such an incriminating story. But, hey, when you’ve got the scoop on such effective buzz to relay — uh, I mean, on such an important, shocking story — you’re not going to sweat it, are you? Let’s just write it up as it comes!
This is music to my ears. That Schiller was willing to respond in such detail and length, on the record, is the first proof I’ve seen that Apple’s leadership is trying to make the course correction that many of us see as necessary for the long-term success of the platform.
As a matter of fact, what’s music to your ears is that Phil Schiller wrote you personally. As for us lowly iPhone users and developers, we’d rather wait until there are tangible facts we can judge, thank you.
Am I the only one thinking that the article should end with “I asked Phil Schiller in reply to explain what was up with Google Voice, but he declined to answer” or something like that? Isn’t that the least you ought to do, under the circumstances?
Is it just inevitable that any prominent, opinionated tech blogger will turn into Michael Arrington?
I hate how iPhone devs have to beg. To think it might be different if I hadn't fallen off the face of the blogosphere a couple times.
Unicode 1.0.1 is live: spammed French blogs, spammed English blogs again for good measure, and cleaned up my inbox. Phew.
Damn, having to develop without JQuery on the iPhone is such a pain.