4 ms·
And it is, I use that argument regularly when people want to spin up a new project in a new language when the tooling doesn't support the new language and it's
by kuchenbecker 3y ago
And it is, I use that argument regularly when people want to spin up a new project in a new language when the tooling doesn't support the new language and it's an uphill battle to make it work.
- wavemode 3y agoNo, "lack of good tooling" is a completely different argument. The argument put forth by the comment I replied to is that there is basically no point learning a new language, because to work with existing code you still have to know the old language. Which I think is a massive fallacy. Yes, Kotlin programmers still have to understand Java to be effective. That doesn't make Kotlin useless.
- theamk 3y agoShell is pretty special though - it is a very frequent secondary language. In fact, even Kotlin itself uses bash: https://github.com/JetBrains/kotlin/blob/master/scripts/build-kotlin-maven.sh https://github.com/JetBrains/kotlin/blob/master/scripts/buil... So sure, replace Java with Kotlin, C++ with Rust, Python with go/julia/ruby/whatever.. but bash or sh is here to stay. (And that would be bash or sh, not fish or nushell or something...)