>>One of the things that I hated about using proprietary closed source
>>software was often hitting the binary brick wall and being able to do
>>naught but scratch my head.
> Please give examples.
>>How many times has someone come up to you and asked, "Why does that
>>happen?", and the only thing you can really say (if you're honest) is
>>"Well, I don't rightly know."
> This happens to both CSS and OSS
Sure, but with OSS you have the opportunity to find out for yourself why
it behaves as it does. Frequently just looking through log files does the
trick (OSS apps tend to provide a lot more diagnostic information than CSS
apps, for some reason), but if you need to delve deeper, you can.
Quote:>>This is just another reason why I love LGX and OSS so much. I never have
>>to say this. Everything is there for me to be able to find out as much or
>>as little as I want, even down to examining source code if I were so
> and if you were able.......which you are not....not even close.
Just because you're not capable of doing something doesn't mean nobody
else is. Programming isn't difficult, and the hardest part tends to be
writing the code to begin with. Making small changes to already-written
code isn't difficult, and is often much easier than you'd expect. The
first version of the much-maligned (well, vaguely-maligned) GtkSpell patch
for Pan was a total of 5 or 6 lines IIRC[*], for example.
[*] - the autoconf macro was likely considerably more.
Quote:>>This means if I am having an issue or a problem, I have the resources
>>available to me to be able to find out and even *resolve* it if I have the
>>wherewithal and knowledge to do so.
> Which you don't.....not even close.
You sound bitter about not being particularly bright. Don't worry, there
are plenty of other people capable of taking advantage of the
opportunities presented to them by Free software.
Quote:>>You never really know freedom until you are truly free.
> What you are proposing is like what I used to think when I was a young
So why exactly did you give up thinking?
Quote:> I wanted to be a car mechanic so I could work on and build my own
> muscle cars, big V8s, big tyres and fat exhausts etc.
> Now, of course, I think that is a mugs game. I pay some grease monkey
> to mantain my high tech sporty and stay clean in an office playing
> with computers.
And the "grease monkey" you pay to maintain your car probably thinks
working with computers is a mugs game, as he loves working with cars. And
he gets to work on, tweak, and test drive your wonderful high-tech sporty
car on YOUR dime. Who's the mug now, eh?
Quote:> I do not want to maintain my car, I will pay someone to do it.
I thought we were talking about computers...
Oh, you were using an analogy? But you just implied you work with
computers ("stay clean in an office playing with computers."), yet you
have no interest in actually knowing how they work, how to look "under the
hood" so to speak and identify (and perhaps fix) problems?
So basically you're no good with cars, and no good with computers.
There's plenty more things out there to try, at least. Hope you find
something that clicks with you.