3 ms·
Thank you for clarifying, I don't think I'm entirely convinced though, a language can be both easy to read and provide a way to avoid that larger code-bases tur
by dusted 4y ago
Thank you for clarifying, I don't think I'm entirely convinced though, a language can be both easy to read and provide a way to avoid that larger code-bases turn into spaghetti.
I don't think there needs to be any tradeoff in the language itself for this. There will be tradeoffs in the complexity of programs to avoid it, but that seems to be true no matter the language.
Of course, the languages that are both easy to get started with, and at the same time, powerful enough for large systems to be written, result in a lot of very terrible programs, not because they are _bad_languages_(tm) but because they're a perfect balance between ease-of-use, flexibility and power to expand.
- valenterry 4y ago> a language can be both easy to read and provide a way to avoid that larger code-bases turn into spaghetti. "easy" is always relative, so compared to what? Compared to a language that isn't well crafted? Sure. And in practice, most languages could be optimized a lot. But that is not what I was talking about and thinking like that only distracts you from the bigger picture.