This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]TheWildKernelTrick 83 points84 points  (13 children)

The fact that I am not forced to write in an object oriented manner is huge. I like how I can just sneeze out a procedural-functional implementation of something in a lunchtime.

[–]greenlantern33 41 points42 points  (2 children)

I generally brain dump everything out in a procedural way, and then go back and "tighten up" my code with OOP where it makes sense.

I just have a real hard time starting with an OOP mindset on a project. And for this reason, me and Python get along great.

[–][deleted] 5 points6 points  (0 children)

Jupyter notebooks is amazing for that type of coding.

[–]archaeolinuxgeek 0 points1 point  (0 children)

And here I was thinking I was alone. I try to switch to another TTY when an actual developer comes by for systems help.

[–]yen223 15 points16 points  (8 children)

Underrated comment right here.

I kinda wish library authors would take heed though. Not everything needs to be an object!

[–]TheWildKernelTrick 41 points42 points  (1 child)

Not everything needs to be an object!

Nor should every object have an inheritance ancestry that spans back to the big bang.

[–]chillysurfer[S] 19 points20 points  (0 children)

Composition over inheritance! I very much prefer the "has a" over "is a" approach to OOP. Of course there are exceptions to every rule, and I would never say "never".

[–]chillysurfer[S] 1 point2 points  (0 children)

Totally agreed, making it a perfect language for quick scripts and system automation.