2 ms·
An illustrative example of how reasonable short-term and narrow-scope considerations can be really bad in long-term and/or at a larger scope.
by lr1970 5y ago
An illustrative example of how reasonable short-term and narrow-scope considerations can be really bad in long-term and/or at a larger scope.
- nojito 5y agoWhy should he care about other use-cases? It’s not his responsibility to make sure his package is as wide as possible before opensourcing.
- lr1970 5y agoThe problem is not with the Wes' original decision but with the fact that it was never revisited even when pandas took off at much larger scope. Should had been fixed before 1.0 release.
- nojito 5y agoThis belief is quite common in the Opensource space. It’s far easier to criticize than it is to submit a pull request.
- kickopotomus 5y agoIt's like there is some strange belief now that software should be "finished" before a 1.0 version now. When did that start?
- anigbrowl 5y agoI'm glad you posted about this because I didn't know, but my reflexive response was 'well guess that won't work for [project idea], guess I'll roll my own or just use the NumPy version.' I personally don't mind the lack of one-size-fits-all. If Pandas were to be part of the Python Standard Library I think you'd have a stronger argument, since the unspoken premise of a SL is that you can leave for a desert island with only that and your IDE and still get things done.
- minsc__and__boo 5y agoThis assumes that all projects should be built with the larger scope in mind. Sometimes you just need a shovel, not a Bagger 288.
- deleted 5y ago[deleted]