Next Version Updates #317
Unanswered
coreybutler
asked this question in
Ideas
Replies: 1 comment
-
Some of the other features of this library (sudo, taskkill, etc) may be extracted into another separate library if there is enough interest. Feel free to voice your interest here by upvoting this comment. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In response to #308, I've reviewed the code pretty extensively. It's... old. I've also reviewed node-mac and node-linux, which are also pretty old code bases. These code bases will continue to work, but I believe there is a better approach.
This library is based on winsw, whereas node-mac directly accesses the OS daemon manager. node-linux only supports systemv (not systemd). The main challenge in maintaining a consistent API is the fact each of these approaches are considerably different... not to mention maintaining 3 repos is getting pretty tired.
At this point, I believe it would be better to abstract the wrapper functionality (i.e. complexity) out of JavaScript and bundle it within the executable itself. This is something that can be done across all operating systems with a Go executable, so I am planning to experiment with that.
Just to pre-answer the question "why rebuild winsw?" (which was asked the last time I brought this up), that project only works on Windows. The goal of this project and its sister projects was always to provide a common API across all operating systems.
If the experiments go well, I intend to deprecate this library (and node-mac/linux) in favor of a new single library focused exclusively on background services/daemons. If these changes happen, it likely won't be for awhile, seeing as I'm still pretty pressed for time.
Beta Was this translation helpful? Give feedback.
All reactions