Win a copy of Pipeline as Code this week in the Cloud/Virtualization forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Jeanne Boyarsky
  • Bear Bibeault
  • Rob Spoor
  • Henry Wong
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Carey Brown
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Frits Walraven
  • Himai Minh
  • Jj Roberts

Functional paradigms are bringing imperative chaos

Ranch Hand
Posts: 536
Android Open BSD Slackware
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am into Kotlin, after three years I am using it, I would not go anymore back to Java, although is 100% compatible, aka is possible to write some class in java other in kotlin into the same project.
It offers a lot of features, most of them offer kind of functional paradigms. I use it with RXJava and RXKotlin a powerful library that is a kind of Observer pattern with muscles. What muscles. Basically there are something as 200 operators that allow to filter, switch, zip, merge, combine an Observable, a stream in the last Java, with an observer that subscribe on a certain time. All of this making use of concurrency just "declaring" upstream to start an operation in a thread, and downstream to observe the final stream event on the User Interface.  This changed completely my idea of Object Oriented programming, of using statements to change states as in the imperative programming one is supposed to do.
From one side I find it really exciting, from another one when one examine some code, there is a lot of magic involved, and I realize to stay miles from low level code.  Is a strange situation but I guess is where coding is going in the future, an universal paradigm, always more functional oriented. But then I think over at all the great dev people that love Lisp and Clojure, and realize that I am losing the dream to have a full knowledge of coding, because is averting completely from :
structured programming paradigms.

Functional or Imperative, why is happening that. We need seriously in my opinion a philosophy of coding, as extension of the
philosophy of the language

to understand
1) where we are going
2) why we are going

Otherwise will be the chaos of the forks of new languages, and chaos is not good because coding in my opinion is firs of all structure
So it takes a day for light to pass through this glass? So this was yesterday's tiny ad?
SKIP - a book about connecting industrious people with elderly land owners
    Bookmark Topic Watch Topic
  • New Topic