BEE provides dual syntax: BEE Script and BEE Tag.  You can mix BEE Tags with HTML Tags seamlessly (e.g. <beeif if="{status%database}"><p>${message%database}</p></beeif>).  All arguments are in name=value pair.  Missing or excessive arguments will not hurt.  This design makes function calls flexible and adaptable to changes.

BEE Scripts is more programmer friendly than BEE Tags, and therefore more often used (e.g. <script language="bee"> if ({status%database}) display "<p>{message%database}</p>"; </script>).  However, the system runs natively on BEE Tags.  In fact, BEE scripts are preprocessed into BEE Tags internally before compilation so as not to impose any performance penalty at run-time.

BEE Tags function calls look very similar to HTML Tags.  For example, <beemyfunc a=1 b=2>.  In BEE Script, the same would become: myfunc a=1 b=2;.  Inside the function, you can access the arguments through the arg% class (e.g. arg%a and arg%b in the example).

You can call remode functions via "connectors".  This is very useful when you want to access the backend without refreshing the page.  For example, if the user select a brand, you can call a remote functions to retrieve all product codes under that brand and present them as a pick list, without submitting or refreshing the web page.

BEE can talk to PHP (currently BEE's implementation language), JavaScript, HTML and XML.  BEE also provides full socket support and can perform web service call via the soap% and xml% object in the library (experimental).