I have a background with socket.io. Should I learn how to use vanilla web sockets or should I use µWebSockets until Why you should never use µWebSockets arrives ? Performance is not a priority right now, and premature optimization can hurt.
I think yarn also has downsides compared to npm. In npm if a dependency updates version patch, the potential security patch is now included in future npm installs. In Yarn you must manually update everything from what I understand
To an extend but not only. To get rid of the server we need to remove its authority too, which mean the client pseudo server are not just executing , they're doing it without a server telling them.
I am also exploring different ways to create "classes" of objects.
1 way I came up with is to use plain function that just returns a plain Object without prototype, without common functionality.
Methods are instead stored as plain functions as properties of the factory function(in JavaScript a function is also an object), with an explicit 1st argument taking the instance.
It plays well with higher order functions (forEach, Map, Some)
Example:
https://github.com/GrosSacASac/JavaScript-Set-Up/blob/master/js/examples/class/class5.js