<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on Joe Galley</title><link>https://joegalley.com/posts/</link><description>Recent content in Posts on Joe Galley</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 18 Jun 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://joegalley.com/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Graceful Degradation vs Progressive Enhancement</title><link>https://joegalley.com/posts/gradeful-degradation-vs-progressive-enhancement/</link><pubDate>Wed, 18 Jun 2025 00:00:00 +0000</pubDate><guid>https://joegalley.com/posts/gradeful-degradation-vs-progressive-enhancement/</guid><description>&lt;p&gt;With new web frameworks coming out every few months and new JavaScript and CSS libraries seemingly every few weeks, compatibility for older browsers and devices sometimes takes a back seat to the rapid pace of innovation on the web. For example, new CSS frameworks are using the flexbox standard which remains riddled with browser-specific issues. Taking advantage of these new features often means wrangling with obtuse issues in older browsers. There are two philosophies for dealing with these types of inconsistencies: graceful degradation and progressive enhancement.&lt;/p&gt;</description></item></channel></rss>