# Red community update: experimental CSV codec, GitHub milestones, and an AI toolkit discussion DevFeed: [Red community update: experimental CSV codec, GitHub milestones, and an AI toolkit discussion]() Original publisher: [Read original article]() Author: Unknown (noreply@blogger.com) Published: 2019-09-15T19:23:00Z Content type: article Language: en Sources: [Red]() Topics: [Red](), [CSV](), [data](), [Code]() Tags: [community](), [experimental](), [format](), [github](), [programming]() ## AI overview A Red community update highlights recent ticket closures, an experimental CSV codec added to nightly builds, Red reaching 4,000 GitHub stars, and a discussion about building an AI toolkit that supports configurable recognition tasks, datasets, and fine-tuning. ## Source excerpt Hello to all the great makers, doers and creative people who are using Red, helping the Red Language grow and improve! As always, there's a standing invitation for you to join us on Gitter, Telegram or Github (if you haven't already) to ask questions and tell us about your Red-powered projects. Here are some recent highlights we'd like to share with you: 1. Tickets Get Priority In the last month, our core team has closed a large number of tickets.We'd like to thank community members rgchris, giesse, and dumblob who are just a few of the passionate contributors putting Red through its paces and providing feedback as fixes and changes occur. @WArP ran the numbers for us, showing a cyclical growth pattern linking bursts of closed issues and some serious Red progress, and September's not even done yet!...: 2. CSV Codec Available Our newly updated CSV codec has been merged in the master branch and is now a part of the nightly (or automatic) build here. It is in an experimental phase, and we want your feedback. Should the standard codec only support block results, so it's as simple as possible? Or do people want and need record and column formats as well (using the load-csv/to-csv helper funcs, rather than load/as)? Including those features as standard means they're always available, rather than moving them to an extended CSV module; but the downside is added size to the base Red binary. Applause goes to @rebolek's excellent organization and his wiki on the codec, which explains the various ways in which Red can represent data matrices. He writes, "Choosing the right format depends on a lot of circumstances, for example, memory usage - column store is more efficient if you have more rows than columns. The bigger the difference, the more efficient." You can judge their efficiency here, where @rebolek has laid out the compile time, size and speed of each version, including encapping and lite. Be sure to get the latest build, and chat with everyone on Gitter to tell us what