Future Support?
JustinGrote opened this issue · comments
Hi @proxb,
Just curious if you plan to maintain the module since I haven't seen a commit in over a year, or if we should be moving to ThreadJob since that's the semi-"official" solution, even though it's nowhere near as feature rich as your awesome module.
Thanks.
if you don’t have enough features, you can try my fork
but ThreadJob looks promising
from my understanding, Microsoft chose ThreadJob becasue PoshRSJob uses some private interfaces.
I think firstly because ThreadJob is a native c# module :)
next, to give compatibility to existing Wait-Job
/Receive-Job
cmdlets
PoshRSJob use private interfaces for:
- Getting job state. ThreadJob use
InvocationStateChanged
event. I think, @proxb just not found it. (looks easy to change, may be I try it) - Importing variable by mask (unique feature), Can't remember why I use this method instead of
Get-Variable
, - Importing functions (unique feature). |I dont' know, is it can be rewritten
- Its own IsReceived flag.
So for Microsoft, I think this is not the reason
@JustinGrote Would I be correct in assuming your go to these days is ThreadJob? (I'm not sure if/how it's progressed since 2019).
@robinmalik Foreach -Parallel and ThreadJob as they are both first party solutions that are "good enough", I've been meaning to make PoshRSJob-style wrappers for easily importing functions and whatnot but it's been low on my priority list.