Simon Albrecht <address@hidden> writes:
On 28.09.2016 11:10, Knut Petersen wrote:
There is one problem with people relying on binaries instead of
building and improving lilypond itself: Almost nobody seems to be able to
bisect a problem. It's e.g. amazing to see how long it takes to
track down
the speed problem on Mac OS systems.
You cannot hope that eventually all LilyPond users are going to become
developers as well. I have delved into LilyPond quite deeper than any
average software user would do, I know some of the (scm) source code,
and I have been able to make a few changes to the program. But I do
not have any ambitions to compile LilyPond on my own.
It's not really a matter of ambition. At some point of time getting
behind some problem without the ability of recompiling will feel like
repairing clockwork with sledgehammer and mittens and it becomes
annoying to wait for others to do it instead. Once you are there,
seeing what it takes to recompile yourself might be the less ambitious
option.
Of course it depends on just what platform you usually work with just
how ambitious recompiling LilyPond may end up for you.