react-websocket VS immutable-js

from flask_socketio import SocketIO, emitapp = Flask(__name__)app.config['SECRET_KEY'] = 'secret!'socketio = SocketIO(app)... # Server functionality for receiving and storing data from elsewhere, not related to the websocket# Handle the webapp connecting to the [email protected]('connect')def test_connect(): print('someone connected to websocket') emit('responseMessage', {'data': 'Connected! ayy'})# Handle the webapp connecting to the websocket, including namespace for [email protected]('connect', namespace='/devices')def test_connect2(): print('someone connected to websocket!') emit('responseMessage', {'data': 'Connected! ayy'})# Handle the webapp sending a message to the [email protected]('message')def handle_message(): print('someone sent to the websocket')# Handle the webapp sending a message to the websocket, including namespace for [email protected]('message', namespace='/devices')def handle_message2(): print('someone sent to the websocket!')@socketio.on_error_default # handles all namespaces without an explicit error handlerdef default_error_handler(e): print('An error occured:') print(e)if __name__ == '__main__': socketio.run(app, debug=True, host='0.0.0.0') For the front end, I initially tried using a library as well. I went with react-websocket.

immutable for JavaScript.

Check out Object.freeze. There's also Immutable.js for working with immutable data.

Use immutability to manage state updates When updating state in your React application, it's important to ensure that you are not mutating the original state object. Instead, you should create a new copy of the state object with the updated values. Immutability makes it easier to manage state updates and ensures that the updates are performed in a predictable and safe manner. Libraries like Immutable.js provide a set of functions that simplify working with immutable data in React applications.

We're wanting to get rid of immutable so I'm trying to replicate what it is about the Record functionality and types that allow this dynamic property access to work. After pulling my hair out looking through the [email protected] type definitions and the actual code, to me it looks like the types are just kind of lying about what's going on ... and it's just working. Does anyone have any ideas how I can replicate this dynamic property access with strong typings?

The Immutable.js README has a much more complete description of immutability and why you might want to use the library. Also worth mentioning that Immer is an alternative which is a bit easier to get started with.

Examples: immutable-js Immer

I can't speak to C# and Java, but the suggestion in this post: ImmutableJS already uses Persistent data structures. (It's the second sentence of their introduction)

Avoiding mutation is just never modifiyng an object, ever. There are tons of implementations of this pattern, notably immutable.js (https://immutable-js.com/), Redux is also an example of this philosophy.

JavaScript is most programers' first introduction to map, filter, and reduce. Easy lambdas made those higher-order functions a staple of a lot of JS code.

Meanwhile, immutable.js[0] is at 10 million downloads per week and rising.

I would add that it's not just the ease of use of lambdas, but the fact that in JavaScript functions really are first class citizens. Most of the other widely used languages that people start on have lambda functions added in as a bit of a hack and only treat some functions as real values.

[0] https://www.npmjs.com/package/immutable