fine, very fine, a new/better fb-terminal is a good thing; still i wonder if this thing couldn't embed itself into a bash-process and serve tui frames with a s

fine, very fine, a new/better fb-terminal is a good thing; still i wonder if this thing couldn't embed itself into a bash-process and serve tui frames with a scriptable curses api so that you could, for ex, have some tabs and buttons and graphs on a system status app it could bring inversion of control to node and any kind repl .. so that instead of away from a term-info and term-cap standard, one would move toward curses as an acessible tui/gui metaphor, or at least toward something that makes sense without constant apologies for the past. maybe i'm not using the right words, but it seems to me that hacking this up so it can be stuck into bash so that its api appears like any other language extension would make notcurses a highly desirable dependency for just about any project!