Title made me think this would be about macro languages causing tech debt after providing quick wins in the early stages of a startup. I should know, we still have > 20 year old load-bearing m4 macros in our web build.
20 year old load-bearing m4 tends to be less of a technical debt than 20 year old load-bearing Java - because it keeps working and doesn’t need constant maintenance.