1,117,019 = Number of Lines of Open Source code for Flex, BlazeDS, and Tamarin.
200,897 lines in the flex_sdk
218,789 lines in blazeds
353,644 lines in tamarin-central
343,689 lines in tamarin-tracing
That’s 1,117,019 more reasons you can Count on Flex!
“Count on Flex” is a series of blogs about the current state of the Flex ecosystem… by the numbers.
For this post I did a very basic calculation which doesn’t factor out comments and licenses. For the Flex SDK and BlazeDS I used this command:
find . \( -name "*.java" -or -name "*.as" -or -name "*.mxml" -or -name "*.css" \)|xargs wc -l
And for the two Tamarin projects I used this command:
find . \( -name "*.py" -or -name "*.as" -or -name "*.cpp" -or -name "*.h" -or -name "*.es" \)|xargs wc -l
3 Comments
I didn’t think that Tamarin Tracing was in Flex yet, but it’s cool that they’re being that leading edge with the under-development tree. Counting both TT and TC is a little odd, since only one will be used in Flex itself, but you should definitely also count the Forth code — *.fs — in the TT tree!
Hi Mike,
Thanks for the tip about the Forth code. Including the Forth code for Tamarin Tracing I get: 348,620 lines of code.
I debated whether or not to include both TT and TC. Since Adobe hasn’t announced any actual plans for TT yet maybe I should not have included it. But then again, this is code largely contributed by Adobe which will hopefully someday be the basis for a VM for Flex applications somewhere.
-James
Yeah, I hope that it will be in Flex, along with other platforms. But if it is, then tamarin-central won’t be, since they are “competing” efforts (in the ecological sense, not market sense). Were I you, I would count only TC today, since it’s what’s going into the development builds of Flex, and then count only TT if/when it becomes the plan of record for Flex (via Player).