3 ms·

Because typescript is optional typing and some libraries don't maintain their own typings, there's a non-zero chance that the typings of a third-party library a

by qudat 4y ago

Because typescript is optional typing and some libraries don't maintain their own typings, there's a non-zero chance that the typings of a third-party library are wrong. In this case the error is noise and not indicative of a runtime error. This is the frustrating part with using a mixed typed ecosystem.

donatj 4y ago
> typings of a third-party library are wrong That's not noise. That is a bug.
- dgb23 4y ago
  It's a TS "bug", not a Deno "bug" though. TS doesn't have a sound type system. It has type annotations on steroids.
  - donatj 4y ago
    It's neither. It's a bug in the library you're trying to use. The library you're trying to use is broken and you shouldn't use it until the problem is fixed.
    - wk_end 4y ago
      It'd be nice if I never had to use software with bugs in it but that's hardly realistic.
    - zackees 4y ago
      “Sorry we can’t use numpy because one of the types in the api is mismatched.”
- cschep 4y ago
  Causing a bunch of pain for the user because of a theoretical thing that should be true doesn't help that thing become more true. I feel like we as a people (programmers) fall for this trap too often. Incentives have to be aligned so perfectly for this kind of thing to work.
- qudat 4y ago
  It's a typing "bug" in code you don't control. In some cases that's enough to not use the library and sometimes it isn't. That's a value judgement based on the developers using the library.
  - SemanticStrengh 4y ago
  - deleted 4y ago
    [deleted]
- hehebdjwis 4y ago
  Whatever you do don’t peek at v8, or the c libraries it links, or the operating system underneath it all…
IshKebab 4y ago
Ok but it should be an opt-in workaround for dependencies' bugs. Tell me if a dependency has an issue, and then let me decide if I want to ignore it. Don't just ignore them all - for one they'll never get fixed.
SemanticStrengh 4y ago
you can always use https://github.com/ds300/patch-package https://github.com/ds300/patch-package there is no excuse for mediocrity, of course you can use any, that just should not be the default behaviour

by qudat 4y ago

donatj 4y ago

> typings of a third-party library are wrong That's not noise. That is a bug.

dgb23 4y ago
It's a TS "bug", not a Deno "bug" though. TS doesn't have a sound type system. It has type annotations on steroids.
- donatj 4y ago
  It's neither. It's a bug in the library you're trying to use. The library you're trying to use is broken and you shouldn't use it until the problem is fixed.
  - wk_end 4y ago
    It'd be nice if I never had to use software with bugs in it but that's hardly realistic.
  - zackees 4y ago
    “Sorry we can’t use numpy because one of the types in the api is mismatched.”
cschep 4y ago
Causing a bunch of pain for the user because of a theoretical thing that should be true doesn't help that thing become more true. I feel like we as a people (programmers) fall for this trap too often. Incentives have to be aligned so perfectly for this kind of thing to work.
qudat 4y ago
It's a typing "bug" in code you don't control. In some cases that's enough to not use the library and sometimes it isn't. That's a value judgement based on the developers using the library.
- SemanticStrengh 4y ago
- deleted 4y ago
  [deleted]
hehebdjwis 4y ago
Whatever you do don’t peek at v8, or the c libraries it links, or the operating system underneath it all…

IshKebab 4y ago

Ok but it should be an opt-in workaround for dependencies' bugs. Tell me if a dependency has an issue, and then let me decide if I want to ignore it. Don't just ignore them all - for one they'll never get fixed.

SemanticStrengh 4y ago

you can always use https://github.com/ds300/patch-package https://github.com/ds300/patch-package there is no excuse for mediocrity, of course you can use any, that just should not be the default behaviour