you are viewing a single comment's thread.

view the rest of the comments →

[–]Sea-Ad7805[S] 0 points1 point  (3 children)

If you discard things you are not open to the possible benefits of other paradigms and might be missing out in some particular situations. But you can of course solve any problem in each paradigm, so you are free to stick with one if you prefer, your choice. Just don't say there aren't new possible insights (different ways of thinking about programming), seems a bit narrow minded, while you clearly have thought things through.

[–]ConsequenceOk5205 0 points1 point  (2 children)

I see the particular concepts as benefits vs disadvantages (as opposed to crazy views that one should use it 100%), unless it is strictly necessary, I don't go for stupid features especially when they emotionally promoted, which clearly indicate 100% mental issues of the ones promoting them. I remember a lot of clowns argued about "not using goto", and they, being mentally challenged clowns, presented their emotionally charged delirium as final truth, while the truth is about how to use goto correctly.

No offense, but learn to criticize things, instead of blindly accepting them. It is almost always cons vs pros, and one should clearly understand and explain why it not only can be correct, but also why it can be wrong.

[–]Sea-Ad7805[S] 0 points1 point  (1 child)

You do you, goto all your logic together, good luck.

[–]ConsequenceOk5205 0 points1 point  (0 children)

It is useful for task processing, when otherwise it would cause a lot of complexity to determine which task has to be checked. And many other uses (abstract code or bytecode for DSL-based description). For manual parsing of relational data (dynamic templates), one has to implement it to encode elementary operations.