17 ms·

Back when I was a kid, we called this rapid application development - but then again, we didn't create cults around dev methodologies...

• naasking 9y ago
  > but then again, we didn't create cults around dev methodologies... You sure about that? I certainly recall plenty of holy wars over object oriented programming.
  • mhd 9y ago
    And the 4GL bubble.
• klibertp 9y ago
  > Back when I was a kid, we called this rapid application development What do you mean by "this"? RAD tools like Visual Basic, Delphi or Cincom Smalltalk were event-based - which is also true with most native GUI frameworks, BTW - but they did not provide any abstraction above the level of events. Reactive programming takes events and stuffs them down a set of pipelines, where previously you had this giant switch statement for dispatch and the logic for actually doing something was split among some of the branches of that switch. Now you can group your logic around a certain pipe, which allows you to see a complete description of complex processes at a glance, without the need to guess "which event is used as a next step of this process?" So Reactive is actually a quite convenient interface to event-driven systems and it wasn't available in RAD tools of the nineties (if memory serves, might be wrong on this?)