JVM Weekly #4 - Kotlin 1.7, Netflix doesn't use RX anymore, Vector API in action
vived.substack.com
1 - Who actually uses RX? Turns out it's not Netflix Today we'll start with some Twitter gossip. Sometimes in an ad hoc conversation, interesting facts can come out in an unexpected way - ones that can turn some commonly known industry facts on their head. It is likely that anyone who has ever used RxJava at some stage has come across the information that this library was created by Netflix. RxJava paved the way for other reactive programming projects. Its original version was created back in the days when nobody even planned Reactive Streams (only the 2.0 release introduced compatibility with this standard). So it's fair to say that it's Netflix we can thank for the boom in reactivity on the backend. So it will come as a surprise to many people that Netflix... has practically phased out reactivity already.
JVM Weekly #4 - Kotlin 1.7, Netflix doesn't use RX anymore, Vector API in action
JVM Weekly #4 - Kotlin 1.7, Netflix doesn't…
JVM Weekly #4 - Kotlin 1.7, Netflix doesn't use RX anymore, Vector API in action
1 - Who actually uses RX? Turns out it's not Netflix Today we'll start with some Twitter gossip. Sometimes in an ad hoc conversation, interesting facts can come out in an unexpected way - ones that can turn some commonly known industry facts on their head. It is likely that anyone who has ever used RxJava at some stage has come across the information that this library was created by Netflix. RxJava paved the way for other reactive programming projects. Its original version was created back in the days when nobody even planned Reactive Streams (only the 2.0 release introduced compatibility with this standard). So it's fair to say that it's Netflix we can thank for the boom in reactivity on the backend. So it will come as a surprise to many people that Netflix... has practically phased out reactivity already.