1w6 uRPGincompatible
http://sn.1w6.org/tag/incompatible/rss
Mit „incompatible“ getaggte Nachrichten auf „1w6 uRPG“!drak: @quix0r on #twitter this evolved into a slightly longer (but one-sided) discussion: drak: @adaptivepattern For blind people: Just write clean HTML+CSS pages. Blind people can use those easily. drak: @adaptivepattern: It is 2014: Good webdesign with strong basics: If you require Javascript to read email archives, you do it wrong drak: adaptivepattern: @ArneBab ~ #UX and #JavaScript are not mutually exclusive. A false choice? For #RIA and #SPA, #JS is UX... drak: @adaptivepattern #Javascript makes for horrible #UX, except if you want to constrain your users to have exactly one UX. drak: @adaptivepattern And if you’re going to push #json streams for API-users, why not write clean HTML in the first place? drak: @adaptivepattern The best pages for information I know are simple, static HTML+CSS sites. Also see http://xkcd.com/1309/ drak: @adaptivepattern or click somewhere next to the timeline in #twitter to hide the autocomplete and see your tweet content disappear #grr drak: @adaptivepattern or watch http://xkcd.com/1264/ . Or try to use #itsalltext with G+. #JS = #incompatible, #incoherent #UX drak: @adaptivepattern #damn, now I have to archive all these tweets by hand, because I did not use a client to escape the twitter-ux constraints. drak: @adaptivepattern I see only 2 good reasons for requiring #Javascript: (1/2): Updating small portions of the site without disturbing the user drak: @adaptivepattern and (2/2) deploying cross-platform apps to people who do not control their computers. (1/2) can still keep #JS optional. drak: @adaptivepattern And I know very few examples of full apps in #Javascript which actually yield advantages for the users.
http://sn.1w6.org/notice/39260
drak's status on Tuesday, 07-Jan-14 05:36:07 UTC@<span class="vcard"><a href="https://status.mxchange.org/quix0r" class="url" title="quix0r"><span class="fn nickname mention">quix0r</span></a></span> on #<span class="tag"><a href="http://sn.1w6.org/tag/twitter" rel="tag">twitter</a></span> this evolved into a slightly longer (but one-sided) discussion: drak: @adaptivepattern For blind people: Just write clean HTML+CSS pages. Blind people can use those easily. drak: @adaptivepattern: It is 2014: Good webdesign with strong basics: If you require Javascript to read email archives, you do it wrong drak: adaptivepattern: @ArneBab ~ #<span class="tag"><a href="http://sn.1w6.org/tag/ux" rel="tag">UX</a></span> and #<span class="tag"><a href="http://sn.1w6.org/tag/javascript" rel="tag">JavaScript</a></span> are not mutually exclusive. A false choice? For #<span class="tag"><a href="http://sn.1w6.org/tag/ria" rel="tag">RIA</a></span> and #<span class="tag"><a href="http://sn.1w6.org/tag/spa" rel="tag">SPA</a></span>, #<span class="tag"><a href="http://sn.1w6.org/tag/js" rel="tag">JS</a></span> is UX... drak: @adaptivepattern #<span class="tag"><a href="http://sn.1w6.org/tag/javascript" rel="tag">Javascript</a></span> makes for horrible #<span class="tag"><a href="http://sn.1w6.org/tag/ux" rel="tag">UX</a></span>, except if you want to constrain your users to have exactly one UX. drak: @adaptivepattern And if you’re going to push #<span class="tag"><a href="http://sn.1w6.org/tag/json" rel="tag">json</a></span> streams for API-users, why not write clean HTML in the first place? drak: @adaptivepattern The best pages for information I know are simple, static HTML+CSS sites. Also see <a href="http://xkcd.com/1309/" title="http://xkcd.com/1309/" rel="nofollow external">http://xkcd.com/1309/</a> drak: @adaptivepattern or click somewhere next to the timeline in #<span class="tag"><a href="http://sn.1w6.org/tag/twitter" rel="tag">twitter</a></span> to hide the autocomplete and see your tweet content disappear #<span class="tag"><a href="http://sn.1w6.org/tag/grr" rel="tag">grr</a></span> drak: @adaptivepattern or watch <a href="http://xkcd.com/1264/" title="http://xkcd.com/1264/" rel="nofollow external">http://xkcd.com/1264/</a> . Or try to use #<span class="tag"><a href="http://sn.1w6.org/tag/itsalltext" rel="tag">itsalltext</a></span> with G+. #<span class="tag"><a href="http://sn.1w6.org/tag/js" rel="tag">JS</a></span> = #<span class="tag"><a href="http://sn.1w6.org/tag/incompatible" rel="tag">incompatible</a></span>, #<span class="tag"><a href="http://sn.1w6.org/tag/incoherent" rel="tag">incoherent</a></span> #<span class="tag"><a href="http://sn.1w6.org/tag/ux" rel="tag">UX</a></span> drak: @adaptivepattern #<span class="tag"><a href="http://sn.1w6.org/tag/damn" rel="tag">damn</a></span>, now I have to archive all these tweets by hand, because I did not use a client to escape the twitter-ux constraints. drak: @adaptivepattern I see only 2 good reasons for requiring #<span class="tag"><a href="http://sn.1w6.org/tag/javascript" rel="tag">Javascript</a></span>: (1/2): Updating small portions of the site without disturbing the user drak: @adaptivepattern and (2/2) deploying cross-platform apps to people who do not control their computers. (1/2) can still keep #<span class="tag"><a href="http://sn.1w6.org/tag/js" rel="tag">JS</a></span> optional. drak: @adaptivepattern And I know very few examples of full apps in #<span class="tag"><a href="http://sn.1w6.org/tag/javascript" rel="tag">Javascript</a></span> which actually yield advantages for the users.2014-01-07T05:36:07+00:00drakdrakdrak