<story><title>The real responsive design challenge is RSS</title><url>https://begriffs.com/posts/2016-05-28-rss-responsive-design.html?hn=1</url></story><parent_chain><item><author>usaphp</author><text>&amp;gt; &amp;quot;web-hipster bullshit&amp;quot;&lt;p&gt;Why so much negativity lately regarding new trends in the web?</text></item><item><author>toyg</author><text>Hey, a post about RSS content quirks! It makes me feel young again!&lt;p&gt;On a more serious note - RSS is the Great Web Leveller. It spites your fancy CSS hacks, it&amp;#x27;s disgusted by your insane javascript, and it will piss all over your &amp;quot;mobile-optimized&amp;quot; crap. No semantic markup == no party; because markup is for robots, and RSS parsers are very stubborn robots that can see through web-hipster bullshit like Superman through walls.&lt;p&gt;The only real sin of RSS (beyond the holy wars and format bikeshedding and committee madness and and and...) is that it&amp;#x27;s too honest a format. It&amp;#x27;s a format for stuff that matters, for content that deserves to be read; it&amp;#x27;s too pure to survive in a world of content silos, stalking analytics and inaccessible material-designs. Its innocence doomed it in a very poetic way.</text></item></parent_chain><comment><author>toyg</author><text>One reason might be that, for anyone with historical perspective, a situation where our pipes can download hundreds of MB per second and &lt;i&gt;still&lt;/i&gt; our browsers crawl like turtles is just shocking. Modern browsers are the most compatible ever and come with all sorts of bells and whistles baked in, and &lt;i&gt;still&lt;/i&gt; people are using JS frameworks over JS frameworks over JS frameworks.&lt;p&gt;Another reason might be that most of this website-fat is actively anti-users. It breaks the back button. It breaks bookmarks. It spies on you. It makes it impossible to interoperate&amp;#x2F;mash stuff, and it makes it incredibly hard to automate things (do you know that in the &amp;#x27;90s you used to be able to download entire websites, so you could comfortably read them offline?).&lt;p&gt;Another reason is probably that a lot of &amp;quot;mainstream web plumbers&amp;quot; (like yours truly) are now hitting late middle-age and feeling it hard. We used to be able to view-source and copypaste our way to image-rollover glory; we were breathing markup and feeds... now it&amp;#x27;s all tooling and frameworks and stacks, even http is going binary, and it feels like the loss of this innocence is not actually gaining anything for anyone except marketing people.&lt;p&gt;Now get off my lawn.</text></comment>
<story><title>The real responsive design challenge is RSS</title><url>https://begriffs.com/posts/2016-05-28-rss-responsive-design.html?hn=1</url></story><parent_chain><item><author>usaphp</author><text>&amp;gt; &amp;quot;web-hipster bullshit&amp;quot;&lt;p&gt;Why so much negativity lately regarding new trends in the web?</text></item><item><author>toyg</author><text>Hey, a post about RSS content quirks! It makes me feel young again!&lt;p&gt;On a more serious note - RSS is the Great Web Leveller. It spites your fancy CSS hacks, it&amp;#x27;s disgusted by your insane javascript, and it will piss all over your &amp;quot;mobile-optimized&amp;quot; crap. No semantic markup == no party; because markup is for robots, and RSS parsers are very stubborn robots that can see through web-hipster bullshit like Superman through walls.&lt;p&gt;The only real sin of RSS (beyond the holy wars and format bikeshedding and committee madness and and and...) is that it&amp;#x27;s too honest a format. It&amp;#x27;s a format for stuff that matters, for content that deserves to be read; it&amp;#x27;s too pure to survive in a world of content silos, stalking analytics and inaccessible material-designs. Its innocence doomed it in a very poetic way.</text></item></parent_chain><comment><author>gue5t</author><text>Because continued development of the Web is an obvious, user-hostile money-grab. If you only care about getting your software to users, you have a million choices for your application runtime. If you want to &lt;i&gt;monetize&lt;/i&gt; every user by selling their privacy or headspace, you have only one: i.e., &amp;quot;pirating&amp;quot; Facebook is a logical impossibility. Communicative efficacy on the Web has not improved since the early 1990s--Javascript and its ilk have virtually no positive effect on the usefulness of Wikipedia, for example. We&amp;#x27;re converting what was intended to be a transport for communication into a framework for writing portable software.&lt;p&gt;The thesis here is that there should be a digital way to share hypertext articles and other statically-described communication without pay the costs (privacy, rendering efficiency, security bugs, transport performance and uncacheability, accessibility) associated with a cross-platform sandboxed multimedia software runtime.</text></comment>