but not the message protocol
also if you look into ignite or any other cluster message exchange
why should it be diffrent concept in nodejs?
i see your point but i would not want that also
why should i circumvent that
it depends what you are trying to do with it, that makes it bad design
we could simply throw the term production ready into that :D
it helps no one if you give em to much freedom
the person which needs that kind of freedom can simply get it as it is open source
not much overhead to change protoypes via import and re export
there is different solutions, some work better than others, some might not be the best solution
but without knowning for it's used for and for what reason, or what the person try to do with it, you can't say it's either good or bad
and i see it the next 5 years
we all did produce a lot of stuff that now needs to get cleaned up
:D
that's the followup lol
let's just stay on topic
it runs now on ios and android all this stuff
that will go no where
so fast
C is still one of the most performant languages
rust will take over but v8 will not get recoded to rust in the next 5 years
it will partial get converted
at present a lot of parts of chromium are already coded in rust
rust can already create .node modules via neobindings
so the connection is perfect
I would love to recreate socketcluster using rust and wasm or a .node module
@Yamuna99 if you got anymore questions, let me know, i'm logging off for the night