I've been following them for a while. The community communication has lot's of room for improvement. For example the mailing list is down for over an year. The

I've been following them for a while. The community communication has lot's of room for improvement. For example the mailing list is down for over an year. The website is not really updated. All communications happens p2p over eMail or is not logged like the IRC. This is frustrating. Their roadmap did not work out because no plan survives contact with the enemy. From what i gathered J4 and J64 were targets in which there was not so much interest. (The customer demand was for J1 and even smaller ones from fabs who want to add it to their library.) They actually made it past J2 since J1 is available here https://github.com/cr1901/jcore-j1 https://github.com/cr1901/jcore-j1 . Note: this is hosted by a community member not J-Core itself. The past development model seem to have been: Develop solution in house for client at SE-Instruments, ask if they can open source it later. There was a push on #j-core on Freenode for a new source release last week but nothing has materialized yet.