The company famous for secrecy is having a pretty hard time keeping things private these days. That now includes the company?s closed-door, developer-only training sessions from WWDC last month. Someone using the name WWDCVideos posted nearly 100 videos from Apple-led sessions to YouTube.
Now, Apple could have posted them, and then there would be no privacy or secrecy problem here at all. However,?as MacStories noted earlier, it seems unlikely the poster of the videos is Apple. First, Apple has its own YouTube account (it goes by ?Apple?) and second, WWDC is closed to the public. The only people who can attend are registered iOS and Mac developers and they must agree to non-disclosure agreements when registering.
It would be a bit odd for Apple to undermine its own NDA agreement, potentially giving developers license to publicly discuss or post in detail about any of the sessions they attended last month.
YouTube shows the videos were posted six days ago, and as of this posting, most individual videos show view counts in the double digits or low 100s.
Source: http://feedproxy.google.com/~r/OmMalik/~3/mkSarhsGcHM/
easter eggs pineapple upside down cake free ecards flying car masters golf tournament the replacements how to hard boil eggs
A Google engineer concluded on his Google+ page?last week that a cloud platform can’t be built without some form of lock-in. That’s evidently true but there really is one main reason for making such a point. Google wants to show that it is not much different from its competitors when it comes to this?hot topic with cloud customers. The post by Google Engineering Director Peter Magnusson has to be read with a dash of skepticism. Magnusson does focus on the lock-in issue with Google App Engine (GAE), but he also uses the topic to show the difference between its managed services and the infrastructure as a service (IaaS) from a provider like AWS. He says without restrictions Google could not offer the service that it does. What they do try to do is offer alternatives such as from services like AppScale. Reading into what Magnusson says, it appears that some customers are not accustomed to the restrictions that come with Google App Engine: The run-time environment is different and customers can’t make systems calls, write directly to the file system, or choose their own operating system. In the end, Magnusson says that lock-in is inevitable for Google to offer the service that it does with GAE: You can?t build an innovative platform without some measure of lock-in. For example, the Datastore is unlike any other NoSQL or NearSQL service or stack out there. It has multi-datacenter synchronous replication, cursors, distinct queries, projection queries, zigzag merge join, transactional tasks, automatic sharding/load balancing, managed secondary indexes, and multi-row and multi-machine transactions. Our developers don?t want us to dumb down those features to some lowest common denominator; they want us to build more features that leverage the unique underlying software systems. GAE comparess to other PaaS providers such as Cloudbees,?Heroku,?and AppFog, acquired in June by CenturyLink. ?Google abstracts the actual hands-on work of managing the infrastructure that is a hallmark of other services. That means there are certain aspects of Google’s app service that have to be restricted. These restrictions allow Google to take responsibility for a customer’s firewall, most?denial of service attacks, viruses — the list goes on. The upside, Magnusson argues, is that for most mobile and web apps, instances can be started quickly, allowing apps to scale fast. Google manages that scale and the problems that arise when, for example, an app has to be moved to another data center.
