<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Latest Comments for ern0</title><link>http://disqus.com/people/031d349e27a3c04ea878413e9af1e62f/</link><description></description><language>en</language><lastBuildDate>Sat, 18 Apr 2009 17:20:09 -0000</lastBuildDate><item><title>Re: OhGizmo!  &amp;raquo; Archive  &amp;raquo; Broken Image Necklace Fails To Load</title><link>http://ohgizmo.disqus.com/ohgizmo_raquo_archive_raquo_broken_image_necklace_fails_to_load/#comment-1766233</link><description>Netscape Navigator / Communicator 4.x. I'm sure, because I was using it until 2004(?), when it was already kinda technology dinosaur. (Now I'm using SeaMonkey.) Also, I did not even noticed that this icon is from an old software, it's _the_ broken image item for me :-)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ern0</dc:creator><pubDate>Thu, 20 Mar 2008 04:19:03 -0000</pubDate></item><item><title>Re: az igazs&amp;aacute;g pillanata</title><link>http://agyberles.disqus.com/az_igazsaacuteg_pillanata/#comment-8337182</link><description>palm pre, synergy, nemsokára</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ern0</dc:creator><pubDate>Sat, 18 Apr 2009 17:20:09 -0000</pubDate></item><item><title>Re: Application Distribution on webOS</title><link>http://pdnblog.disqus.com/application_distribution_on_webos/#comment-8662552</link><description>TOC&lt;br&gt;1. Native API&lt;br&gt;2. Sync/Backup&lt;br&gt;&lt;br&gt;&lt;br&gt;1. Native API&lt;br&gt;&lt;br&gt;Sooner ot later, there will be native apps hacked to the phone. So, it's better if *you* release the native API.&lt;br&gt;&lt;br&gt;PalmOS (from 5.x) runs M68000 code as default, and ARMlets can be called from the 68K emulation. For example, there's an image wiever written in 68K - except the JPEG decoder, which is an ARMlet (also, it contains the 68K alternative routine for Dragonball systems); and it runs fast as hell.&lt;br&gt;&lt;br&gt;WebOS should use similar mechanism. The interface should be as thin as possible, and it should forbid access to things which are accessable via JS API. Then, the holy day, when the newest Palm machine comes out with a new architecture (processor/family), only this thin layer (API + processor) must be emulated by the new version of the WebOS operating system, and only these small routines must be rewritten (or just recompiled) by sw developers.&lt;br&gt;&lt;br&gt;(I don't wanna live in a world, where I can't play Bejeweled with my Palm. Okay, it's not my favourite game, but others'.)&lt;br&gt;&lt;br&gt;&lt;br&gt;2. Sync/Backup&lt;br&gt;&lt;br&gt;I have a Treo650 now, and I don't sync. I am happy with the weekly backup to card.&lt;br&gt;&lt;br&gt;What about a small client which runs on the PC/Mac, and can receive the backup requests initiated from the phone? This small stuff should listen on your internet server as well, for a small fee (or for free: "We know that this gadget is the most important toy of you, dear customer, so we provide you not just reliable hardware but professional backup solution. We know, that your next phone will be a Palm too, so we're in continous partnership, and that's why we provide it for no extra fee. It's a kind of marketing cost for your next phone buying.").&lt;br&gt;&lt;br&gt;Also, if something make apart professionals from amateurs, it's the backup solution. Professionals take care of their data. Let turn Palm customers to Professionals.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ern0</dc:creator><pubDate>Sun, 18 Jan 2009 16:18:50 -0000</pubDate></item></channel></rss>