— Switching to serial instead brought the solving time down to 1 second because it didn't have to create and manage literally 1000 fibers
Message permanent page
The process completely locking itself with 100% CPU and no system calls at all and no response because of a fiber bug
— 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?
— How to introduce multiprocessing in nodejs?