maclalala:link

John Gruber のポッドキャスト — WWDC 会場からライブ

Posted in アップル, イベント, ポッドキャスト by shiro on 2014年6月7日

Marco Arment と John Siracusa の WWDC 印象

Posted in ひと, アップル, ポッドキャスト by shiro on 2014年6月5日

ATP

68: Siracusa Waited Impatiently For This | Accidental Tech Podcast

Swift の感想がオモシロい・・・

OS X 10.9 Mavericks: The Ars Technica Review

Posted in ひと, アップル, レビュー, OS by shiro on 2013年11月17日

mavericks-feature

OS X 10.9 Mavericks: The Ars Technica Review | Ars Technica

読むのが大変!2万4千語にもおよぶ John Siracusa の徹底的 Mavericks レビュー・・・

Siracusa’s Review of OS X 10.9 Mavericks | Daring Fireball

A Dog Named Maverick – The Talk Show | Mule Radio Syndicate

John Siracusa’s Mavericks Review | Marco.org

37: A 3,000-Word Digression | Accidental Tech Podcast

Apple OS X Mavericks review | gdgt

読むに値するのは・・・:Marco Arment | maclalala2

Beauty, Truth, and Jony Ive

Posted in ひと, アップル, デザイン by shiro on 2013年5月9日

macbook-air

Beauty, Truth, and Jony Ive | Hypercritical

It’s interesting that Jobs and Ive saw eye to eye on hardware design and yet seemed far apart, at least in Jobs’s final years, when it comes to software design. While Jobs was reportedly a champion of rich Corinthian leather, Ive could only wince when asked about it in an interview.

I’m confident that we’ll see less leather, wood, felt, and animated reel-to-reel tapes in Apple’s future software products, but the question remains: what does it mean for an application or an OS to be true to itself?

Beauty, Truth, and Jony Ive | Daring Fireball

Accidental Tech Podcast

Posted in ひと, ポッドキャスト by shiro on 2013年3月16日

ATP

5: Negativity, Skepticism, and Doubt | Accidental Tech Podcast

Marco Arment と John Siracusa が本音で語るところがメチャおもしろい! John Gruber もベタ褒め・・・

Accidental Tech Podcast: Episode 5 | Daring Fireball

The Case for a True Mac Pro Successor

Posted in アップル by shiro on 2013年3月10日

lfa

Hypercritical: The Case for a True Mac Pro Successor | Marco.org

Mac Pro はいったいどうなる?

Until we get closure on this Mac Pro generation — discontinuation or an update — we won’t know why it’s been stagnating for so long. (Unless someone gets another email from Tim Cook.)

The Case for a True Mac Pro Successor | Hypercritical

The Mac Pro is Apple’s halo car. It’s a chance for Apple to make the fastest, most powerful computer it can, besting its own past efforts and the efforts of its competitors, year after year. This is Apple’s space program, its moonshot. It’s a venue for new technologies to be explored.

A Mac Pro Mini | Marco.org

It’s turning out to be even more brutal than I expected: Apple didn’t even bother with a Xeon E5 update. It looks like they’re accelerating the Mac Pro’s demise by neglect, not preparing for its recovery.

アップルは Copland の過ちを繰り返すか

Posted in アップル, イベント by shiro on 2011年6月13日

Copland 2010 revisited: Apple’s language and API future | Ars Technica
〈WWDC 2011 に対する John Siracusa の感想〉

Despite the lack of a 2010 crisis, Apple will eventually need to address this issue. The reason I was thinking about it five years ago is the same reason I’m even more concerned about it now: development platforms are hard to change. First there are the technical issues of selecting or developing a new language and creating a new API for it. Great APIs take years to develop and mature. Just look at Cocoa for a good example

The largest single collection of people who know and love Objective-C and Cocoa is at Apple, and these same people are perhaps not the most likely to aggressively push for a new language and API. Add to that Apple’s tendency—as evidenced by its App Store policies—to charge ahead with what it believes is the best course of action, despite outside opinions to the contrary, and you have some strong forces pushing Apple away from thinking seriously about this issue.

Apple can’t use another platform vendor’s API without ceding control of its destiny to an outside entity. Apple would also probably prefer not to hitch its star to a programming language predominantly driven, if not outright controlled, by a competitor. That leaves two options: either do it all in-house or find a “vendorless” solution not controlled by any single party.

The use of web technologies neatly solves many of Apple’s potential problems. Instead of having to come up with a world-beating language and API on its own, Apple’s got the entire industry working towards a solution on its behalf. The web is not controlled by any single competitor, and Apple arguably exerts as much influence on it as any other technology company.

Unfortunately, that means it’s not controlled by Apple, either. Furthermore, web technologies have a long, long way to go to catch up with the state of the art in traditional GUI application development environments. Most experienced Cocoa developers are very aware of this, and view any alternative based on web technologies with…some trepidation, let’s say.

Finally, I have to admit that I also just love a good mystery. Five years ago, I had no idea what Apple’s future language and API plans were, and today I still don’t. In a world where almost all of our longstanding fantasies have now actually come true—we’ve got our new OS, our Apple phone, our mythical tablet—the language/API successor question stubbornly remains. I’ve wisely chosen not to put a new deadline year in the title this time around, but rest assured, I’ll be watching and waiting. I just hope I’m not the only one.

モバイルマーケットで iPhone が Android フォンに負けないためには・・・

Posted in スマートフォン, iPhone by shiro on 2010年8月12日

iPhones-Assaulting-Deathstar.jpg

Ars Technica: “Can you buy me now? Apple and the war for the mobile market” by John Siracusa: 05? August 2010

The only way for Apple to eliminate the distribution and marketing advantage currently enjoyed by Android is to make sure that everywhere an Android phone is for sale, there’s an iPhone sitting right next to it that will work on the same network.