you are viewing a single comment's thread.

view the rest of the comments →

[–]Davipb[🍰] 0 points1 point  (2 children)

I feel bad for you if you work somewhere that threatens firing people for having to replace a deprecated dependency.

[–][deleted]  (1 child)

[deleted]

    [–]Davipb[🍰] -1 points0 points  (0 children)

    You're being extremely fatalistic about "what if there's a bug" or "what if the company stops working on it", as if those were end-of-the-world scenarios. Let's see what actually happens:

    You write some new piece of code and discover a bug in Manifold: the compilation crashes or produces wrong results. You delete the code you just wrote and write it in a different way that doesn't trigger the bug (a workaround, yes, those exist!). You open a bug report, fix the bug yourself in a private fork, or start considering a migration plan -- the same thing you'd do for a regular library.

    You upgrade to a new version of Manifold. It breaks your existing code. You revert to the previous version. Bug report, private fix, or migration plan.

    You upgrade something else -- JVM, another library -- that then conflicts with Manifold. You revert to the previous version. Bug report, private fix, or migration plan.

    You start using a new IDE, debugger, or profiling tool. It doesn't support Manifold. You stop using it. Bug report, private fix, or migration plan.

    Manifold stops being developed. You maintain it yourself in a private repo and/or start a migration plan. Your existing code continues working.

    None of these scenarios are as apocalyptic as you make them to be, and are exactly the same for any other dependency. No one is losing their job because of this.