Yeah, I have been planning to try out Iroh sometime soon. However, what I explained will take a whole lot of planning on top of Iroh. I also don't want to replicate what others have already achieved. It would be best if something could be built on top of those. Let's see how it goes.
This doesn't do much for the argument that artists only do art for money. Everyone knows what happens to free use art, same as what happens to FOSS: corpos bundle it up and sell it back to people.
By the way, I do know a lot of artists that just give their work away for free. Hell, any Burn is just a bunch of free art that usually gets lit on fire or destroyed after a week. There's also graffiti art which is uncompensated and usually painted over within a month.
So there are some jobs that only a biological male can do, that a biological female is not qualified to do? If we made a list, which jobs do you think might be on it?
Being firefighters, yes to some extent, because males are more likely to have acquired the physical strength needed to lift people out of burning buildings. But there are many female firefighters who excel in the profession too.
There is nothing about males that make them more suited to be doctors. We also can see that in the demographics in some countries (e.g. the UK), there is a roughly equal balance of female doctors to male doctors.
Having mathematical ability is linked to intelligence, not sex.
Testosterone is inextricably linked to mathematical and spatial reasoning in the human brain. You are incorrect in your assertion that men do not inherently make better doctors and mathematicians. It is factually accurate to state that they do.
It's fine as long as the graph of references is immutable, or is unidirectional/acyclic with unique ownership.
If you have backreferences or "parent pointers", you need `Arc<Mutex<...>>` or `Rc<RefCell<...>>`, and then you run into trouble as you encounter the same node multiple times while traversing the graph, because you cannot hold a mutex lock or mutably borrow `RefCell` twice in the same call stack.
The solution with much less resistance in Rust is to go for a data-oriented representation. If you really need an actual graph of objects, separate the node data from the topology metadata, and refer to the nodes using an ID or index. (As an extra bonus, this also gives you much better cache locality.)
You don't really need the different IDEs. For example, you can install the Rust plugin and the TypeScript plugin in IntelliJ Ultimate, without needing RustRover and WebStorm.
reply