<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Blog vs. Blog: Daring Fireball/GigaOm MobileMe-nia!</title>
	<atom:link href="http://www.theiphoneblog.com/2008/08/06/blog-vs-blog-daring-fireballgigaom-mobileme-nia/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.theiphoneblog.com/2008/08/06/blog-vs-blog-daring-fireballgigaom-mobileme-nia/</link>
	<description>For people who dare to Phone Different.</description>
	<lastBuildDate>Mon, 23 Nov 2009 00:38:59 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: His_wife83</title>
		<link>http://www.theiphoneblog.com/2008/08/06/blog-vs-blog-daring-fireballgigaom-mobileme-nia/comment-page-1/#comment-88120</link>
		<dc:creator>His_wife83</dc:creator>
		<pubDate>Thu, 22 Oct 2009 19:51:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.theiphoneblog.com/?p=3645#comment-88120</guid>
		<description>&lt;p&gt;Nontheless, citizens need to participate in decision-making about important issues and be provided with opportunities to deliberate with those who can inform the discussion. ,&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Nontheless, citizens need to participate in decision-making about important issues and be provided with opportunities to deliberate with those who can inform the discussion. ,</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Settor11</title>
		<link>http://www.theiphoneblog.com/2008/08/06/blog-vs-blog-daring-fireballgigaom-mobileme-nia/comment-page-1/#comment-88119</link>
		<dc:creator>Settor11</dc:creator>
		<pubDate>Thu, 22 Oct 2009 19:50:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.theiphoneblog.com/?p=3645#comment-88119</guid>
		<description>&lt;p&gt;This philosophy moves   the library deeper into the realms of openness, transparency, and participation. ,&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>This philosophy moves   the library deeper into the realms of openness, transparency, and participation. ,</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://www.theiphoneblog.com/2008/08/06/blog-vs-blog-daring-fireballgigaom-mobileme-nia/comment-page-1/#comment-12139</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Mon, 11 Aug 2008 02:29:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.theiphoneblog.com/?p=3645#comment-12139</guid>
		<description>&lt;p&gt;WebObjects http://developer.apple.com/tools/webobjects/ http://members.capmac.org/~orb/blog.cgi/tech/Open&lt;em&gt;source&lt;/em&gt;WebObje.html may have been around for a long time, but it&#039;s hardly old school (given the relationship through Java is transitive). (What would you consider new school?) It is still the best back-end technology for generating dynamic web pages and a lot of work is going on in it both in Apple and outside.&lt;/p&gt;

&lt;p&gt;As for MobileMe... it was more a fiasco than a disaster. I think you could put it down to some management somewhere wanting everything done at once. Good technical people would have gone for a staged roll out. I think SJ&#039;s email recognizes that&#039;s the way Apple will do things in future. But for all the things they did try to do in that week, perhaps things actually went exceptionally well, which shows how Apple&#039;s technology stands up really well against management stupidity.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>WebObjects <a href="http://developer.apple.com/tools/webobjects/" rel="nofollow">http://developer.apple.com/tools/webobjects/</a> <a href="http://members.capmac.org/~orb/blog.cgi/tech/Open" rel="nofollow">http://members.capmac.org/~orb/blog.cgi/tech/Open</a><em>source</em>WebObje.html may have been around for a long time, but it&#8217;s hardly old school (given the relationship through Java is transitive). (What would you consider new school?) It is still the best back-end technology for generating dynamic web pages and a lot of work is going on in it both in Apple and outside.</p>

<p>As for MobileMe&#8230; it was more a fiasco than a disaster. I think you could put it down to some management somewhere wanting everything done at once. Good technical people would have gone for a staged roll out. I think SJ&#8217;s email recognizes that&#8217;s the way Apple will do things in future. But for all the things they did try to do in that week, perhaps things actually went exceptionally well, which shows how Apple&#8217;s technology stands up really well against management stupidity.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Rene Ritchie</title>
		<link>http://www.theiphoneblog.com/2008/08/06/blog-vs-blog-daring-fireballgigaom-mobileme-nia/comment-page-1/#comment-12125</link>
		<dc:creator>Rene Ritchie</dc:creator>
		<pubDate>Mon, 11 Aug 2008 01:23:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.theiphoneblog.com/?p=3645#comment-12125</guid>
		<description>&lt;p&gt;&quot;If you have no idea what you are talking about, why are you doing it in the first place?&quot;&lt;/p&gt;

&lt;p&gt;Silly me, I forgot this was the intertubes where, rather than engaging and providing additional information in the spirit of community and shared learning, we must act all prissy-rude and confrontational -- especially when we miss our cybernaps. My bad.&lt;/p&gt;

