4 ms·

So with infinite resources it would be best to write everything from scratch?

by kreetx 1y ago

whstl 1y ago
This is not a black-or-white situation. There's no need to only go to one extreme or the other.
- kreetx 1y ago
  You have made your normative assessment very clear, but I haven't heard of where and how do you draw the line. EDIT: Can't post any deeper, but the child can see that no such "statements" have been made.
  - the__alchemist 1y ago
    Please re-read his or her replies. I will (re) state it explicitly if you don't see it, but I believe you will find it.
  - the__alchemist 1y ago
    The explicit re-statement: There is no general line to draw of whether to use a dependency, or write code internally using a language's primitives (Or already-used libs); it varies based on the situation, and there is a high degree of subjectivity in each of these choices.
    - kreetx 1y ago
      So what do you subjectively consider when making this choice?
      - the__alchemist 1y ago
        Some examples: - How much work would it take to implement and maintain this if done without a library? - What other libraries are available? - Does this library meet our needs superficially, or will it be a robust solution long-term? - When our requirements change slightly, or we need to add or change features, will this library still work? - How much code architecture needs to change to integrate this? Does it require changing other parts of the program that it seems should not be required to change for the reason we are bringing this in? - What impact does including this have on binary size and compile time? - What is the risk of security vulnerabilities? - Does this library have its own deep dependency tree? - Will this require continuous maintenance to keep it in sync with other dependencies? - Does this library require certain system dependencies to be installed that will make the build more fragile / less portable? - Will using this dependency impact performance over implementing manually? (Or over another dependency)
        kreetx 1y ago
        A good dependency solves a well defined problem with a direct API towards it, so yes, if the dependencies you talk about aren't high quality then yes, don't use those.

So with infinite resources it would be best to write everything from scratch?

by kreetx 1y ago

So with infinite resources it would be best to write everything from scratch?

whstl 1y ago

This is not a black-or-white situation. There's no need to only go to one extreme or the other.

kreetx 1y ago
You have made your normative assessment very clear, but I haven't heard of where and how do you draw the line. EDIT: Can't post any deeper, but the child can see that no such "statements" have been made.
- the__alchemist 1y ago
  Please re-read his or her replies. I will (re) state it explicitly if you don't see it, but I believe you will find it.
- the__alchemist 1y ago
  The explicit re-statement: There is no general line to draw of whether to use a dependency, or write code internally using a language's primitives (Or already-used libs); it varies based on the situation, and there is a high degree of subjectivity in each of these choices.
  - kreetx 1y ago
    So what do you subjectively consider when making this choice?
    - the__alchemist 1y ago
      Some examples: - How much work would it take to implement and maintain this if done without a library? - What other libraries are available? - Does this library meet our needs superficially, or will it be a robust solution long-term? - When our requirements change slightly, or we need to add or change features, will this library still work? - How much code architecture needs to change to integrate this? Does it require changing other parts of the program that it seems should not be required to change for the reason we are bringing this in? - What impact does including this have on binary size and compile time? - What is the risk of security vulnerabilities? - Does this library have its own deep dependency tree? - Will this require continuous maintenance to keep it in sync with other dependencies? - Does this library require certain system dependencies to be installed that will make the build more fragile / less portable? - Will using this dependency impact performance over implementing manually? (Or over another dependency)
      - kreetx 1y ago
        A good dependency solves a well defined problem with a direct API towards it, so yes, if the dependencies you talk about aren't high quality then yes, don't use those.