As we get more & more sophisticated microservice implementations, each one grows their own crappy version of Erlang:http://www.infoq.com/news/2015/04/north-kerr-complexity-code …
-
-
Replying to @FrancescoC
@FrancescoC reflecting on whether we have created a crappy Erlang at@Wunderlist1 reply 0 retweets 0 likes -
Replying to @chadfowler
@chadfowler it does not always have to be crappy, those who understand the patterns and semantics often get it right.2 replies 0 retweets 2 likes -
Replying to @FrancescoC
@FrancescoC@chadfowler where is a good intro to a few of the most important ones?1 reply 0 retweets 1 like -
Replying to @PLT_cheater
@PLT_cheater@chadfowler look at the concurrency model, error handling (links, exit signals and monitors) and OTP1 reply 0 retweets 0 likes -
Replying to @FrancescoC
@FrancescoC@chadfowler I find the concurrency model in Haskell just as compelling, do you see any advantages in Erlang?1 reply 0 retweets 0 likes
Replying to @PLT_cheater
@PLT_cheater @chadfowler guess what inspired Haskell's concurrency model :-)
1:16 AM - 25 Apr 2015
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.