lurch_mojoff

Come on. Big Brother? Really?

And do you honestly believe that it is a bad thing that ordinary, unsavvy with computers users will not immediately be able to install applications from unverified sources?

Yes, I have. And I can confidently say that Mac OS X, even today after a decade of evolution and sweeping changes, is clearly a direct descendant of NeXTStep and has little in common with System 7. I'll also reiterate what others said -- there is everything wrong with Gates' statement.

I disagree that Apple's goal was lock-in. If it was, they'd probably make the interactive textbooks iOS applications, similar to what PushPopPress did, instead of this bastardized version of epub.

Quotes from the linked post like this: "The ability to control the size of each column and column gap was recently discussed in the CSS WG. The Group decided that allowing setting of individual column width and column gap width is not a feature considered for the first REC of this document.", suggest, to me at least, that Apple created their proprietary format because standards didn't and still don't cover the fictionality they have in mind for these interactive books. I'd rather Apple do that than hastily muscle their implementation into the standards.

Which is compltely idiotic business model for Netflix. They can sell their original content directly to me. Unlike traditional TV content producers, they don't have to rely on (and split profits with) third party distributors.

I suspect you are right, but I sure as hell hope you are not.

Lack of empathy is the definition of psychopathy. A psychopath will look at someone ran over on the street and think "too bad it ruined that nice jacket" or something similarly disjointed form the fact that a human being is dead. Stallman's comment is similarly unempathetic.

And tablets… and portable music players… and small and light laptops… and…

The sentence you quote does look outright ridiculous when said about Apple.

Three years? Make that five.

And every additional year makes your point even more relevant — I can understand, even if it is just subconsciously, that one cannot fit all the things I expect in a 6 or 12 month release cycle. I cannot accept the same for a 60 month cycle, even though I do know that that’s not how software development works (cf. mythical man month, etc.)

"Let's be clear: Apple changed its delivery pattern for iPhone. It's a delay, and a big one.” Followed by absolutely no evidence supporting the statement.

Yep, this is not link-bait, no siree.

The question is how many people will buy a PlayBook now on the off chance they’ll get a rebate at some future point. Not that many I reckon.

It is way too early to proclaim that history is repeating itself. 20 years ago Apple were a rudderless ship. Today they are on of the most efficiently operating computer companies out there. They have a vision, they have a solid foundation on which to build, and they have the resources to execute rapidly on that vision.

The important thing is not whether Apple should or shouldn't have won, but that they did. A court of law, as biased as it may be, has concluded that Apple’s complaint has merit. And now that may serve as precedent for Apple to use in other jurisdictions. Samsung are getting deeper into the crapper.

I still don't understand how a bunch of stored-to-file object graphs "dirty the code base" but I guess you are right -- it is a preference thing. Believe me, I have weirder quirks than that when it comes to coding.

Your example, however, is probably amongst the worst to support the argument you are making. Here are the steps to create a tab bar view with four tabs, each containing a navigation view, and those containing alternating table views and plain views:

- drag out a UITabBarController

- remove the two default UIViewControllers instantiated with it

- drag out to the tab bar four UINavigationControllers

- select each tab and drag out to the center area of the view a UITableViewController or UIViewController

- customize to your heart's content

- there is no step six…

In my guestimate this will take at least 20 lines of boilerplate code, even with the minimal amount of customization. And you’d be missing out on all the rest of the benefits of NIBs, like the ability to see (and to some degree test) your UI without having to build and run your application or the ability to send it off for localization to a collaborator.

Would you care to qualify that. In my experience it has been the exact opposite -- setting up your UI in Interface Builder has always reduced the amount of code necessary and has allowed quite complex view hierarchies to appear pretty much flat in code. And I'm taking about iOS UIs, for which a bunch of the code saving goodies of AppKit Interface Builder are not available -- things like Cocoa bindings and the new auto layout machinery in Lion.

Sure, it is. But Push Pop got a ton of publicity partly because of Al Gore and partly because of Mike's passionate Ted talk, so I presume they would have been able to get more than enough funding. And of course you can't change the world if someone does it before you.

