If you need to drop down, at least drop down to Rust and not C/C++, please :-)
So the moral of this story is that if you need to fix a bottleneck in the real world, you mainly use erlang then drop into C (port/nif) where necessary?
Ask yourself: Why do kids prefer to spend money on pizza and burgers, and not green vegetables and fruit? It's obvious which is the better investment.
I'd say that Rust is telling you that you don't correctly understand your use of shared data. This should be looked upon as a great prompt to figure it out. I faced a similar issue with "getting" Rust. I found that a…
Ah yes. The difference between actual requirement and perceived requirement. Worthy statement.
Yeah. No.
If you need to drop down, at least drop down to Rust and not C/C++, please :-)
So the moral of this story is that if you need to fix a bottleneck in the real world, you mainly use erlang then drop into C (port/nif) where necessary?
Ask yourself: Why do kids prefer to spend money on pizza and burgers, and not green vegetables and fruit? It's obvious which is the better investment.
I'd say that Rust is telling you that you don't correctly understand your use of shared data. This should be looked upon as a great prompt to figure it out. I faced a similar issue with "getting" Rust. I found that a…
Ah yes. The difference between actual requirement and perceived requirement. Worthy statement.
Yeah. No.