But a product has a couple of difficulties. One is that there are not robust mechanisms for obfuscating eLisp code. The other is that binary changes would be under GPL and the source would be available to users.
And the ordinary problem that an Emacs product would be competing with free. There's not only good free tooling with almost fifty years of maturity, but also Emacs is about as deep into GPL culture as you can go.
But a product has a couple of difficulties. One is that there are not robust mechanisms for obfuscating eLisp code. The other is that binary changes would be under GPL and the source would be available to users.
And the ordinary problem that an Emacs product would be competing with free. There's not only good free tooling with almost fifty years of maturity, but also Emacs is about as deep into GPL culture as you can go.
You'd almost need to impose Emacs as your companies "blessed" code editor, which, as we know in cases of editors, is extremely hard.
Emacs users are very willing to provide support at no cost. Emacs users are pretty easy to nerd snipe.
You can hire individuals for individual Emacs needs. Such people exist.