Philip Meyer;602559 Wrote:
>
>
> >Let's focus on the music related stuff which really matters instead
> of
> >technical issues like this which don't have any impact on our music
> >listening experience.
> >
> I'd actually prefer if Logitech focusses on making a stable platform,
> providing an extensible framework. I really don't think we'll ever see
> drastic changes in music browsing capabilities, and never with the same
> level of features that come from third-party plugins. Providing better
> development support to make creation of plugins easier is more likely to
> provide better power user facilities.
>
I can't disagree with you regarding this but things that are related to
third party plugins almost always gets low priority already today.
I would love if Logitech focused on making a stable core and made it
easy to enhance it with third party plugins. To make it easy to enhance
it with third party plugins, it's important to also take the QA time of
the third party developer into account. It will be easier for the third
party developers if they only have to verify their plugins with one
configuration.
Philip Meyer;602559 Wrote:
>
> Changing database engine should be easy with this app. There's hardly
> any difference in SQL queries, just how the DB is created and generally
> accessed.
>
As you say, the SQL isn't a big problem, even with my plugins which
heavily depends on native SQL most things work with both databases.
I might be wrong but I believe the main difference is not in the SQL,
the main difference is related to in-process database or a database
that runs as separate process.
Logitech has taken advantage of the in-process paradigm of SQLite to
get a more effective system and this makes it more complicated to also
support MySQL.
The big problem is the time it takes to do QA on two databases. This
effectively duplicates the testing time on some parts of the system. If
Logitech only do QA on one of the databases the other one isn't going to
work reliably. This is also pretty much what Andy's statement mean, it's
just that most people doesn't seem to understand it. To make MySQL
unusable, it's enough if Logitech decides to not prioritize one
important MySQL bug. To me it's obvious that it's going to be bugs left
if Logitech doesn't think MySQL is a priority.
--
erland
Erland Isaksson ('My homepage' (http://erland.isaksson.info))
(Developer of 'many plugins/applets'
(http://wiki.slimdevices.com/index.php/User:Erland). If my answer
helped you and you like to encourage future presence on this forum
and/or third party plugin/applet development, 'donations are always
appreciated' (http://erland.isaksson.info/donate))
------------------------------------------------------------------------
erland's Profile: http://forums.slimdevices.com/member.php?userid=3124
View this thread: http://forums.slimdevices.com/showthread.php?t=84697
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
