| • Accelerated Mobile Pages (AMP) explained by Alex Sexton
|
| • AMP is a Google initiative to provide fast mobile browsing experiences for news articles and other content
|
| • AMP works by caching content on Google's servers, serving it edge-cached, and pre-loading articles based on agreed-upon rules
|
| • Rules include limiting external CSS, inlining 50 kilobytes of CSS, and using custom elements for images
|
| • Benefits include faster loading times, but also concerns about centralization of control and data by Google
|
| • Negative aspects include non-intuitive URLs and limitations on user interaction with AMP content
|
| • The speaker discusses the benefits and potential drawbacks of AMP (Accelerated Mobile Pages) technology
|
| • Rachel White questions whether AMP prioritizes certain websites over others, potentially affecting search results
|
| • Alex Sexton explains that AMP's primary goal is to make the web better, but the incentives for adoption are indirect, such as improved SEO and ranking
|
| • Mikeal Rogers criticizes AMP, saying it creates a proprietary format that requires websites to conform to Google's rules in order to get into the top search results
|
| • The discussion touches on issues of fake news, conspiracy theories, and the potential for untrustworthy sources to game the system
|
| • Alex Sexton acknowledges that while AMP has its flaws, killing it would not necessarily solve the underlying problems of misinformation on the web
|
| • Centralization of AMP pages and its performance benefits
|
| • Concerns about relying on a centralized system for performance
|
| • Ease of integration of AMP into existing websites
|
| • Potential backlash against AMP due to serving different content to Google vs users
|
| • JavaScript fatigue and the burden of choice among various frameworks, libraries, and tools
|
| • The unique challenges of the JavaScript community in terms of "paralysis of choice"
|
| • The concept of "JavaScript fatigue" refers to the overwhelming number of frameworks and tools available for building web applications
|
| • This problem predates the npm ecosystem but has been accelerated by it
|
| • Frameworks have always been a part of web development, but the explosion in their number has made it difficult for developers to keep up
|
| • The issue is not just about learning new tools, but also about the hidden semantics and complexity that come with using frameworks
|
| • This can lead to a narrow worldview among developers who specialize in specific frameworks or technologies
|
| • There are alternatives to this approach, such as using small components with understandable inputs and outputs, which can make it easier to adopt new modules and replace old ones
|
| • Frameworks helping to prevent JavaScript fatigue by making many choices by default
|
| • The problem of module makers creating many different versions of the same thing contributing to JS fatigue
|
| • The tradeoff between learning new tools and gaining speed in application development
|
| • The role of free markets and innovation driving new solutions in web and JavaScript tooling
|
| • The debate on whether innovation is driven by new capabilities or new use cases
|
| • New frameworks emerging as a response to new problems or challenges, rather than underlying platform changes
|
| • Underutilization of language-level features that could simplify development, such as tagged template literals
|
| • The potential for new technologies and patterns to emerge once the next set of use cases is understood.
|
| • The discussion revolves around a new library that allows for easier use of SVG and math operations
|
| • The mid-level API makes it accessible for users who aren't familiar with intense SVG coding
|
| • Comparison to D3, where many libraries use D3 as an underlying tool but require knowledge of D3 itself
|
| • Discussion about how the new library could be used in conjunction with other libraries and its potential impact on the ecosystem
|
| • Criticism of D3's complexity and difficulty for non-visual programmers to understand
|
| • Comparison to other types of programming, such as WebGL, which is also complex and difficult to understand
|
| • The introduction of Rachel White's pick: Tracery, a library that allows for easier generative storytelling through grammar objects
|
| • Discussion about the format of their podcast being similar to "mad libs" stories
|
| • Mikeal Rogers' pick of the week: Lemonade Stand, a repository of open source funding models by Nadia Eghbal
|
| • Alex Sexton's pick of the week: Intl.js library, a polyfill for internationalization and formatting in web development
|
| • Brief conversation about Andy Earnshaw's polyfill for Intl.js and its limitations
|
| • Mikeal Rogers' question about whether Intl.js can convert foreign exchange rate currencies
|
| • Humorous exchange about Mikeal's European travel plans and the strength of the US dollar |
