In oOp it is so difficult to determine the livetime of objects and if properties change over time.
for most node.js server applications the word functional programming is taking it to short. because testing a unit with input and output does not meet what we are doing when implementing application servers (same in php, ruby,....), when the only thing we are doing is to build side-effect machines.
I started saying to do structured programming. A bit as described by Kevlin Henney. I name it structured programming, even dough in my current project, most methods are part of a class.
using class syntax does not necessarily mean to do OOP, same as the use of pure objects or structs still allow you to organise code in a object oriented manner.
thanks for this question 👍
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In oOp it is so difficult to determine the livetime of objects and if properties change over time.
for most node.js server applications the word functional programming is taking it to short. because testing a unit with input and output does not meet what we are doing when implementing application servers (same in php, ruby,....), when the only thing we are doing is to build side-effect machines.
I started saying to do structured programming. A bit as described by
Kevlin Henney. I name it structured programming, even dough in my current project, most methods are part of a class.using
classsyntax does not necessarily mean to do OOP, same as the use of pure objects or structs still allow you to organise code in a object oriented manner.thanks for this question 👍