7 ms·

> How about both? Because the "issues" with type hinting that you are talking about are only based on what you wished it was, not on what it is or what it coul

> How about both? Because the "issues" with type hinting that you are talking about are only based on what you wished it was, not on what it is or what it could become! Ask yourself this: what about the python's type hinting story you think could be improved without turning python into a statically typed language? What about the python's type checking story that is missing or broken and that is attributable to the language and not to the tool? > I suppose you're more interested in the article's topic. Quite frankly, no. My motivation for the conversation now is mostly to see how long is going to take you to realize that you are merely wishing that your motorboat could fly like a hydroplane. It's not about "misconceptions", it's about you complaining about something not meeting your unfounded expectations .

the_af 5y ago
> "Quite frankly, no. My motivation for the conversation now is mostly to see how long is going to take you to realize [...]" Oh, I see. Well, I have no interest in that kind of conversation. Goodbye.
- rglullis 5y ago
  Please don't read it as snark. It was not my intention. What I am trying to say is that perhaps the lesson you could take from this it's to not think that something is "inferior" or "needs fixing" just because it doesn't immediately meet your expectations. It isn't Python's fault that you have to use at the job even though you don't like it. It isn't Python's fault that you have to use even though you are absolutely certain that dynamically typed languages are worse. It isn't Python's fault that type hints are just hints and can not become a full-fledged type system. It isn't Python's fault that mypy is still not mature enough to work reliably for you. And it certainly isn't Python's fault that your coworkers don't care about all that as much as you do.
  - the_af 5y ago
    > "What I am trying to say is that perhaps the lesson you could take" I think there's a lesson here, but it's for you rather than me. This is tiring. You keep making stuff up for the sake of argument. I never claimed I didn't like Python; in fact I like it. I never claimed it was Python's fault. I thought you were going to "wait until I realize". Go on waiting, then. Off you go!
    - rglullis 5y ago
      I am sorry for my assumption, I just wouldn't think that someone so certain of the superiority of statically typed languages and so disappointed (with a feature that is barely a defining aspect of it) would also claim to like it. Anyway, you also had the chance to respond to other questions I made, but instead you preferred to stick to defensive retorts.
      - the_af 5y ago
        Your questions weren't very reasonable, were they? You made lots of claims about what you supposed I thought. I'm under no obligation to answer, for example, what "my company and team are optimizing for", that's an open ended question which is not reasonable to ask in this context, nor would it benefit me to answer it in any way, nor is it related to the question at hand. It looks like cross-examination, something explicitly discouraged by HN guidelines. I'm not interested in being "educated". In general, you sound very condescending regardless of your claims that you are not snarky. It's easier to pick on someone's comments than to make a comment of your own, because that would open you to correction and criticism. I think that's what's going on with you in this case. Regardless, I suggest you stick to commenting about TFA in the future. It will go better for you. You'll be criticized, but that's par for the course.
        rglullis 5y ago
        I don't see what is unreasonable about prodding for the "why" of the reasons you gave (which was basically the point of asking what your company wanted to optimize by using Python), and I don't see what is unreasonable about asking what would be your way to solving what "disappoints" you about the typing story without changing the language. > I'm not interested in being "educated" by knowitalls. From where I am standing, you are trying to get your coworkers to adopt some practice without a strong case for how it would help them or the bottomline, purely out of your belief that statically languages are better. If you think I am being the know-it-all here, fine. > It's easier to pick on someone's comments than to make a comment of your own, because that would open you to correction and criticism. Someone else in the thread already pointed out that your original comment and TFA are basically a statement of opinion, not of fact. I do not see what kind of comment we can have except the meta-commentary.

the_af 5y ago

> "Quite frankly, no. My motivation for the conversation now is mostly to see how long is going to take you to realize [...]" Oh, I see. Well, I have no interest in that kind of conversation. Goodbye.

rglullis 5y ago
Please don't read it as snark. It was not my intention. What I am trying to say is that perhaps the lesson you could take from this it's to not think that something is "inferior" or "needs fixing" just because it doesn't immediately meet your expectations. It isn't Python's fault that you have to use at the job even though you don't like it. It isn't Python's fault that you have to use even though you are absolutely certain that dynamically typed languages are worse. It isn't Python's fault that type hints are just hints and can not become a full-fledged type system. It isn't Python's fault that mypy is still not mature enough to work reliably for you. And it certainly isn't Python's fault that your coworkers don't care about all that as much as you do.
- the_af 5y ago
  > "What I am trying to say is that perhaps the lesson you could take" I think there's a lesson here, but it's for you rather than me. This is tiring. You keep making stuff up for the sake of argument. I never claimed I didn't like Python; in fact I like it. I never claimed it was Python's fault. I thought you were going to "wait until I realize". Go on waiting, then. Off you go!
  - rglullis 5y ago
    I am sorry for my assumption, I just wouldn't think that someone so certain of the superiority of statically typed languages and so disappointed (with a feature that is barely a defining aspect of it) would also claim to like it. Anyway, you also had the chance to respond to other questions I made, but instead you preferred to stick to defensive retorts.
    - the_af 5y ago
      Your questions weren't very reasonable, were they? You made lots of claims about what you supposed I thought. I'm under no obligation to answer, for example, what "my company and team are optimizing for", that's an open ended question which is not reasonable to ask in this context, nor would it benefit me to answer it in any way, nor is it related to the question at hand. It looks like cross-examination, something explicitly discouraged by HN guidelines. I'm not interested in being "educated". In general, you sound very condescending regardless of your claims that you are not snarky. It's easier to pick on someone's comments than to make a comment of your own, because that would open you to correction and criticism. I think that's what's going on with you in this case. Regardless, I suggest you stick to commenting about TFA in the future. It will go better for you. You'll be criticized, but that's par for the course.
      - rglullis 5y ago
        I don't see what is unreasonable about prodding for the "why" of the reasons you gave (which was basically the point of asking what your company wanted to optimize by using Python), and I don't see what is unreasonable about asking what would be your way to solving what "disappoints" you about the typing story without changing the language. > I'm not interested in being "educated" by knowitalls. From where I am standing, you are trying to get your coworkers to adopt some practice without a strong case for how it would help them or the bottomline, purely out of your belief that statically languages are better. If you think I am being the know-it-all here, fine. > It's easier to pick on someone's comments than to make a comment of your own, because that would open you to correction and criticism. Someone else in the thread already pointed out that your original comment and TFA are basically a statement of opinion, not of fact. I do not see what kind of comment we can have except the meta-commentary.