Prev: Automatic File Translation Utility for Windows-based Mobile Devices
Next: Help With Free WiFi !!
From: nospam on 24 May 2010 16:51 In article <4golv5hng752vpfhlsgkbbucfivd1ordg1(a)4ax.com>, John Navas <jnspam1(a)navasgroup.com> wrote: > Total nonsense. Evidence abounds in comparable but properly-designed > non-bloated robust Windows software. properly designed is a fuzzy term. who determines whether it is or not? you? there is also no comparable software that does what itunes does, only a small subset. > >as for the bloat, it has too many features (music, movies, apps, email, > >activate phones, etc.) but on the other hand, that makes it easier to > >sync everything with one click. > > It's not just features. It's design, horribly bloated by any measure. because you say so? it does have feature bloat, i'm the first to say that, but that's a design decision to make it easy to sync ipods and iphones. the alternative would be multiple apps, and that's much worse. > >> You've proven that iTunes is not ready for prime time. > > > >it's very ready for prime time. it has its faults but not the ones > >you're claiming. > > Too late -- you've already conceded the point. i've done no such thing. > >> The average user isn't willing to get special training -- > >> they expect it to just work. Imagine that. ;) > > > >training? what in hell are you talking about? it's very easy to use. on > >first launch it asks to look for music. after that, just drag new music > >to it. you can even set up a watch folder to auto-add music. sorting is > >no more difficult than a single click. > > It's you that's brought up the issue of training. nope. you mentioned users needing special training. no such training is required. > >anyone that can't figure out how to use itunes has bigger problems. > > It's not bad software, so it must be bad users! apparently so. > >> You've just demonstrated that you don't have relevant expertise. > > > >i've done no such thing and i'm not the one with the corrupted itunes > >databases. > > Actually you have. again, no > >> >not to mention that a system crash is rare and itunes can rebuild the > >> >database, but why let that get in the way of anything. > >> > >> Unfortunately it doesn't. > >> Unless you have a manual backup, your playlists are history. > > > >wrong. > > Then prove it. to quote you: > In article <buolv555otri2vhhs6ulblml5gr0mf3ov2(a)4ax.com>, John Navas > <jnspam1(a)navasgroup.com> wrote: > > > Why should I bother? > > The difference is patently obvious, and your mind is clearly made up. > >and you still haven't explained this so called corruption. i'm > >beginning to think it doesn't exist. > > I've explained it sufficiently for anyone with even less expertise than > you've claimed. no you have not. specifically what gets corrupted? how is it out of sync? how did you fix it? you're very light on details, which is not at all surprising.
From: John Navas on 24 May 2010 22:19 On Mon, 24 May 2010 13:51:27 -0700, nospam <nospam(a)nospam.invalid> wrote in <240520101351274825%nospam(a)nospam.invalid>: >specifically what gets corrupted? how is it out of sync? how did you >fix it? you're very light on details, which is not at all surprising. If you don't known that and how a system crash can cause corruption of open output or update files, not to mention the file system itself, then you lack the necessary expertise to understand what I'm saying (no offense intended). -- Best regards, John If the iPhone is really so impressive, why do iFans keep making excuses for it?
From: nospam on 24 May 2010 22:46 In article <tkcmv5hd9s2082q40pd8veo1hcsooqujqc(a)4ax.com>, John Navas <jnspam1(a)navasgroup.com> wrote: > >specifically what gets corrupted? how is it out of sync? how did you > >fix it? you're very light on details, which is not at all surprising. > > If you don't known that and how a system crash can cause corruption of > open output or update files, not to mention the file system itself, then > you lack the necessary expertise to understand what I'm saying (no > offense intended). you're avoiding answering my questions and trying to twist it into something it isn't. so noted. of course a system crash can potentially cause problems (it doesn't always), but that's not the fault of itunes. furthermore, its database is not as fragile as you imply.
From: John Navas on 24 May 2010 23:58 On Mon, 24 May 2010 19:46:49 -0700, nospam <nospam(a)nospam.invalid> wrote in <240520101946497438%nospam(a)nospam.invalid>: >In article <tkcmv5hd9s2082q40pd8veo1hcsooqujqc(a)4ax.com>, John Navas ><jnspam1(a)navasgroup.com> wrote: >> If you don't known that and how a system crash can cause corruption of >> open output or update files, not to mention the file system itself, then >> you lack the necessary expertise to understand what I'm saying (no >> offense intended). > >you're avoiding answering my questions and trying to twist it into >something it isn't. so noted. Nothing of the sort. If you're not being disingenuous, then you lack the necessary expertise to understand what I'm writing. >of course a system crash can potentially cause problems (it doesn't >always), but that's not the fault of itunes. Being so fragile is the fault of iTunes. >furthermore, its database >is not as fragile as you imply. It is fragile. -- Best regards, John If the iPhone is really so impressive, why do iFans keep making excuses for it?
From: nospam on 25 May 2010 00:12
In article <qhimv51dvm17ta3eq48i6u2l2afgnevjoc(a)4ax.com>, John Navas <jnspam1(a)navasgroup.com> wrote: > >> If you don't known that and how a system crash can cause corruption of > >> open output or update files, not to mention the file system itself, then > >> you lack the necessary expertise to understand what I'm saying (no > >> offense intended). > > > >you're avoiding answering my questions and trying to twist it into > >something it isn't. so noted. > > Nothing of the sort. If you're not being disingenuous, then you lack > the necessary expertise to understand what I'm writing. i understand it, and it's irrelevant. answer the question. > >of course a system crash can potentially cause problems (it doesn't > >always), but that's not the fault of itunes. > > Being so fragile is the fault of iTunes. it's not fragile > >furthermore, its database > >is not as fragile as you imply. > > It is fragile. nope. otherwise it would be a common problem. it isn't. |