As I’ve explained elsewhere there’s nothing wrong with just using the stuff from hx3compat if that suits your needs. But: all those solutions have serious limitations and you can’t lift those without compromising on simplicity.
So I guess the remaining question is whether or not this “stack” should stay in the standard lib.
My impression is that nobody on the compiler team likes it or uses it, which seems enough of a reason to move it out. Additionally, it’s doubtful that today it should be the suggested solution for people who come to Haxe (when these solutions were new they were absolutely amazing, but things evolve while no part of this stack caught up). Dispatch’s inability to route based on verb pretty much promotes unrestful RPC-ish interfaces, haxe.remoting is a custom protocol that is not exactly easy to interface with from other languages and as for SPOD it is pretty much ok, but it doesn’t work on node, and is overall quite limited.
That is not to say that this you shouldn’t be using this stack if it serves you well 