3 ms·
I think "Jargon" would probably have been a much less controversial term than "Dialect" for expressing this idea. "Dialect" implies that it's a sub-language, b
by byroot 5y ago
I think "Jargon" would probably have been a much less controversial term than "Dialect" for expressing this idea.
"Dialect" implies that it's a sub-language, but Ruby is still Ruby no matter how many methods you add or modify.
Whereas a "Jargon" is a specialized vocabulary, and even sometimes some word change meaning as part of a jargon.
But I suppose that when you title your post like this, controversy is actually what you are looking for.
- samatman 5y agoThe non-composability of ActiveSupport-flavored-Ruby with other Ruby code which tries to use the same approach, is the point of the article. It's that which (the author argues) makes it a dialect, rather than a specific jargon.
- byroot 5y agoSome professional Jargon are non-composable too when they use the same words for different meanings.