As much as one can use a given style for a personal project so can one for a professional one so long as it fills the given need. Too often (in my view) fungibility is seen as a preeminent requirement and layers and layers of self justifying processes are built on top of that. I’m only saying that’s a choice and the costs and benefits are not as obvious as most suppose.

Also you can minimize risks with redundancy but most presume those costs to be too high. But again this quickly becomes about politics.

But for the loss of control you get stuff like fancy SIMD implementation for nothing.

All and all there’s a cost/benefit calculation but that ratio can get quite low.

I think most sizable stuff is proprietary. I implemented an lsp in an open source K which uses json/rpc. But the open source K is probably best considered a hobby project.

https://github.com/gitonthescene/ngnk-lsp/blob/kpath/k/lsp.k

You might consider joining one of the APL forums if you haven’t already.

The expansion is mechanical and thus not really at attempt at readability.