8 ms·
How is using a language that is buggy, inconsistent, and incomplete any better than use a better language to write an app that is buggy, inconsistent, and incom
by pc86 2y ago
How is using a language that is buggy, inconsistent, and incomplete any better than use a better language to write an app that is buggy, inconsistent, and incomplete?
Checkmate.
- jbs789 2y agoUmm if we are looking for analogies. I would prefer a castle built on rock rather than one built on sand.
- PhilipRoman 2y agoBetter than a sandcastle built on a rock, I suppose...
- TeMPOraL 2y ago> rather than one built on sand Well, that is exactly what your app is if it's built on modern "state of the art" tooling - you're probably pulling in a thousand trivial dependencies; every day, something gets updated, and you're rolling dice on whether or not your program will build. Writing your own language to build your app in creates a lot of big problems, but not those particular problems.
- AnimalMuppet 2y agoYes, my apps are buggy, inconsistent, and incomplete (as are all apps). But they're less bad than my language would be, because they're my day job, and my language wouldn't be. So, not checkmate at all.
- anta40 2y agoDifferent context, though. I'm pretty sure that my Java/Go/Kotlin apps are buggy. So what, bugs are always exist. Just fix them. But as a language user, it's not my job to fix compiler/RTL library bugs. Write a bug report on GitHub, instead. But when you are designing a programming language and writing the interpreter/compiler, well you are on your own :D