CentOS Death in 2021

Pi Digital sean at pidigital.co.uk
Tue Dec 15 23:14:22 EST 2020


It’s this kind of rhetoric that drive me to madness and then getting a used of being abusive as I defend what I’ve said.  Richard, there is no need as you have clearly misinterpreted practically everything I said in an effort to get some kind of oneupmanship. 

>> On 16 Dec 2020, at 01:00, Richard Gaskin via use-livecode <use-livecode at lists.runrev.com> wrote:
>> 
>> Pi Digital wrote:
>> 
>> But that does not seem to correlate to the way it is for MacOS or Win.
>> Are you saying they compile from all of those versions of MacOS and
>> Win they reference to supporting.
> 
> Mac and Windows are each made by a single organization, with specs defining compatibility.
> 
> "Linux" isn't an OS per se, it's a family of OSes, where the one thing they all have in common is some form of the Linux kernel.

Show Quoted Content
>> On 16 Dec 2020, at 01:00, Richard Gaskin via use-livecode <use-livecode at lists.runrev.com> wrote:
>> 
>> Pi Digital wrote:
>> 
>> But that does not seem to correlate to the way it is for MacOS or Win.
>> Are you saying they compile from all of those versions of MacOS and
>> Win they reference to supporting.
> 
> Mac and Windows are each made by a single organization, with specs defining compatibility.
> 
> "Linux" isn't an OS per se, it's a family of OSes, where the one thing they all have in common is some form of the Linux kernel.

Debian is Debian. Ubuntu is Ubuntu. Red hat is red hat. Blah blah. This is not my issue. Get the net. 

>> When reading about LiveCode support, to me it doesn’t matter if it
>> is LC Ltd or the LC app. The two are pretty much interchangeable.
> 
> One is a business, the other is a technology stack. The difference may not matter to you, but it matters to them, and understandably so...
> 
Point entirely missed! We are wholly talking about its mention in the release notes and that the ambiguation is not made evident and can ONLY be understood in the context of a release note under the heading of OS support that it refers to the support by the software of a given OS. Sheesh, I’m surprised I have to spell this out to you. Why do you pick on me as if, in this instance, I am trying to criticise LC (Ltd) in any way. 

> 
>> ...the release notes are written SPECIFICALLY for LC the product, not
>> in reference to the company.
> 
> Clearly I agree that the wording in the Release Notes can too easily give that impression, which is why I submitted the enhancement request to clarify it:
> https://quality.livecode.com/show_bug.cgi?id=23035
> 
> 
>> I cannot see where this inference is coming from.
> 
> It is not an inference. I'm familiar with qualifiers like "might be", and use them liberally. I did not use a qualifier here, because in this case I'm drawing from direct conversation with a key member of the core team.
> 
> The explanation I conveyed to you was given to me a while back by Dr Peter Brett in one of my ongoing Community Liaison meetings I have with the company.

Show Quoted Content
> 
>> ...the release notes are written SPECIFICALLY for LC the product, not
>> in reference to the company.
> 
> Clearly I agree that the wording in the Release Notes can too easily give that impression, which is why I submitted the enhancement request to clarify it:
> https://quality.livecode.com/show_bug.cgi?id=23035
> 
> 
>> I cannot see where this inference is coming from.
> 
> It is not an inference. I'm familiar with qualifiers like "might be", and use them liberally. I did not use a qualifier here, because in this case I'm drawing from direct conversation with a key member of the core team.
> 
> The explanation I conveyed to you was given to me a while back by Dr Peter Brett in one of my ongoing Community Liaison meetings I have with the company.

PB hasn’t worked there in a while so I’m guessing that conversation has disappeared into obscurity. 
> 
> This is why I wrote: "...cited Mark Weider. He and I have each had
> conversations with the core team on this, and what he wrote is correct."
> 
> I have no reason to make this up.  When I take time to write to you it's because I'm doing my best to provide you with the best information I have

Misunderstood as it is. 

> 
>> Basically put, if they can’t build it in, for example, Ubuntu 20, then
>> it is not supported fully because of some minor/major issue.
> 
> Have you considered the possibility that not everything in the build system is made in LiveCode?

I know all this so yes it’s not only considered but fully appreciated. This is not a complaint. It’s a situation I find myself facing with legitimate questions around what I should do best case for the future. 
> 
> Funny thing is, those of us who use LiveCode on Linux daily are the least bothered by these support commitment things.
> 
> Let our experience be of help where it can: LiveCode runs well on Ubuntu 18.04 and Ubuntu 20.04, with the exceptions Panos noted earlier.
And PDF rendering as I noted earlier, which is my main concern along with security of up to date code and capability of being supported by my remote server host in some years time. 

What of Fedora and Debian? These are my other concerns.  

Please stop picking on me and using semantics against me. It’s not helpful. And does not do my mental health (as an autistic, BPD, manic depressive, suicide watched, paranoid schizophrenic) any good by treating me with such barrages so you can later go on the defensive and point the finger back at me for asking reasonable questions. [Head meet wall]


More information about the use-livecode mailing list