I have to say I sympathize with Lazarus developers for a reason. People who write programs are developers. They are supposed to be capable of reading documentation, following the steps and testing the results properly.
If things don't work they are supposed to document the findings and report the results back to the original developers to see if there are bugs in the system or the documentation is incorrect or incomplete.
I really can't sympathize with programmers who say things are difficult to install. There are always people out there who can help.
What I have to admit about FPC/Lazarus is that it is hard for a newcomer to get a bird's eye view of how it all hangs together. It is difficult to know who is in charge of his or that or who is in charge of what area. It doesn't seem to have taken shape well enough to be broken down into clearly defined parts which can be assigned to leaders and different groups.
I for one seeing how the whole setup looks like, just need the information on how to compile everything from scratch, from FPC to Lazarus. Once I know that I can carry on from there.
Currently I am even afraid to add new components and not even sure how to add libraries in case I break my existing setup, and
It just ain't right.
A Software developer is like a builder. He doesn't need the architect to layout in detail the steps needed for construction, he only needs the plans. FPC/Lazarus leading developers should produce a
single detailed document on how it all fits together, or how it is meant to. Once that is clear the community should be able to do the rest.
If such a already document exists, just point me/us to it. We can then all contribute to it, each in his own little way. The FPC/Lazarus community needs a
webchick of its own. (Males not need apply)