Bean Nuts refers to the Bean Nuts Projects and its Bean's Nuts Namespace Nomenclature for systemic naming of all his private projects, this project, for its purpose is to create a prototype runtime framework for a specific language (e.g. C/C++), and use this prototype to recursively bootstrap other libraries and functions, then those functions will also become one of this framework. This idea has a long history is set up when he was 10 years old, initiating with his private templated code-set, for help he fast creates VB and VC-MFC programs and also for fun, and apply all those functions to other programs like SCM. Then during his college period, he uses systemic object-oriented methods to package and extend his code-set to those frameworks for different languages, some ancient languages have been dropped (e.g. VB, ActionScript, PHP, etc.), and some are extended.

The Nuts have many nuts (aka. the root of the subbranch), and each Nut also includes many subbranches, all subbranches are derived from the kingpin (aka. the archetype) nut, which the kingpin is dominant and rapacious, its purpose is maximizing to pursue versatility, the kingpin of all nuts is the Pinecone, which has the philosophy that each Nut comes from Pinecone and returns to Pinecone, which for those branches, including Pinecone (Framework), Hazelnut (Profiling Algorithms), Almond (Formal Language), etc. for more details see in Nuts Family. Also, He pursues unity and aesthetics, so that each Nut it can see as his child, and it has its exclusive application domain, name (They are named by enriched background and connotation.), story, and heraldry (Medieval Style Logo, which is designed by myself, see in figure->).

Writing documents is literally killing me, there are some open projects only for fun, and others may be added depending on my mood. Pinecone Draco CPP | Hazelnut Sauron | Pinecone Ursus Java/JS | Walnut Ulfheðinn | Cashew RedNest