<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: intrnl</title>
    <description>The latest articles on DEV Community by intrnl (@intrnl).</description>
    <link>https://dev.to/intrnl</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F106098%2F6f362394-6ddd-46d9-b7c7-20348733e300.jpg</url>
      <title>DEV Community: intrnl</title>
      <link>https://dev.to/intrnl</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/intrnl"/>
    <language>en</language>
    <item>
      <title>Safari is problematic.</title>
      <dc:creator>intrnl</dc:creator>
      <pubDate>Thu, 16 Sep 2021 07:10:19 +0000</pubDate>
      <link>https://dev.to/intrnl/safari-is-problematic-2p6a</link>
      <guid>https://dev.to/intrnl/safari-is-problematic-2p6a</guid>
      <description>&lt;p&gt;I've never been an Apple user, maybe once, but not long enough to get into their ecosystem entirely, and yet I love what they do. I feel like they make great products, both hardware and software, but there's just one thing...&lt;/p&gt;




&lt;p&gt;Why is Apple so hostile towards the web platform?&lt;/p&gt;

&lt;p&gt;Safari is problematic, it does not support platforms other than iOS and macOS. If I want to get my website to work with those platforms, I have to invest into Apple's ecosystem.&lt;/p&gt;

&lt;p&gt;It's not cheap, especially when your biggest concerns are whether you're making enough money to put food into your mouth.&lt;/p&gt;

&lt;p&gt;So tell me, why do I have to support a browser, that is not only lacking a lot of the new API and features that makes it easy for us to build websites, but also costs a considerable fortune to get started?&lt;/p&gt;




&lt;p&gt;On my first point, this isn't something only I encounter. We can see that on &lt;a href="https://insights.developer.mozilla.org/reports/mdn-web-developer-needs-assessment-2020.html#technologies-browsers-that-cause-issues" rel="noopener noreferrer"&gt;MDN Web Developers Needs Assesment 2020 survey results&lt;/a&gt; that aside from Internet Explorer, a lot of web developers are having pains with Safari as well, and it's really high up there!&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fhnoblqx6nw8quyq35d7q.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fhnoblqx6nw8quyq35d7q.png" alt="A list of browsers that cause issues, as ranked by developers"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;As for the second, while I do know that as a Linux user I have the option of using WebKitGTK to test, it should be known clearly that this is still not Safari.&lt;/p&gt;

&lt;p&gt;Without an Apple device, would I be able to know that there's a workaround for getting IndexedDB to work on macOS 11.4 and iOS 14.6, and that's &lt;a href="https://github.com/jakearchibald/safari-14-idb-fix" rel="noopener noreferrer"&gt;to keep poking it until it decides to work&lt;/a&gt;?&lt;/p&gt;

&lt;p&gt;Theoretically, I could get a second-hand device, but is that really the only choice I can make in this situation?&lt;/p&gt;




&lt;p&gt;I've felt the need to write this post because, like many web developers, the reason why I started as one is because I want to build things that can be enjoyed by everyone, and the web just happens to be the best platform for that.&lt;/p&gt;

&lt;p&gt;So it's just sad to see that I, as a web developer, is unable to support iOS and macOS users, which could be a significant amount, just because I'm simply unable to do so.&lt;/p&gt;

&lt;p&gt;We should be able to build and deliver a great experience to everyone, without worrying about the differences in what the user's browser might support.&lt;/p&gt;

&lt;p&gt;Thanks for reading this short post. There's still a ton of points worth exploring, but I feel like this series of blog posts by Alex Russell really goes deep into things like this and it's worth a read.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://infrequently.org/2021/04/progress-delayed/" rel="noopener noreferrer"&gt;Progress Delayed Is Progress Denied&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://infrequently.org/2021/07/hobsons-browser/" rel="noopener noreferrer"&gt;Hobson's Browser&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://infrequently.org/2021/08/webkit-ios-deep-dive/" rel="noopener noreferrer"&gt;iOS Engine Choice In Depth&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
    </item>
  </channel>
</rss>
