4 ms·

For any large project you need type-safe languages. 99% of experience developers (10+ years of experience) will agree with this opinion. Sure you can develop v

For any large project you need type-safe languages. 99% of experience developers (10+ years of experience) will agree with this opinion. Sure you can develop very large projects in JS, as long as you don't mind being 1% as efficient, and having 100x more bugs. In JS, refactoring a huge project is the biggest nightmare in the world and really no human is capable of doing a great job of it in a reasonable time, even if they have a high IQ and decades of experience.

baobabKoodaa 2y ago
I don't share your opinion but I'm too tired to go into another JS vs TS debate
- quantadev 2y ago
  Me too. lol. People who don't think type-safe languages are important are the ones who simply haven't yet run into the problems you run into without type safety, and no amount of HackerNews posting is going to suddenly give them the experience to understand.
  - baobabKoodaa 2y ago
    "People who disagree with me on the topic of """best language/framework""" are ignorant and lack experience to see how {my_favorite_language} is actually the bestest"
    - quantadev 2y ago
      I literally said the exact opposite. I don't care what language you use as long as it's type-safe. Any language that lacks type-safety is completely inappropriate for large-scale projects. There's no seasoned developer on the planet who disagrees with that sentiment. None. Zilch. If some guy claims to be #1) decades experienced and #2) doesn't like type-safe languages, then he's lying about either #1 or #2 or both.
      - baobabKoodaa 2y ago
        First it was "10+ years experience", which would qualify me, but now you shifted the goalposts again to "decades" experience. Lol. I guess you can keep pretending that everybody who matters agrees with you when you just count everybody who disagrees as someone who doesn't matter
        quantadev 2y ago
        I originally typed "seasoned developer" and then I edited it to say decades. Neither one of us has perfect definition of "seasoned developer" in terms of precise years, and it doesn't even matter. But there are some things that are obvious to any seasoned developer and the value of type-safety is one of them. It's not my opinion. Is a fact. And yes if you say you have 10+ yrs and you don't prefer type-safe languages, then yes I indeed do not even believe you.
        baobabKoodaa 2y ago
        I'm a seasoned developer. Your opinion is just your opinion, not a fact. Have you heard of Python by any chance? Pretty much the entire field of data science is built on top of a dynamically typed language. Plenty more seasoned developers working in that field.
        quantadev 2y ago
        Seasoned Python developers started using every type-safety feature available to them, as they've became available, just like JavaScript developers who know what they're doing have switched to TypeScript for the same exact reason. If Python was just fine without type-safety that's how everyone would have kept it.
        baobabKoodaa 2y ago
        > Seasoned Python developers started using every type-safety feature available to them, as they've became available, just like JavaScript developers who know what they're doing have switched to TypeScript for the same exact reason. This is another lie from you. A vanishingly small minority of Python developers is using "every type-safety feature available to them". Not that it even matters to your earlier claim, because Python is not a type-safe language even for those developers who are using "every type-safety feature available to them". You claimed earlier that "Any language that lacks type-safety is completely inappropriate for large-scale projects" even though you seem to be aware of the fact that "seasoned developers" are using Python for "large-scale projects". So, again, you're just lying.
  - xcrunner529 2y ago
    Awfully funny considering our major security issues in code these days are from a type safe language.
    - quantadev 2y ago
      Yeah because any systems or OS programming is done in type-safe languages. lol. And BTW correlation is not causation.
      - xcrunner529 2y ago
        That was kind of my point. You speak to type safety and all the issues not having is that would be prevented but memory safety is yet another one and is a huge issue with common platforms TODAY. So, obviously your pet issue isn’t the only one out there and there are trade offs made.
        quantadev 2y ago
        Here's how your "point" landed, according to everyone but you: Me: "Seat belts are important." You: "Awfully funny considering our major car accidents these days are mostly all ones with seat belts." You're implying a nonsensical causation that's purely a correlation.
        xcrunner529 2y ago
        My point was how our most serious issues are with memory management that exists in popular type-strict languages and so type safety is not up there in importance compared to the biggest causes.
        quantadev 2y ago
        That's exactly backwards. Without the type-safety in those memory-unsafe languages (like C++) there would be 100x more buffer overruns and other memory issues and security holes. Having the type-safety in place is literally the main thing that makes memory-unsafe languages viable.

baobabKoodaa 2y ago

I don't share your opinion but I'm too tired to go into another JS vs TS debate

quantadev 2y ago
Me too. lol. People who don't think type-safe languages are important are the ones who simply haven't yet run into the problems you run into without type safety, and no amount of HackerNews posting is going to suddenly give them the experience to understand.
- baobabKoodaa 2y ago
  "People who disagree with me on the topic of """best language/framework""" are ignorant and lack experience to see how {my_favorite_language} is actually the bestest"
  - quantadev 2y ago
    I literally said the exact opposite. I don't care what language you use as long as it's type-safe. Any language that lacks type-safety is completely inappropriate for large-scale projects. There's no seasoned developer on the planet who disagrees with that sentiment. None. Zilch. If some guy claims to be #1) decades experienced and #2) doesn't like type-safe languages, then he's lying about either #1 or #2 or both.
    - baobabKoodaa 2y ago
      First it was "10+ years experience", which would qualify me, but now you shifted the goalposts again to "decades" experience. Lol. I guess you can keep pretending that everybody who matters agrees with you when you just count everybody who disagrees as someone who doesn't matter
      - quantadev 2y ago
        I originally typed "seasoned developer" and then I edited it to say decades. Neither one of us has perfect definition of "seasoned developer" in terms of precise years, and it doesn't even matter. But there are some things that are obvious to any seasoned developer and the value of type-safety is one of them. It's not my opinion. Is a fact. And yes if you say you have 10+ yrs and you don't prefer type-safe languages, then yes I indeed do not even believe you.
        baobabKoodaa 2y ago
        I'm a seasoned developer. Your opinion is just your opinion, not a fact. Have you heard of Python by any chance? Pretty much the entire field of data science is built on top of a dynamically typed language. Plenty more seasoned developers working in that field.
        quantadev 2y ago
        Seasoned Python developers started using every type-safety feature available to them, as they've became available, just like JavaScript developers who know what they're doing have switched to TypeScript for the same exact reason. If Python was just fine without type-safety that's how everyone would have kept it.
        baobabKoodaa 2y ago
        > Seasoned Python developers started using every type-safety feature available to them, as they've became available, just like JavaScript developers who know what they're doing have switched to TypeScript for the same exact reason. This is another lie from you. A vanishingly small minority of Python developers is using "every type-safety feature available to them". Not that it even matters to your earlier claim, because Python is not a type-safe language even for those developers who are using "every type-safety feature available to them". You claimed earlier that "Any language that lacks type-safety is completely inappropriate for large-scale projects" even though you seem to be aware of the fact that "seasoned developers" are using Python for "large-scale projects". So, again, you're just lying.
- xcrunner529 2y ago
  Awfully funny considering our major security issues in code these days are from a type safe language.
  - quantadev 2y ago
    Yeah because any systems or OS programming is done in type-safe languages. lol. And BTW correlation is not causation.
    - xcrunner529 2y ago
      That was kind of my point. You speak to type safety and all the issues not having is that would be prevented but memory safety is yet another one and is a huge issue with common platforms TODAY. So, obviously your pet issue isn’t the only one out there and there are trade offs made.
      - quantadev 2y ago
        Here's how your "point" landed, according to everyone but you: Me: "Seat belts are important." You: "Awfully funny considering our major car accidents these days are mostly all ones with seat belts." You're implying a nonsensical causation that's purely a correlation.
        xcrunner529 2y ago
        My point was how our most serious issues are with memory management that exists in popular type-strict languages and so type safety is not up there in importance compared to the biggest causes.
        quantadev 2y ago
        That's exactly backwards. Without the type-safety in those memory-unsafe languages (like C++) there would be 100x more buffer overruns and other memory issues and security holes. Having the type-safety in place is literally the main thing that makes memory-unsafe languages viable.