I don't think that killer applications written using FPC/Lazarus are that important, because that's what the end user usually comes into contact with. The vast majority of end users don't care what the program was created in. Ergonomics are important to the user. Nevertheless, I think that applications created using FPC/Lazarus should be documented. This will always, to some extent, increase the popularization of FPC/Lazarus.
However, considering that FPC and Lazarus are programming tools, the most effective way to popularize them would be:
- expanding and improving: compiler, debugger and IDE,
- expanding existing libraries and creating new ones,
- expanding and improving documentation regarding: FPC, Lazarus, libraries.
Point
(1) time is being realized (slowly but steadily). Some fixes to the compiler (language pains) should be included. Some of them were mentioned by
440bx, such oddities as writable constants (but there are more). This should “be straightened out” in the language.
Point
(2) is also (generally) realized. But there are fewer libraries compared to, for example, C or C++ (which is obvious - the number of people involved). And this point is one of the more important ones. This is well shown by the popularity of Python - the reason is libraries (even though it is basically the worst programming language, right next to JS). In any case, it seems to me that for most programmers it is probably easier to create libraries than to expand a compiler or debugger.
Point
(3) is also very important. Much of the content in the documentation would need to be improved, supplemented and expanded. In addition, one central repository with documentation would be useful: FPC, Lazarus, libraries (scattering it across several different websites is inconvenient). In addition, many descriptions are incomplete (this has been mentioned many times on this forum). Also the look of these pages and the layout of the content (headers, links, color, size and font style, etc.) is quite archaic. It would be good to refresh this. But those who wanted to do it would have to have access to it.
The FPC and Lazarus website(s) could also use some refreshing. It doesn't always have to involve completely turning everything upside down. Just "a bit" is enough.
I have no major objections to the tutorials. They are quite decent. Besides, creating them is very time-consuming and demanding. But basic documentation of tools and libraries is necessary. Without it, it is difficult to work even for those who already know FPC/Lazarus.
I believe that the first step is to improve, streamline and expand the documentation, starting with the appearance and then moving on to the content (in stages). Yes, I know, it's a lot of work. But without it, the slow "downhill slide" will continue (which I don't think any of us want).