&lt;p&gt;FWIW - I was aware of the different areas WebObjects and SproutCore cover, I just didn&#039;t think about MobileMe using WebObjects behind SproutCore (makes perfect sense though), and thought iTunes was more like a dedicated WebKit browser than &quot;iTunes&quot;, which I guess your saying is more akin to a SproutCore-like frontend framework?&lt;/p&gt;

&lt;p&gt;Thanks for the insights, however. All that time spent on the IE 6 render-engine team and Friendster scalability panel was obviously well spent :)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>&#8220;If you have no idea what you are talking about, why are you doing it in the first place?&#8221;</p>

<p>Silly me, I forgot this was the intertubes where, rather than engaging and providing additional information in the spirit of community and shared learning, we must act all prissy-rude and confrontational &#8212; especially when we miss our cybernaps. My bad.</p>

<p>FWIW &#8211; I was aware of the different areas WebObjects and SproutCore cover, I just didn&#8217;t think about MobileMe using WebObjects behind SproutCore (makes perfect sense though), and thought iTunes was more like a dedicated WebKit browser than &#8220;iTunes&#8221;, which I guess your saying is more akin to a SproutCore-like frontend framework?</p>

<p>Thanks for the insights, however. All that time spent on the IE 6 render-engine team and Friendster scalability panel was obviously well spent <img src='http://www.theiphoneblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>]]></content:encoded>
	</item>
	<item>
		<title>By: G.</title>
		<link>http://www.theiphoneblog.com/2008/08/06/blog-vs-blog-daring-fireballgigaom-mobileme-nia/comment-page-1/#comment-12106</link>
		<dc:creator>G.</dc:creator>
		<pubDate>Sun, 10 Aug 2008 16:18:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.theiphoneblog.com/?p=3645#comment-12106</guid>
		<description>&lt;p&gt;&quot;The crazy thing is, MobileMe should have been an iTunes-learned breeze for Apple in terms of meeting service levels, given their pedigree. But then iTunes uses WebObjects (which I believe is old school Java-based) and MobileMe uses SproutCore (which is all dressed up in Ajax-y 2.0 objectivity), and the pretty much disastrous July 11th launch, which took down both iTunes iPhone activation, and slammed the MobileMe servers into weeks of problems, show something clearly is different with the new kit on the block.&quot;&lt;/p&gt;

&lt;p&gt;If you have no idea what you are talking about, why are you doing it in the first place?&lt;/p&gt;

&lt;p&gt;SproutCore is a frontend display layer while WebObjects is server side technology for providing the data. Both, iTunes Store AND Mobile Me are using WebObjects as the backend data provider, the iTunes Store uses iTunes and Mobile Me uses SproutCore in a browser as the display layer. &lt;/p&gt;

&lt;p&gt;I don&#039;t know why the Mobile Me start was so disastrous, but it had NOTHING to do with SproutCore because that is only DISPLAYING what comes from the server. Get it?&lt;/p&gt;

&lt;p&gt;Probably they underestimated demand and new signups and added servers over the first days until the load was spread over enough hardware. That they had dataloss on a mailserver is a completely different topic ...&lt;/p&gt;

