3 ms·

This is really very fascinating and I'm looking forward to testing it out. Question for the author: I'm a firm believer that, the more a tool is really good at

This is really very fascinating and I'm looking forward to testing it out. Question for the author: I'm a firm believer that, the more a tool is really good at some things, the more that tool is not good for other things. (A really good drill is also really not good at being a hammer.) It looks like Cell is really new and interesting and does some things really well; what things does it not do really well, or would you recommend to not use it for (as compared to other frameworks?)

gliechtenstein 9y ago
Thanks! I'll be honest, cell is only a couple of days old, and I myself can't say what The best practices are. And this is by design because the goal was to create complexity out of simplicity. I believe this bottom up approach can be much more scalable in the long run than some frameworks that dictate every single detail you need to implement, because all organisms are basically built that way (cells make up body) and they seem to be working fine. Personally the more I use this the more I find creative ways of using it, which is the beauty. But I also do realize sometimes it's good to have some sort of "best practice" structure and I think people will figure it out eventually. TLDR: I think you should be able to build all kinds of sophisticated apps with it because I believe emergence is the best way to construct something. if that's not the case, that doesn't mean the framework is a failure but just needs some tuning, which I believe is totally possible just because the library is so minimal. So please feel free to play with it and share if you run into trouble, we can evolve cell just like cells evolve in the real world.