Quote:
Originally Posted by alheva
Thanks again for your interest, all of you.
Finally, I must say that I was expecting for a big, big update of Marvin (and I know 3 is showing many interesting features, so far). Of course, I thought that Marvin 3 would be a new version, not a new app -as Turtle suggests-. Otherwise it should have came with a new NAME, not a new number.
And I say again: in my opinion Marvin is, by far, the best e-reading app -at least for Ipads-.
|
I definitely agree with your opinion that Marvin is the best e-reading app! And I dare say that there is actually quite a bit of improvement "under the hood". One of the big advances is Marvin's ability to read ePub3 (not to mention cbx/cbr) files. I'm sure that was one of the reasons Kris took a "ground-up rewrite" stance on the coding - it probably was much easier than trying to fix the old code. He also took the opportunity to remove some of the "bloat" - features that were not popular or only desired by a handful of vocal users - and focus on Marvin being a
reading app.
The numbering system is pretty much industry standard - how else do the vendors capitalize on name recognition?? Even software that doesn't use numbers simply use a name
attached to, or
associated with, the main name...
For those that don't know their ear from a hole in the ground about programming - and expect to get whatever they want just because they can
imagine it being possible - they need to realize that they will hear the same answer over and over again when they ask the same question over and over and over and over and over again. The answer doesn't change just because they ask the question again. For someone who is so into languages (and is supposed to be good at it??
) they should realize that words have meanings and intentionally using the wrong word incorrectly does not make them a better person - it just shows their arrogantly condescending ignorance...
Definition of a computer bug:
Quote:
|
A software bug is an error, flaw, failure or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.
|
emphasis added
If the programmer
intended their code to behave in a specific manner, then it
is not a bug. It is a "feature" of the program. You may not like the feature, you may not agree with the feature, you may think of half a dozen ways to make the feature better, but it is a feature and not a bug.
And...as I mentioned above...I happen to agree that feature is not well implemented. I just choose not to be a hot headed windbag and whine and complain and bully until I force my opinions on others. I mention it once to someone who is able to actually fix the problem - rather than rant on a public forum attempting to make myself look important. After giving my arguments/reasons to the person who can actually do something about it, I let them make the decision on how to go forward. If they take my advice, then great! If they don't, then so be it. I'm not going to throw a temper tantrum like a two-year-old who doesn't get his candy.... after all, it isn't my program/app...
Have a great day!
