Quote:
Originally Posted by loviedovie
kovid
Please take it easy. We all love Calibre but we are trying to understand why the certain decisions were made such that they changed the previous behaviors drastically.
|
This is exactly what I meant in my last post.. the community (esp. the people also working in the IT for many many years) just want to understand such drastic design changes like between V2 and V3 and have to learn, how to deal with it. Mainly if those changes affects the actual implementations in such a way, that it has to get extremly be re-designed or even brakes some functionalities that where successfully used in former versions.
Quote:
Originally Posted by loviedovie
Sure, I understand that multiple sources modifying the database is a no no. I get that. But what I do not understand is that why the new tangent was a choice of design compared to the previous behaviour? I already tried to give you an example where the gui or the server approach just make it sound just like highway or my way thing instead of user friendliness.
|
I also think it is always not a good idea to develop "next to" the users needs only because me as developer personally think a new decision is a good thought but perhaps 90% of the users don't need or don't like it or the way, it will be implemented.
Quote:
Originally Posted by loviedovie
Please do not get me wrong. I am pretty sure that you have a much better grasp of these things compared to most of us but from the user perspective, certain changes are just "too much" to adapt right away if you will, when it comes to the server/client thing. I am personally not upgrading( not mad or anything) because I need to figure out first how I can fit this new model into my user space.
|
Exactly... such drastic design changes can make an update very complicated or even impossible so that users could look for alternatives