Anyway, the folks at Push Pop Press, as well as Sofa and the rest of top tier design talent that Facebook have been eating up, are smart bunch and I'm sure they know what and why are they doing. Or it could be the allure of a metric buttload of money.

I'm definitely in the K&R camp. I keep alternating between 1TBS and Compact Control Readability, depending on the preferences of the other members of the team working on that particular project. I personally prefer Compact Control Readability.

How much do musicians get paid for Spotify streaming? Well, this much: http://www.informationisbeautiful.net/2010/how-much-do-music...

"Offline streaming", right. You can synch only music you have bought from Spotify. It does not work with the "all you can eat" subscription. So it is very much not an obsolete complaint.

Yeah, I should stop hanging around iOS developers - I'm loosing sense of what is under NDA and what's not. :)

It is actually much more than probable that Apple will require Mac App Store apps to be sandboxed, it is certain — Apple have notified developers that come Fall (I can't remember the exact month; October? November?) that requirement comes into action.

And even if that was not the case sandboxing would still be understated — the system provided segregation of common attack vectors, e.g. WebKit2's separate HTML parsing processes, Quicktime's separate video decoding processes, the segregated PDF parser, etc., is one of the bigger security enhancements of any OS.

Apple have never shown any interest in being friends with the carriers. Since day one of their foray into the mobile phone business, they've been barely tolerating their partner carriers - like a horrible roommate, you cannot kick out because you need their share of the rent. It's just now Apple feel strong and established enough to completely shun them.

In computers Apple are not competing on price. In fact they maintain atypically high prices there. In tablets they are.

Because Apple don't allow the use of private APIs and the modification of the function of physical buttons. Both for a good reason - if they allow those they lose control over user experience and set up things to break horribly down the road.

I don't know, "near monopoly" doesn't mean anything - 70% or 7%, you either have a leverage over the market and are a monopoly or you don't and aren't.

I think it's rather that Apple figured that those two (and others) going out of business (or at least ditching iOS) will hurt their platform more than anything they'll gain from the subscription rule change.

> Have you ever tried to compile Xcode samples on a MacMini?

Yes, I have been doing it on a four year old, Core Duo one for the whole three years since the iOS SDK became available and have had zero compilation performance issues. Keep in mind that the vast majority of iOS applications are laughably small compared to desktop apps.

I'm not disputing that a Mini is still too costly for many, but I think it is unfair to exclude it as development machine.

One difference is that the command-line and DOS applications didn't require more CPU and memory resources. Another difference is that the mouse didn't remove the main input device for the command line - the keyboard. Yet another difference is that extending the command-line into GUI didn't coincide with a switch to an entirely different system architecture.

The argument is not that personal computer OSes and mobile device OSes won't be converging down the road. Actually that's the big thing with Lion, isn't it. And I'm sure it will be a similar thing with iOS 5. The argument, though, is that they will never meld completely because it is impossible (or at the very least very, very unlikely) to have both full backwards compatibility and full and proper casual computer, or tablet if you will, experience.

Or simpler still - the iTunes application will generate fingerprint of the whole audio in each file and send it along with whatever metadata is available. Then serverside the fingerprint and metadata are analyzed and if a certain criteria for a match are not met, iTunes is prompted to upload the file.

No they don't. If you don't renew your ADC membership Apple won't pull your apps from the store.

Does it really matter who's done "it"? The whole "hunt for Osama" was not about punishment or rehabilitation of the guilty. It was a symbolic act. In the eyes of the world the ones who did it are the ones who took responsibility for doing it — al-Quaeda. Shooting the face of al-Qaueda in the face sends the unambiguous message — "If you try to terrorize us and kill innocent people, we'll not rest until we find you and kill you."

I think jschuur's suggestion is that they should have made a video targeted at the general public. The use case of many of these mobile services and apps is not inherently obvious, not the the general public anyway. Compare the information you get from Color's website to the information you get from the lonelysandwich video promo for a similar app - Everyday, on its website: http://everyday-app.com/

The thing is those "other specialized frameworks" are mostly the exact same ones you get on the Mac. So the accurate description would be: "Apple ported the major parts of Mac OS X to ARM and exchanged UIKit for AppKit".