May 14th, 2010 by Arjan Olsder Posted in Platforms: Adobe Flash & Air, Platforms: iOS | No Comments »
Adobe has started a new media offensive in which it explains it’s love/hate relationship with Apple. In a marketing campaign, the company details their opinion.
Next to launching the marketing campaign, the founders of Adobe (Chuck Geschke and John Warnock) also sent an open letter to the industry showing their thoughts on an open market.
We believe that consumers should be able to freely access their favorite content and applications, regardless of what computer they have, what browser they like, or what device suits their needs. No company – no matter how big or how creative – should dictate what you can create, how you create it, or what you can experience on the web.
When markets are open, anyone with a great idea has a chance to drive innovation and find new customers. Adobe’s business philosophy is based on a premise that, in an open market, the best products will win in the end – and the best way to compete is to create the best technology and innovate faster than your competitors.
We believe that Apple, by taking the opposite approach, has taken a step that could undermine this next chapter of the web – the chapter in which mobile devices outnumber computers, any individual can be a publisher, and content is accessed anywhere and at any time.
In the end, we believe the question is really this: Who controls the World Wide Web? And we believe the answer is: nobody – and everybody, but certainly not a single company.
Congratulations
Your first AWS Elastic Beanstalk Node.js application is now running on your own dedicated environment in the AWS Cloud
This environment is launched with Elastic Beanstalk Node.js Platform
What’s Next?
- AWS Elastic Beanstalk overview
- AWS Elastic Beanstalk concepts
- Deploy an Express Application to AWS Elastic Beanstalk
- Deploy an Express Application with Amazon ElastiCache to AWS Elastic Beanstalk
- Deploy a Geddy Application with Amazon ElastiCache to AWS Elastic Beanstalk
- Customizing and Configuring a Node.js Container
- Working with Logs