Chapter 7. Conclusion
And One More Thing...
When we talk about the JAMstack, it’s easy to drill into the advantages that it has for us as developers and the projects we build. But there’s something larger at stake that the JAMstack addresses, and we’d be remiss not to discuss it here.
The JAMstack is a response to some of the most urgent threats to the web. But first, a quick history lesson.
When the iPhone was brand new and Steve Jobs was busy killing off Flash, HTML5 applications were meant to be the main delivery mechanism for all third-party applications on the Apple ecosystem. Jobs wrote in his famous open letter to Adobe:
Adobe’s Flash products are 100% proprietary. They are only available from Adobe, and Adobe has sole authority as to their future enhancement, pricing, etc. While Adobe’s Flash products are widely available, this does not mean they are open, since they are controlled entirely by Adobe and available only from Adobe. By almost any definition, Flash is a closed system.
Apple has many proprietary products too. Though the operating system for the iPhone, iPod and iPad is proprietary, we strongly believe that all standards pertaining to the web should be open. Rather than use Flash, Apple has adopted HTML5, CSS and JavaScript – all open standards. Apple’s mobile devices all ship with high performance, low power implementations of these open standards. HTML5, the new web standard that has been adopted by Apple, Google and many others, lets web developers create ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access