<?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: Rant: 1.1.1 iPhone Update</title> <atom:link href="http://xentek.net/rants/36/rant-111-iphone-update/feed/" rel="self" type="application/rss+xml" /><link>http://xentek.net/rants/36/rant-111-iphone-update/</link> <description>enlightened internet solutions</description> <lastBuildDate>Thu, 04 Mar 2010 23:19:24 +0000</lastBuildDate> <generator>http://wordpress.org/?v=3.0-alpha</generator> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: Godless Geek</title><link>http://xentek.net/rants/36/rant-111-iphone-update/comment-page-1/#comment-6</link> <dc:creator>Godless Geek</dc:creator> <pubDate>Fri, 05 Oct 2007 20:15:45 +0000</pubDate> <guid
isPermaLink="false">http:/xentek.net/rants/36/rant-111-iphone-update/#comment-6</guid> <description>&lt;blockquote&gt;which was probably more of a side affect of updating files used in the unlocking process, than a deliberate attempt to break hacked phones&lt;/blockquote&gt;I don&#039;t see any reason to think otherwise.  I work for a software company that does extensive customization work with a commercial asset management software system, according to the needs of our customers.  The tools and SDK&#039;s are provided for us to do this work, but often what we are provided is simply not enough to do what we need, so we have to code around the system.  Once we get into the core of the development cycle on a new release, we lock ourselves down to a particular patch release of the parent software and do not change, because it is not infrequent that a new patch will break parts of our code.  This is not part of any intentional conspiracy by our upstream vendor (in fact, they are often astounded by our ingenuity), it is simply because they have made updates, changes, or bug fixes to a particular file that we have made functionality changes against, and changes in that file break our code.  I have no doubt that is the case here.  These software unlocks apparently do some pretty extensive modifications to the core software, so you can&#039;t expect it to simply keep working after even a minor bugfix update, much less one as extensive as this one.&lt;blockquote&gt;Leave a comment if you have one. Let me know how your update to 1.1.1 went or if you avoided the update because you unlocked it.&lt;/blockquote&gt;I have one.  I haven&#039;t unlocked it.  I&#039;ve been with BellSouth/Cingular/AT&amp;T for six or seven years and don&#039;t have any need to change.  I haven&#039;t modified it in any way, and honestly don&#039;t understand the desire (and I&#039;m a tinkerer to the nth degree).  I&#039;ve never understood the need to have games and obnoxious ringtones on a phone.  Update 1.1.1 went extremely smoothly for me.  Just click and forget.  Took about 10 minutes to apply.  A warning is displayed in large, bold letters before the update warning you not to run the update if you have unlocked or otherwise modified your iPhone software, so anyone who did install it has no excuse whatsoever.  They have the right to unlock it if they want to, but Apple is under no obligation whatsoever to support them.</description> <content:encoded><![CDATA[<blockquote><p>which was probably more of a side affect of updating files used in the unlocking process, than a deliberate attempt to break hacked phones</p></blockquote><p>I don&#8217;t see any reason to think otherwise.  I work for a software company that does extensive customization work with a commercial asset management software system, according to the needs of our customers.  The tools and SDK&#8217;s are provided for us to do this work, but often what we are provided is simply not enough to do what we need, so we have to code around the system.  Once we get into the core of the development cycle on a new release, we lock ourselves down to a particular patch release of the parent software and do not change, because it is not infrequent that a new patch will break parts of our code.  This is not part of any intentional conspiracy by our upstream vendor (in fact, they are often astounded by our ingenuity), it is simply because they have made updates, changes, or bug fixes to a particular file that we have made functionality changes against, and changes in that file break our code.  I have no doubt that is the case here.  These software unlocks apparently do some pretty extensive modifications to the core software, so you can&#8217;t expect it to simply keep working after even a minor bugfix update, much less one as extensive as this one.</p><blockquote><p>Leave a comment if you have one. Let me know how your update to 1.1.1 went or if you avoided the update because you unlocked it.</p></blockquote><p>I have one.  I haven&#8217;t unlocked it.  I&#8217;ve been with BellSouth/Cingular/AT&amp;T for six or seven years and don&#8217;t have any need to change.  I haven&#8217;t modified it in any way, and honestly don&#8217;t understand the desire (and I&#8217;m a tinkerer to the nth degree).  I&#8217;ve never understood the need to have games and obnoxious ringtones on a phone.  Update 1.1.1 went extremely smoothly for me.  Just click and forget.  Took about 10 minutes to apply.  A warning is displayed in large, bold letters before the update warning you not to run the update if you have unlocked or otherwise modified your iPhone software, so anyone who did install it has no excuse whatsoever.  They have the right to unlock it if they want to, but Apple is under no obligation whatsoever to support them.</p> ]]></content:encoded> </item> <item><title>By: { dr.xnlb: Of Apples and iPhones }</title><link>http://xentek.net/rants/36/rant-111-iphone-update/comment-page-1/#comment-5</link> <dc:creator>{ dr.xnlb: Of Apples and iPhones }</dc:creator> <pubDate>Fri, 05 Oct 2007 18:04:59 +0000</pubDate> <guid
isPermaLink="false">http:/xentek.net/rants/36/rant-111-iphone-update/#comment-5</guid> <description>[...] more of my opinion on my pro blog.   Email: dr.xnlb&#160;&#160;&#124;&#160;&#160;Filed under: blog  [...]</description> <content:encoded><![CDATA[<p>[...] more of my opinion on my pro blog.   Email: dr.xnlb&nbsp;&nbsp;|&nbsp;&nbsp;Filed under: blog  [...]</p> ]]></content:encoded> </item> </channel> </rss>
<!-- This site's performance optimized by W3 Total Cache. Dramatically improve the speed and reliability of your blog!

Learn more about our WordPress Plugins: http://www.w3-edge.com/wordpress-plugins/

Minified using apc
Page Caching using apc (user agent is rejected)
Database Caching 6/13 queries in 0.008 seconds using apc

Served from: web.xen.hostedbyxentek.net @ 2010-03-12 19:29:45 -->