On 13/01/2022 12:35, Alexander Thurgood wrote:
Thanks for jumping in on this thread, and I appreciate you having taken the time to address my points.

        Nice to talk the issues through constructively =)

Oh, yes, I still remember the pain involved in transitioning
from PPC to Intel.

Quite =) Apple seems to deprecates APIs less quickly than Linux but rather more quickly than Windows.

The downside for the commercial offerings then is why would I continue to keep subscribing to the AppStore versions (and contributing financially, however little that might be), if I have to have multiple different versions of what is perceived as the "same" software in order to get work done ?

In a nutshell, if your primary focus is Base on Mac, then at the moment it makes little sense to - except of course that supports the project somewhat. Obviously you could support the project instead by donating to TDF.

Lest there be some misunderstanding, I also wasn't touting that Base be atticised, far from it, that would be counter-productive for me

        Sure; I don't think anyone is proposing that.

particular, my concerns were levelled more at the perceived (by me) risk that apathy, or lack of foresight at the Board level, or whichever circumstances, might lead to the commercially branded offerings of LO in the long run being the only ones available via the AppStore, or indeed anywhere.

My take is that app-stores are a significant strategic risk to TDF from several perspectives and that keeping people's ability to install their own software alive - outside the grip of DRM'd app stores is an important thing to do. Also - the economics of endless free updates in app-stores hurts TDF's revenue very significantly when you model it: not de-funding TDF needs to be a concern for the project.

Endian-ness for embedded Firebird seems to be the elephant in the room here. ODB files made on MacOS can not easily be shared with other OSes/arch.

Oh - wow, I didn't know that. Wow - that is awful. That crushed my hopes for a good Firebird based future.

So what other options are there for a sensibly licensed, in-process database ?

Does PostgreSQL do it - could we run the server in a thread cross-platform, can we get its data into a file ? ;-) I guess we should prolly re-do the analysis of alternatives here to work out if there is a sensible way forward; but that belongs on the dev-list - and it's a big job to even know what we might want to do.

    You certainly highlight an interesting challenge. How can we find individual volunteers and resources to apply to such problems ? More development mentors may help, its worth a try - but I'm sure many more such problems will remain.

Agreed, and I don't believe that there are any easy options, nor do I see any "prepackaged" solutions that will satisfy everyone.

Yep; seems like a nightmare; the endianess issue burst my bubble of having a nice direction - but just getting there slowly. How can we avoid the galloping bit-rot and fund the improvement of a good database infrastructure ? it's an un-solved question.

Thanks again for your input Michael, it is always useful for me to have this kind of engagement.

No problem; Its a shame that the Linux Desktop is not floating your boat too, I agree with you on lots of what you wrote that I excised for brevity.

Anyhow - I'd like to hope that we can research and come up with a plan for a capable database that we can bundle & be sure is always there for embedded db's; one that will not bit-rot, and is not built on another bit-rotting infrastructure =)

I guess with Noel's experience perhaps a J2C++ conversion on HSQLDB would do it ;-) still at 100k LOC of Java that's also a nightmare.

        Hey ho,

                Michael.

--
michael.me...@collabora.com <><, GM Collabora Productivity
Hangout: mejme...@gmail.com, Skype: mmeeks
(M) +44 7795 666 147 - timezone usually UK / Europe

--
To unsubscribe e-mail to: board-discuss+unsubscr...@documentfoundation.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.documentfoundation.org/www/board-discuss/
Privacy Policy: https://www.documentfoundation.org/privacy

Reply via email to