— And also stuff simply not working as intended because I didn't wrap stuff in Meteor.bindEnvironment
And stuff which looks very sync because of no await or .then, but is really async because of fibers, makes code harder to understand and debug
— Typescript VS ES6,7,8 ?
— Then your "bugs" are the same all people have when dealing with threads..
— And nodejs works very well with just 1 thread
— Keep it that way
— Why would I introduce a buggy and error prone lib to my code to do stuff which I can do perfectly well without that lib?
Message permanent page
— How to introduce multiprocessing in nodejs?
— Fibers are not buggy then, programmers of js have no idea about threading
— This stuff stands regardless of whether or not it's the programmer's fault