Potential users

Hi all, I want to philosofize a bit about Nim and its potential users, 
use-cases, and user-growth. First of all I want to distinguish some groups 
important to Nim. I see 5 (+1) major groups being: Nim's core-developpers, 
lib-developpers (=semi-users; hybrids of developpers and users), end-users 
(which are application-programmers or device-system-service programmers), 
maintainers and promotors (=5). Of course many people have multiple roles.

As a separate group I mention the (+1 group): consumers of Nim-programs. When 
there are many consumers of a Nim-program it creates confidence/status for the 
underlying programming-language, and is thereby inviting more users.

Concerning consumers again I distinguish pff between end-consumers and 
company-consumers. In case of a popular end-consumer-Nim-app its positive 
influence is clear. In case of an invisible device-system-service it is not so 
clear to the consumer, but it is to the company who creates the device and 
thereby becomes also a bit of consumer of the Nim-program. And finally there 
are tooling-apps for companies. Still folowin?

To accomodate growth one has to service all these groups. Of course in earlier 
phases -besides the core-devs- the lib-devs are very important. Without libs, 
it is harder or even impossible to create specialized apps. The current major 
challenge in lib-land are the GUI-libs. The GUI-libs are important for some 
end-users and consumers because they have all these nice colors and cool 
widgets, and sometimes even sounds that are attractive. The more you get to the 
end-consumer-side the more flashy and fun it has to be. Or would fun-ctional 
would be better?

I thought I would shed some light on user-growth but it is all more complicated 
than I anticipated. But that's true of most things isnt it? 

Reply via email to