performance - Writing a large project using J programming language -

disclosure

this "general" question, perhaps without specific answer, not intended flame war. information before embarking on project.

i have implement particular project really benefit data structures , abstractions provided j. large project, meant function central component of large (soft real-time) web application. performance important.

i have been trying find information usage of j in large commercial or open source projects, unable find information on base decision move forward. have:

• searched google trends, received following response: "your terms - j programming language - not have enough search volume show graphs."
• searched on free(code), , not found single project using j
• searched on sourceforge, , not found single project using j
• searched on lambda ultimate, , found following discussion obliquely references apl
• searched on google , bing, , failed find examples of large scale projects in deployment use j

would making mistake in using j project? seems have everything--especially in terms of data structures, abstraction , concision--that want. sure, spend time simulating properties in f#, or c#, or c++, j has them, so...

can please tell me drawbacks of using j (or obscure language) important projects? not sufficiently performant? not have libraries? else should know?

thanks in advance responses.

i think j suitable critical use on large, important projects. think j adventurous choice (read: high-risk) such project.

the 2 good-sized companies i'm aware of use j central technology major software system cognos , luen thai. (cognos has been purchased ibm.) discussion of these systems, or @ least experiences involving them, have shown in j chat forum. there's not information there, however.

there may other big software systems rely on j, i've not identified them (and have been keeping eye out years.)

dmitri chubarov right think difficulty finding appropriately skilled developers significant problem. moreover, think difficult people have not developed significant skill in array language estimate how effort take them become @ programming in j. consider particularly important j learned out of attitude of joyful excitement, , attitude can put @ risk production pressures of software project. (it is possible learn j on job , love it, risk programmer hate because "have to" learn should not ignored.)

another difficulty integration efforts. j has variety of libraries, , has been connected various other software systems, contrast has been accomplished more popular languages dramatic. experience has indicated j interfaces pretty readily, attribute choices how work outside world. (this includes dlls, memory-mapped files, sockets, , text-file scripts.) nevertheless, in large project you'd innovating more usual when making connection surrounding support software.

in mind, biggest factor whether had adequate team undertaking core product. might realistically smaller team "large" projects rely on. array languages have been associated smaller teams typical field, consider among advantages. if have arranged involvement of whatever colleagues you'll need, great. if not, don't commit such project until do.

the next important things knowing expect obtain primary benefits of j, , ways check you're getting benefits move through project. i'm not right person advise how this, sure don't want devote investment capital without keeping track of whether high-risk choice bearing out anticipated rewards.

paul graham has written languages relied on secret advantages. j such language. merely using j, however, not enough assure gives sort of advantages had in mind. described appealing aspects of j suggest such advantage might within reach you. if choose rely on it, vital have major participants have strong, , sober, understanding why language chosen work.