Comments by "" (@jboss1073) on "Functional Programming IS NO BETTER than Object Oriented Programming | Prime Reacts" video.

  1. 25
  2. 25
  3. 17
  4. 12
  5. 10
  6. 7
  7. 5
  8. 5
  9. 3
  10. 3
  11. 2
  12. 2
  13.  @curlyfryactual  " like I said, a global is just a poorly implemented object. " But it's not, and no serious Computer Scientist would say that. A global is just a variable - an address in memory with some room for you to store some bytes. An object is a closure over methods and attributes plus a virtual table. In no way can you say that "a global is just a poorly implemented object" as those two things have nothing in common with each other. Globals are not objects. Not even poorly implemented ones. They're just not objects at all. "because a global is already the enemy of concurrency. " WRONG. If it is a Mutable Transactional Variable made global then it is concurrency-safe and parallelism-safe. You are having this newbie mindset that "globals" are just what you learned, but that's not true. Many things can be global, including concurrently-safe transactional variables. In fact, that is how it is done in the industry. "I work with enough "procedural with globals" architecture these days, and it's simply a pain. It is no easier to parallelize the execution of it; in fact, far worse." That is because you are ignorant of the existence of transactional variables. You shouldn't just make a value globally available in a global variable without putting it in a Software-Transactional-Memory box. Look into Clojure, all the globals are parallel-safe and concurrent-safe. "I love declarative code as much as the next guy. Plopping in a global is certainly not that." This discussion is not about "declarative code". But even if it were, Haskell is transactional and they have concurrent-safe globals too just like Clojure. It may be only the stinky language you're using making you believe globals cannot be concurrent-safe. Not true. "May as well do it right." Throughout your answer you have demonstrated you do not have the sufficient Computer Science knowledge to do anything right. God help your clients.
    2
  14. 2
  15. 1
  16. 1
  17. 1
  18. 1
  19. 1
  20. 1
  21. 1
  22. 1
  23. 1
  24. 1