The article even points out that raftlib must be statically linked which forces a few kb to be used when the binary is loaded. In a super computer you would have a cluster of many machines and would need to load even dynamic libraries at least once per machine.
Then looking at the raftlib site [1] and their wiki on github [2] it is clear that they have no way to scale to super computers, yet. They do use the terms, like "execution kernels" and talk about abstracting where the execution happens, but the focus seems to be on syntax (which is a thing I suppose).
Looking at the TBB developer guide[3] it seems clear that either would take some custom coding to get working across multiple machines.
It seems clear to me that Raftlib and TBB exist in the same space, targeting the typical app or system coder wanting threads. A much better point to raise if you want to support raftlib would be its focus on syntax, which is often ugly with many threading libraries. But the the raftlib guy thinks his looks good. I won't comment on something so subjective.
[1] http://www.raftlib.io/ [2] https://github.com/RaftLib/RaftLib/wiki/Execution-Model [3] https://software.intel.com/en-us/node/506045