2 Nov
2016
2 Nov
'16
5:29 p.m.
On Wed, 2 Nov 2016 17:19:01 +0100
Louigi Verona <louigi.verona(a)gmail.com> wrote:
I disagree that reading someone's code is a good
way to educate
yourself.
Another good way to learn is to go work for a company.
... In which case it will be very likely that browsing through the
existing code will be done. One does not want necessarily to do
things very differently. And if one chooses to do so, it will be
because browsing through the existing code was done and observations
were noted.
So, I disagree that you need open source projects to
learn. What you
need is a community, not open sourced programs.
Yes, although I remember when I did not know about Linux and was
working in Windows with MSDN documentation and just about no working
source code. Sure, you it is possible to learn everything, but there's
also an aspect of time and getting things done. And, not reinventing
the wheel. If it's already done, and done in a good way, which ignore
it and spend the time doing it again to possibly have only a slight
optimization if any at all ?
In this regard, having working., from-the-field source code is
beneficial. Now, this is not specifically linked to Open Source
perhaps, but as the name implies, Open Source is... access to code.
If I may be perceived as being not for Open Source, this is not
correct. I am for Open Source. What I have something about, is
following Phil's statement in the magazine for the reasons a musician
would use Open Source, as it was mentioned at the beginning of this
thread.
Still looking for a good reason why a *musician* would use Linux .... :)