We can discuss a lot about this. However, the problem lies in how developers enforce these rules. When you have 1-2-3 developers with a strict rule of approving all the changes by one another developer, you probably will be able to maintain it. With a big development team and a legacy codebase, it will be mission impossible.

Unless, if we would be able to have linters set in with forced checks in CI, and it would fix some issues on the fly or enforce developer do it. As well as proper Formatter setup in the developer environment (nowadays that would be VSCode), with a bunch of rules defined for the project.

But we don't have any linters (ObjectScriptQuality is quite bulky and may still require some improvements), or good formatters (the one with InterSystems Language Server extension is quite primitive), and no way to build new tools, and especially inject to CI process.

That leads us to the point that our community requires open-source ObjectScript parser that can help developers to build all sorts of tools, such as linters, formatters, and all sorts of scanners of the code. It would even help with AI today, so LLM would better understand our code. Until then, all these discussions are mostly useless.

Can I get a bonus for Community opportunity Idea?

As part of the main project, to proper test across multiple versions of IRIS, I implemented another project and wrote an article about it, with examples from typeorm-iris project

I know that only Python matters nowadays, but what about other languages officially supported by InterSystems?

I found significant bugs in the NodeJS driver, and it is not worth anything.

Javascript support for IRIS is quite limited, and it includes async/await. But you can wrap all IRIS related stuff to promises, and it will work, kind of. There is a lot of work needed to be done on the driver side, to make it powerful in JavaScript.

At the moment, I'm working on TypeORM support for IRIS, the package not published yet, should finish this week. But mostly working, there are some samples provided, all of them working.

Please have a look. I'm looking forward to any feedback, and open to any suggestions about which JS library would need to get IRIS support next

SSL Error for this driver does not really mean it's SSL ERROR, in most cases it could mean, that connection can't be established, from the first step. Check if port really available, you could try it by using some different tools, like DBeaver.

And unfortunately I can't recommend this driver you trying to use, it's unstable. May throw sigfault errors randomly and have other bugs. I would recommend using this driver instead, in most scenarios both are compatible, this one just more stable and predictible. And this driver used by lots of other Python projects, like SQLAlchemy, Django, irissqlcli, and more based on them.