This is a last-ditch attempt to keep the original MuleSoft product relevant. DataWeave is XSLT with shittier tooling. Take a look at Stylus Studio's XSLT mapper

This is a last-ditch attempt to keep the original MuleSoft product relevant. DataWeave is XSLT with shittier tooling. Take a look at Stylus Studio's XSLT mapper and compare it with the mapping functions of Studio. Oracle did this 20 years ago. https://www.stylusstudio.com/images/screenshots/xslt_function_block.gif https://www.stylusstudio.com/images/screenshots/xslt_functio... It's 1-1. Anyone who's used this knows there's much better options for this tooling native to actual programming languages, or datatype specific tooling (eg XPath visualizers). Let's face it, 99% of the work isn't the actual mapping of data, it's building out the definitions and understanding which definition from source to target needs to be mapped. This tooling doesn't address that problem. I'd pick VS Code, Visual Studio or JetBrains "code previews" (where it auto-compiles and gives you expected outputs of variables as you write it) over some bespoke data mapping language any day. You can't hire developers to understand and build these mappings, you're better off hiring developers who understand literally ANY programming language. And don't get me started on performance. Tuning this is impossible outside of throwing more CPU at the problem. Also.. If it's open, where is it?