What is discouraged when dealing with domain-specific scripting?

Using explicit references to sys_domain_path is discouraged in domain-specific scripting because it can lead to code that is less flexible and maintainable. When scripts are tightly coupled to a specific domain path, they become harder to adapt to changes in the domain structure or when the script needs to work across multiple domains. This explicit dependence can create issues if the domain structure changes or if you need to apply the script in a different context where the domain paths vary.

In domain-specific scripting, it is generally preferred to use more abstract or generalized methods to access domain data. This approach allows the scripting to be more dynamic, making it easier to maintain and adjust as the environment evolves. It also reduces the risk of hard-coded dependencies that can break the functionality if a domain structure is altered.

The focus of best practices in domain-specific scripting is often on creating reusable, adaptable code that can function across different domains without direct references to specific paths, thereby promoting better software design principles.