Hey guys, It recently came to my attention (a week ago) that JackDanielZ is writing a JSON parser to go into the EFL. I've been arguing against it on IRC, but I think it's time to post it here.
Although most of us (some more than others) suffer from a severe case of NIH, I think this is really going one step too far. Sure, a JSON parser is easy to implement and is sub 1000 lines of codes. That on it's own is not a good enough reason to get it in. We already have enough code to maintain. We always complain that we don't have enough people to do X and Y. The reason for that is we insist or adding more code we need to maintain instead of using one of the many available solutions. There are: json-c, yajl and jansson to name a few. It's crazy to re-implement it. We'll have to test it on our own, maintain it, document it, debug it and other kinds of unwanted extra work. Together we can stop this madness. Just send "NOMOREDUP" to 1212 to donate £5 to the effort. Hm... I meant, just reply to this email and voice your opinion. No more useless code duplication. -- Tom. ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
