These are the traditional advantages of Smalltalk-like systems, and yes, this system is based on Smalltalk. There's a 2014 paper about Bee Smalltalk [1]. There's a Github repo [2]. There are no real docs and minimal comments in source control.
Section 5.3.3 talks about some drawbacks, and there are more in "8. Conclusions" and "9. Future Work."
> Today, Bee is far from finished, yet we know all required functionalities can be implemented. Furthermore, the resulting code is fully object oriented and can take advantage of all the benefits that a high-level environment brings. The main remaining question to be answered is what
is the maximum performance to expect from the system. We believe that the answer to that question will be highly positive, and that we will be able to unravel the mystery very soon.
...
> Current implementation of Bee is more than 10x slower than the hosted environment [...]
So, interesting work in progress, maybe check back later?
Section 5.3.3 talks about some drawbacks, and there are more in "8. Conclusions" and "9. Future Work."
> Today, Bee is far from finished, yet we know all required functionalities can be implemented. Furthermore, the resulting code is fully object oriented and can take advantage of all the benefits that a high-level environment brings. The main remaining question to be answered is what is the maximum performance to expect from the system. We believe that the answer to that question will be highly positive, and that we will be able to unravel the mystery very soon.
...
> Current implementation of Bee is more than 10x slower than the hosted environment [...]
So, interesting work in progress, maybe check back later?
[1] http://esug.org/data/ESUG2014/IWST/Papers/iwst2014_Design%20... [2] https://github.com/aucerna/bee-dmr