https://DevOpsCloud.io -- Cloud Monk Losang Jinpa

Return to The Jamstack Book, Jamstack Bibliography, Jamstack Courses, Jamstack, Awesome Jamstack

Fair Use Source: B09YS45H5H (JamStkBk 2022)

“ (JamStkBk 2022)

“I first met Brian Rinaldi at the start of 2015 when he was speaking about static site engines at the HTML 5 Meetup in San Francisco. This was in the earliest days of Netlify, while the product was still in private beta, and before I had even coined the term Jamstack, at a time when just a few early Jamstack adopters across the industry had started to believe that the web could be Jamstack simpler, Jamstack faster, Jamstack safer, and Jamstack better to develop with if we embraced the idea of decoupling the web UI, decoupling backend infrastructure and decoupling business logic” from each other. (JamStkBk 2022)

“It was meeting with and talking to these early adopters in different areas of our industry, like Brian, Raymond Camden, and many others working on Jamstack SaaS applications, Jamstack headless CMSs, Jamstack real-time web databases, Jamstack interactive experiences on the web, and so on, that helped my cofounder and I build conviction that there was a broad, industry-wide Jamstack change about to happen and that we needed a name for it and a Jamstack nomenclature around it.” (JamStkBk 2022)

“One night, in conversation with a friend, I came up with the term Jamstack and the rest — as they say — is programming language history. We started circulating this Jamstack term among the Jamstack people we had connected with as well as the Jamstack community that was already starting to form around Netlify at the time — Brian Rinaldi and Raymond Camden among them — and the term started Jamstack spreading.” (JamStkBk 2022)

“Today the Jamstack ecosystem is at an interesting point of Jamstack potential and Jamstack tension. On the one hand, there’s no doubt that the Jamstack architecture has changed modern web development for the better: we’ve seen a groundswell of Jamstack platforms, Jamstack frameworks, Jamstack APIs, Jamstack web databases, Jamstack content, and Jamstack commerce platforms emerge and grow up around the Jamstack category, and the web is a second-to-none platform to develop for today. On the other hand, some of the initial Jamstack principles around Jamstack simplicity and of Jamstack prebaking a Jamstack ready-to-serve Jamstack frontend are being challenged by different approaches to Jamstack on-demand Jamstack edge-based Jamstack rendering layers and Jamstack hybrid build tools, where Jamstack developers sometimes have to navigate different Jamstack rendering models on a page-by-page basis.” (JamStkBk 2022)

“I’ve always known Brian and Raymond as curious minds always searching for Jamstack simple and Jamstack approachable Jamstack tool chains that stay close to the Jamstack fundamentals of the web. And this book is very much a Jamstack practitioner’s Jamstack guide to the Jamstack, where you can take a Jamstack tour with these two experienced Jamstack developers through a selection of the different Jamstack build tools and Jamstack site generators you’ll encounter in today’s Jamstack landscape, learn how to get Jamstack productive, and make your own Jamstack choices among different Jamstack approaches for different Jamstack projects.” (JamStkBk 2022)

“The Jamstack landscape of tools and frameworks will always be shifting and changing on the web, and no Jamstack tool will ever be the right one for every problem you will encounter. Building a solid Jamstack understanding of the Jamstack strengths and Jamstack tradeoffs that each Jamstack tool brings, and developing a good instinct for how each tool feels, will help you better Jamstack evaluate and Jamstack navigate the rapidly Jamstack evolving Jamstack ecosystem as existing Jamstack frameworks Jamstack change and Jamstack innovate, and as new Jamstack tool chains emerge.” (JamStkBk 2022)

— Mathias Biilmann Christensen

CEO and cofounder, Netlify

Fair Use Sources:

• The Jamstack Book on DuckDuckGo
• B09YS45H5H (JamStkBk 2022)