Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
An American would have said "Apple IS done". Phrasing "Apple ARE done" is more likely UK.
That is one of many a fine point in English grammar across the pond. In the states, proper named groups are treated as a singular while in the UK it is treated as a plural. When I was in high school in the States, we had an exchange student from Liverpool. Our English class was eventful with his attendance.
[doublepost=1461106681][/doublepost]
Not at all. Blizzard said this in one of their forum posts about 4 months ago. It's common knowledge in the Blizzard community.
I haven't followed the Blizzard community since they phased out the original Merlin server network. Guess it is more transparent of a company now. Back then, they were paranoid crazy about any internal operations.
 
Last edited:
Worse thing about software announcements is that most of us have to wait months before we even get a taste of them, understandably though.

I wonder if we'll see the rumoured ultra thin MacBook Pros announced. Can't see that they've got much more than that to release, aside from iOS 10 and MacOS whatever.
Well, there are public betas these days.
 
Either the voice of authority or a delusional option. I wish this could be verified.

I'd say it really depends on the nature of the application itself.

Per my "raised hand" comment if anyone was using it, I started an app cold, in Swift, and it's been terrific. It's a very standard app:

Tab interface
All standard UIKit components
Data from a backend API (Nodejs)
Map Kit
Push notifications

I'd say as soon as you get into a custom UI, hardcore graphics, etc., things may go off the rails. I'd imagine there is a huge amount of codebase, originally written in Obj-C, probably with all sorts of crazy subclassing, it's probably a huge PITA to migrate or combine to/with Swift. Plus there's a ton of 3rd party libraries and coding support, still in Obj-C.

Short version: simple, BTB, standard template UI patterns, Swift is totally groovy. That's my perspective from someone who's been in the industry ~25 years, developer, architect, author, work[ed] in most languages/frameworks, enterprise, mobile, etc.
 
Short version: simple, BTB, standard template UI patterns, Swift is totally groovy. That's my perspective from someone who's been in the industry ~25 years, developer, architect, author, work[ed] in most languages/frameworks, enterprise, mobile, etc.

I'm seeing the same perspective. If you are doing a straight forward, standard views interface, Swift is fine.

However, if you are in some of the exotic app categories such as customer graphics, non-standard view transitions, accessory connectivity or non-standard IO, Swift may fall short.

For me, if Google, Microsoft and others follows through with their intent to have Swift a supported language, then it becomes more than a one-shop language with the compiler given a very through extra party review.

The same thing happened to the Unix / C community when it was licensed out of Bell Labs post-breakup. You saw C supported on dozens of instruction sets. The compiler was much improved and made the need for Assembly a specialty -- specifically when the cross compilers started up.
 
Well, there are public betas these days.

Yeah, I guess you're right. I've participated in public betas in the past if the update has features I want sooner rather than later, but betas tend to cause more headaches than anything else.
 
I'm seeing the same perspective. If you are doing a straight forward, standard views interface, Swift is fine.

However, if you are in some of the exotic app categories such as customer graphics, non-standard view transitions, accessory connectivity or non-standard IO, Swift may fall short.

That has not been my experience at all and I don't see how custom transitions would be limited in Swift. The whole of the SDK is available to Swift and legacy code can be made available through the bridging header. The interoperability between Swift and Objective-C is quite robust. Most of the annoyances come when you want to call Swift code from Objective-C, in which case you are better off refactoring to a pure Swift implementation.
 
  • Like
Reactions: galrito
I had been attending WWDC about every other year since 2007 and have seen it shrink from a "dense packed" five day conference down now to basically three days. Fridays have shrunk over the years, and now they've removed deep technical content from Monday, which is now just the keynote + dog and pony shows. Not really worth it anymore.
[doublepost=1461221369][/doublepost]"Apple will also be providing 125 scholarships to aspiring developers with financial limitations, a program that is new this year"

Wrong. Apple is providing travel assistance for up to 125 SCHOLARSHIP recipients with limited financial means. All you bankrupt developers who've only sold 5 copies of your app are not eligible :)
 
Last edited:
So Apple are giving 350 scholarships the same amount as last year, with them using the Bill Graham Civic Auditorium i would of thought they were going to offer more seats to people, after all that building is far bigger than the usual place that Apple does the WWDC keynote.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.