taharvey

I've spent the last week trying to get good file transfer between two applictions, just for static 3D scenes - and I don't know if there isn existing file format. Heck, I can't even get two applications from Autodesk to wholly share a full 3D scene.

If you know of a 3D file format that understand all types of geometry: Nurbs, solids, polygons AND physics based material shaders, AND understands whole scenes: lighting, cameras, and animation. Well I'd like to know of another one.

Also this format adds futher concepts from a pipeline, things that are interesting to AR like late stage lighting, effects, composition, and overrides

Your assumptions underscore your bias. Perhaps they have bigger dreams then the rest of industry.

Apple stands out from the rest of those industry players by historically having much longer range architectural vision. They have also been investing heavily in their devices for many years to support that vision. The processing power of the typical iPhone outruns average competitor by multiples.

Technically under the covers HFS isn't anything great. But from a users point of view apple has extended it in ways that it hasn't materss to customers.

ummmm... metal cames out 2 years before vulkan. Vulkan was inspired by metal.

Why does Google get kudos for inventing new languages (Go), and Apple gets mocked? (Swift)

You mean an API than you can actually read and understand? How dare them take your 1970s 80-char display away from you!

What about the special snowflake projects of google, mozilla, or sun? Apples language development is no less valid than google developing Go, or mozilla developing rust. This just shows your inherent bias.

I've been amazed recently how many open-source projects that we rolled into our linux product were Apple sourced: LLVM, Clang, libdispatch, webkit, OpenCL, zeroConf. Can't think of anything google has done for me recently.

And if there is anyone who will knock-this out of the park, its Chris Lattner. LLVM, Clang, and openCL is all him. He has done more for compiler tech than anyone in 30 years.

reference counting != garbage collection. Garbage collection take CPU and lots of memory. Reference counting just ++ the pointer count on allocation, and -- on free. Essentially no overhead.

No I'd say Apples approach was: methodically develop until very polished first, then announce after. You just didn't get to see the 0.1, 0.2, 0.3... versions.

This is actually nice, because knowing about languages years before they are production ready probably just slows developer adoption because nobody is quite sure when they should trust there development process to a new language.