Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | dialmove <dialmove@gmail.com> |
|---|---|
| Newsgroups | comp.misc |
| Subject | Re: Can Reactive Programming Handle Complexity? |
| Date | 2014-02-20 16:17 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <le59r0$1c4$1@dont-email.me> (permalink) |
| References | <le0u4o$eup$1@dont-email.me> |
El Tue, 18 Feb 2014 16:33:28 -0800, Oregonian Haruspex escribió: > He shows how Reactive can handle complexity using > two different scenarios: a classically complicated database application > (a bill of materials price rollup) and procedural integration (to > address external systems such as email and transactions not limited by a > database update). Take a look at his work; do you agree?" The Functional Reactive paradigm provides better abstractions for concurrency than imperative code - futures, promises and observables are at a way higher level than locks and semaphores, and in many cases allow writing complex asynchronous code in a pure functional way. For the rest of cases, you can add explicit state and transform it into an agent-based model, which is essentially OOP parallelism done right. So yes, I think a high-level paradigm that simplifies synchronization can make complex parallel tasks easier to program and reason about. I've seen some examples in action, of which Espresso Logic is an awesome case. > It seems that every few years somebody tries to re-invent true MVC OOP. > "Reactive Programming™" seems to be the attempt being pushed on the > poor public by Dice Media, no doubt in exchange for a healthy sum. If > you look at the examples given, and are familiar with Self or Smalltalk, > you'll see nothing new, and both languages are now over two decades old > (Smalltalk is well over three). That's like saying that building a library for P2P communication is trying to reinvent the TCP/IP protocol. Sometimes you need to look your old tools from a new perspective to adapt it for new, complex use cases that were impossible to tackle from a low level perspective. Several mayor players as well as multiple small ones are adopting tools from FRP for their libraries and software stacks, and knowledge about the paradigm is spreading through official documentation, MMO courses and the blogosphere - which makes corner cases shallow, and deepens our understanding of the paradigm.
Back to comp.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Can Reactive Programming Handle Complexity? Oregonian Haruspex <bob_davis_retired@yahoo.com> - 2014-02-18 16:33 -0800
Re: Can Reactive Programming Handle Complexity? dialmove <dialmove@gmail.com> - 2014-02-20 16:17 +0000
Re: Can Reactive Programming Handle Complexity? dialmove <dialmove@gmail.com> - 2014-02-20 16:36 +0000
Re: Can Reactive Programming Handle Complexity? Marko Rauhamaa <marko@pacujo.net> - 2014-02-20 20:09 +0200
Re: Can Reactive Programming Handle Complexity? wjwlsn <ibillwilson@gmail.com> - 2014-02-20 13:05 -0800
Re: Can Reactive Programming Handle Complexity? Marko Rauhamaa <marko@pacujo.net> - 2014-02-20 23:18 +0200
Re: Can Reactive Programming Handle Complexity? wjwlsn <ibillwilson@gmail.com> - 2014-02-20 13:40 -0800
Re: Can Reactive Programming Handle Complexity? dialmove <dialmove@gmail.com> - 2014-02-21 13:56 +0000
Re: Can Reactive Programming Handle Complexity? dialmove <dialmove@gmail.com> - 2014-02-21 13:34 +0000
Re: Can Reactive Programming Handle Complexity? Marko Rauhamaa <marko@pacujo.net> - 2014-02-21 16:57 +0200
Re: Can Reactive Programming Handle Complexity? dialmove <dialmove@gmail.com> - 2014-02-21 15:49 +0000
Re: Can Reactive Programming Handle Complexity? Marko Rauhamaa <marko@pacujo.net> - 2014-02-21 18:22 +0200
csiph-web