&lt;p&gt;So, please, if you give your opinion on something, please make it clear, that you have:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;No background knowledge at all.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Obviously no knowledge about the used technologies.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;No knowledge to base educated guesses upon.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;
</description>
		<content:encoded><![CDATA[<p>&#8220;The crazy thing is, MobileMe should have been an iTunes-learned breeze for Apple in terms of meeting service levels, given their pedigree. But then iTunes uses WebObjects (which I believe is old school Java-based) and MobileMe uses SproutCore (which is all dressed up in Ajax-y 2.0 objectivity), and the pretty much disastrous July 11th launch, which took down both iTunes iPhone activation, and slammed the MobileMe servers into weeks of problems, show something clearly is different with the new kit on the block.&#8221;</p>

<p>If you have no idea what you are talking about, why are you doing it in the first place?</p>

<p>SproutCore is a frontend display layer while WebObjects is server side technology for providing the data. Both, iTunes Store AND Mobile Me are using WebObjects as the backend data provider, the iTunes Store uses iTunes and Mobile Me uses SproutCore in a browser as the display layer. </p>

<p>I don&#8217;t know why the Mobile Me start was so disastrous, but it had NOTHING to do with SproutCore because that is only DISPLAYING what comes from the server. Get it?</p>

<p>Probably they underestimated demand and new signups and added servers over the first days until the load was spread over enough hardware. That they had dataloss on a mailserver is a completely different topic &#8230;</p>

<p>So, please, if you give your opinion on something, please make it clear, that you have:</p>

<ol>
<li><p>No background knowledge at all.</p></li>
<li><p>Obviously no knowledge about the used technologies.</p></li>
<li><p>No knowledge to base educated guesses upon.</p></li>
</ol>]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://www.theiphoneblog.com/2008/08/06/blog-vs-blog-daring-fireballgigaom-mobileme-nia/comment-page-1/#comment-11921</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Wed, 06 Aug 2008 18:38:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.theiphoneblog.com/?p=3645#comment-11921</guid>
		<description>&lt;p&gt;What amazes me is the real story is how buggy iTunes and the iPhone software is. How unreliable the iPhone is, how often apps crash and brick your phone. This is a mess, that the fanboys do not want to talk about. One visit to the Apple support forums and you will see just how widespread it is.&lt;/p&gt;

&lt;p&gt;I have had my iPhone brick 22 times in 22 days, I got a replacement and it was no better. the iTunes and iPhone updates have done NOTHING to relieve the problem!&lt;/p&gt;

&lt;p&gt;Blackberry has nothing to worry about if this keeps up.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>What amazes me is the real story is how buggy iTunes and the iPhone software is. How unreliable the iPhone is, how often apps crash and brick your phone. This is a mess, that the fanboys do not want to talk about. One visit to the Apple support forums and you will see just how widespread it is.</p>

<p>I have had my iPhone brick 22 times in 22 days, I got a replacement and it was no better. the iTunes and iPhone updates have done NOTHING to relieve the problem!</p>

<p>Blackberry has nothing to worry about if this keeps up.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: stephen lakis</title>
		<link>http://www.theiphoneblog.com/2008/08/06/blog-vs-blog-daring-fireballgigaom-mobileme-nia/comment-page-1/#comment-11920</link>
		<dc:creator>stephen lakis</dc:creator>
		<pubDate>Wed, 06 Aug 2008 18:11:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.theiphoneblog.com/?p=3645#comment-11920</guid>
		<description>&lt;p&gt;i couldn&#039;t wait to by the new i phone. Being an exclusive user of mac laptops, desktops, and ipods I figured the new i phone would seamlessly fit my business needs. From the day I purchased it (about a week ago) until the day I returned it, this past Monday, the i phone completely disappointed me.&lt;/p&gt;

&lt;p&gt;The email functions in comparison to my blackberry, in a word, suck. I was astonished by the limited applicability of the so called push function. I couldn&#039;t push aol and I couldn&#039;t push my .mac mail. What&#039;s more I could never resolve sending mail from my devise! Whenever I attempted to reply to an email I received a notice that the address was invalid! And believe me, I spent countless hours with applecare trying to resolve all my problems. One tech person instructed me to turn off the 3G, wifi and switch to manually searching for email as a means to save battery life and stop my phone from continuously searching for mail or trying to send mail! What&#039;s the point of having all these services if you can&#039;t use them?  &lt;/p&gt;

&lt;p&gt;The i phone is  a great toy but no comparison to the blackberry for serious business use—and being an exclusive mac user, this is hard for me say.&lt;/p&gt;

&lt;p&gt;One final word... I am mystified by the lack of critical comment on the significant shortcomings of the i phone&#039;s email functions and battery life, especially when contrasted with blackberrys. Am I missing something here? And will Mac eventually resolve these weaknesses so I can consider again purchasing an i phone?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>i couldn&#8217;t wait to by the new i phone. Being an exclusive user of mac laptops, desktops, and ipods I figured the new i phone would seamlessly fit my business needs. From the day I purchased it (about a week ago) until the day I returned it, this past Monday, the i phone completely disappointed me.</p>

<p>The email functions in comparison to my blackberry, in a word, suck. I was astonished by the limited applicability of the so called push function. I couldn&#8217;t push aol and I couldn&#8217;t push my .mac mail. What&#8217;s more I could never resolve sending mail from my devise! Whenever I attempted to reply to an email I received a notice that the address was invalid! And believe me, I spent countless hours with applecare trying to resolve all my problems. One tech person instructed me to turn off the 3G, wifi and switch to manually searching for email as a means to save battery life and stop my phone from continuously searching for mail or trying to send mail! What&#8217;s the point of having all these services if you can&#8217;t use them?  </p>

<p>The i phone is  a great toy but no comparison to the blackberry for serious business use—and being an exclusive mac user, this is hard for me say.</p>

<p>One final word&#8230; I am mystified by the lack of critical comment on the significant shortcomings of the i phone&#8217;s email functions and battery life, especially when contrasted with blackberrys. Am I missing something here? And will Mac eventually resolve these weaknesses so I can consider again purchasing an i phone?</p>]]></content:encoded>
	</item>
</channel>
</rss>

