3 ms·

It’s frustration at having to learn more than one programming language. At this time, due to the social integration of technology the number of people who inte

It’s frustration at having to learn more than one programming language. At this time, due to the social integration of technology the number of people who interact with development has far out paced the number of people who enjoy development. > they are much more complimentary If you hate writing code but do it for your job, then you are going to really hate writing code in two different languages with their own syntax and paradigms. Also, nearly all programming language projects want to be the “everything language” so essentially any language is a fine choice and what it really comes down to is the people who enjoy the work develop “tastes” and “preferences” that they treat as dogma when defending their language of choice.

lagniappe 2y ago
> It’s frustration at having to learn more than one programming language. Imagine bob ross with only one color could still make something magnificent, but what could he do with two colors? You can't have Burnt Umber without some Phthalo Green..
- zer00eyz 2y ago
  > Imagine bob ross with only one color could still make something magnificent, but what could he do with two colors? https://www.youtube.com/watch?v=I-ousb8-SD0 https://www.youtube.com/watch?v=I-ousb8-SD0
- okhugres 2y ago
  Due the concept of Turing completeness I’d argue it’s more of deciding which paint brand to use, or if you must, I suppose you could liken it to the distinction between choosing oils or acrylics.
  - Jtsummers 2y ago
    You don't actually understand Turing completeness if that's your takeaway. Turing completeness is about computational equivalence. That, fundamentally, any Turing complete language can perform the same classes of computations as any other. It says nothing about substitutability of one language for another within any other context.
koreth1 2y ago
> If you hate writing code but do it for your job, then you are going to really hate writing code in two different languages with their own syntax and paradigms. I don't wish for this, but sometimes I wonder how different the industry would be today if dev salaries had remained in "respectable but nothing amazing" territory. Maybe it's just nostalgia goggles, but when I was getting started ~35 years ago, I think it was rare to run into someone who hated writing code but did it for their job. There were other much more profitable jobs for people who were looking to be paid as well as possible for work they hated.

lagniappe 2y ago

> It’s frustration at having to learn more than one programming language. Imagine bob ross with only one color could still make something magnificent, but what could he do with two colors? You can't have Burnt Umber without some Phthalo Green..

zer00eyz 2y ago
> Imagine bob ross with only one color could still make something magnificent, but what could he do with two colors? https://www.youtube.com/watch?v=I-ousb8-SD0 https://www.youtube.com/watch?v=I-ousb8-SD0
okhugres 2y ago
Due the concept of Turing completeness I’d argue it’s more of deciding which paint brand to use, or if you must, I suppose you could liken it to the distinction between choosing oils or acrylics.
- Jtsummers 2y ago
  You don't actually understand Turing completeness if that's your takeaway. Turing completeness is about computational equivalence. That, fundamentally, any Turing complete language can perform the same classes of computations as any other. It says nothing about substitutability of one language for another within any other context.

koreth1 2y ago

> If you hate writing code but do it for your job, then you are going to really hate writing code in two different languages with their own syntax and paradigms. I don't wish for this, but sometimes I wonder how different the industry would be today if dev salaries had remained in "respectable but nothing amazing" territory. Maybe it's just nostalgia goggles, but when I was getting started ~35 years ago, I think it was rare to run into someone who hated writing code but did it for their job. There were other much more profitable jobs for people who were looking to be paid as well as possible for work they hated.