3 ms·

What is "conventional programming", pray tell?

by hfkwer 3y ago

dragonwriter 3y ago
Functional? Procedural? Logic? Dataflow? Relational? Unstructured imperative, like old-school BASIC? I mean, the only clue we have is that it is some paradigm that isn’t OO, but that leaves... a whole lof options.
dsego 3y ago
Maybe procedural?
- KerrAvon 3y ago
  I think the root rant here, which I personally find unconvincing, is thinking in terms of OOP vs functional programming. Procedural isn't the opposite of OO; objects are composed of many procedures.
  - MetaWhirledPeas 3y ago
    I wasn't intending to trigger anyone but it seems I have. Perhaps I should have stated it as, "why OOP instead of organizing the code through other means?" It's a genuine question I have, and it just hasn't clicked for me yet, personally. So it's not really trying to be convincing at all; I'm just sharing my experience.
    - c_crank 3y ago
      The most compelling scenario for OOP is situations where, in its absence, a developer would tend towards reimplementing some OOP concepts over time. I think it is a natural fit for game development and some other things, but I don't think it melds so well with that thing we call 'business logic'.
    - dsego 3y ago
      I don't think there is a satisfying case for OOP. https://youtu.be/QM1iUe6IofM?t=477 https://youtu.be/QM1iUe6IofM?t=477
    - SAI_Peregrinus 3y ago
      OOP works well when state and behavior are tightly coupled, particularly for things which are naturally modeled as state machines. Device drivers tend to be perfectly suited to OOP organization: the underlying device has state that needs to be tracked, it has behaviors which can be controlled (usually by sending particular messages), and there are often multiple implementations of the hardware which should all expose the same high-level API. OOP allows bundling the state handling with the control messages needed, exposing a single common API while allowing specialized implementations for particular driver implementations. For the higher-level code, it's often less useful.
afiori 3y ago
Algol

What is "conventional programming", pray tell?

by hfkwer 3y ago

What is "conventional programming", pray tell?

Functional? Procedural? Logic? Dataflow? Relational? Unstructured imperative, like old-school BASIC? I mean, the only clue we have is that it is some paradigm that isn’t OO, but that leaves... a whole lof options.

dsego 3y ago

Maybe procedural?

KerrAvon 3y ago
I think the root rant here, which I personally find unconvincing, is thinking in terms of OOP vs functional programming. Procedural isn't the opposite of OO; objects are composed of many procedures.
- MetaWhirledPeas 3y ago
  I wasn't intending to trigger anyone but it seems I have. Perhaps I should have stated it as, "why OOP instead of organizing the code through other means?" It's a genuine question I have, and it just hasn't clicked for me yet, personally. So it's not really trying to be convincing at all; I'm just sharing my experience.
  - c_crank 3y ago
    The most compelling scenario for OOP is situations where, in its absence, a developer would tend towards reimplementing some OOP concepts over time. I think it is a natural fit for game development and some other things, but I don't think it melds so well with that thing we call 'business logic'.
  - dsego 3y ago
    I don't think there is a satisfying case for OOP. https://youtu.be/QM1iUe6IofM?t=477 https://youtu.be/QM1iUe6IofM?t=477
  - SAI_Peregrinus 3y ago
    OOP works well when state and behavior are tightly coupled, particularly for things which are naturally modeled as state machines. Device drivers tend to be perfectly suited to OOP organization: the underlying device has state that needs to be tracked, it has behaviors which can be controlled (usually by sending particular messages), and there are often multiple implementations of the hardware which should all expose the same high-level API. OOP allows bundling the state handling with the control messages needed, exposing a single common API while allowing specialized implementations for particular driver implementations. For the higher-level code, it's often less useful.

afiori 3y ago

Algol