> Like everyone sane before them they figured N:M scheduling is not the way forward and they ripped it out before going stable. Why do you think Java recently

> Like everyone sane before them they figured N:M scheduling is not the way forward and they ripped it out before going stable. Why do you think Java recently went from N:M scheduling? Surely there's something to it?