Mario.

yes pg does very well re accessibility.

All.

i would just like to mention a wrinkle in cleaning up legacy systems and i DO realise lots of pg users want various legacy and other issues fixed....

heres a case study...

once i was called into a very large organisation to manage the renovation and modernisation of a huge legacy system...
the issues were...
...a zillion lines of source code
...lots of hard coded tables which couldnt be updated rapidly as users wanted.
...execs who didnt understand the rea!ities of making changes untill i sat them down with the coders and heard the execs then apologise.
...a massive internal user base of thousands
..a external customer base of more than a million people.
and that was just the start...lol.

in summary a challenge even though the programming team was the best available on the market...brilliant in fact.

now lets look at how the above system came about.
answer was basically a desire in the IT group to keep everyone happy always.
but the problem is a systems group can never achieve nirvana.
its just the nature of the system development beast.
one major issue is often user groups cant agree....for various reasons.
in the above case i often felt like a referee...lol. even with user sign offs still one user group might be happy but another might not.

you still see the same today viz 'everyone wants certain standards as long as its theirs'.

now re pg i suspect the legacy and other things the user base want addressed built up over time...ie pg didnt purposely decide to create problems.
they were just trying to keep all the different user camps happy.
eg maybe one group of users might want feature A but another group
of users might want B.
so things build up over time. the positives being bb has a plethora of features no other music app can match...the negative being sometimes it takes a time to locate bugs.

lets take modernising the gui for example.
some user groups might want the same gui they have got used to.
others want fancy shmancy modern groovy graphics.
other users might want to customise the gui any way they want.
i might like the gui one way but another user might think my way is junk and want another way the gui is presented.

thus its a real challenge for the coders.
the major issue being how do the coders keep everyone happy without ballooning the amount of source code to be maintained.

in the case i first described we had to make very difficult decisions so the system didnt become unable to manage.
this of course teed off some users as they didnt get their needs met.

frankly i feel for pg because keeping all the diverse user camps happy is one heck of a challenge. also a coder group is often limited by the platform and os they are developing for. ive got a few grey hairs to prove it...lol.

do i have bugaboos with bb ?...sure...but haveing been on the developer side of fence i look at what pg have achieved as rather remarkable...warts and all. given the many challenges.
lets look at the glass as half full because where would we all be without the tools provided by pg.
here is a small canadian company that has built a world wide diverse user base.
with this come various challenges at both the technical and the user level.

i know some people get frustrated...but lets also look at the positives
at the same time.

hopefully pg can reach a point of all users being happy...but its incredibly difficult for any tech company to do so.

happinesx to all...

om. 🇨🇦🇨🇦 🇬🇧🇬🇧

Last edited by justanoldmuso; 05/30/24 05:47 PM.
my songs....mixed for good earbuds...(fyi..my vocs on all songs..)
https://soundcloud.com/alfsongs
(90 songs created useing bb/rb)
(lots of tips of mine in pg tips forum.)