2 ms·
Had experience with it. I'll give my goods and bads after about 3 years. Good: 1. Its behavior is very predictable, both in performance and for conditional b
by cordite 9y ago
Had experience with it.
I'll give my goods and bads after about 3 years.
Good:
1. Its behavior is very predictable, both in performance and for conditional behavior.
2. Error handling is not leaky, which helps with predictability.
3. Memory sharing is pretty isolated when it comes to processes / threads, much like erlang
Bads:
1. If you want to do any sort of polymorphism or code reuse, consider yourself screwed.
2. It feels like assembly, everything ends up being tacked together and tangled for code reuse
3. What you write, and what you edit, and what you depend on will be long lived; version control blame will show code still running in production from before you even finished elementary school. Refactoring is impractical.
4. Event driven designs are nearly impossible to do in this environment.
5. Local environments are not a thing. You code in the same mainframe everyone else does. Good luck.