choiway
Joined 9 years ago
Karma
72
Submissions
61
Member since
Jan 24
https://choiway.github.io
B97F 5BA3 3E2D E45A 094A 5963 3413 5EAC 6083 2C90
View on Hacker NewsJoined 9 years ago
The way isolated processes can be created and managed allows for the "let it crash" ideology in Erlang. For example, when you visit a Phoenix Framework site, you have your own process. If I was visiting the same site and encountered a state that crashed my process your process would be unaffected. The "exception" would only affect me until you ran into the same state that caused the crashed.
If I reported the crash to the developer, the developer could fix the bug and soft start the entire application without affecting your process. This isn't possible because of the language per se but really because of the entire Erlang ecosystem around fault tolerance.
*edited for more stuff
Isn't WPF getting phased out tho?