If much of it comes to feel like that, however...What then? π
ALostInquirer
Any in particular you're fond of but don't see mentioned as much?
Yes I've been paying attention, however it remains baffling to me as I see curiosity as essential as breathing or eating, so perhaps the question may be better asked as, how is inhibiting curiosity not recognized as a form of abuse?
Do you guys think we use Steam because we HAVE to? GoG exists bros, weβre using Steam because we prefer it.
Do you think many are aware of options like GOG? Every other time I've seen it mentioned/suggested, it's often accompanied by, "What's GOG?"
The other part of the question remains however, what happens when leadership changes, even supposing no sale of the company?
Oh, I hadn't read of it in that form, thanks!
What happens when the leadership or ownership changes hands?
What is a PMFN?
How do you indoctrinate the curiosity out of people? π¬
Thanks for elaborating! I'm pretty sure I've written some variations of the first form you mention in my learning projects, or broken them up in some other ways to ease myself into it, which is why I was asking as I did.
One is simply organizing your code by having a bunch of operations that could be performed on the same data be expressed as an object with different functions you could apply.
Not OP, but also interested in wrapping my head around OOP and I still struggle with this in a few different respects. If what I'm writing isn't a full program, but more like a few functions to process data, is there still a use case for writing it in an OOP style? Say I'm doing what you describe, operating on the same data with different functions, if written properly couldn't a program do this even without a class structure to it? π€
Perhaps it's inelegant and terrible in the long term, but if it serves a brief purpose, is it more in the case of long term use that it reveals its greater utility?
Thanks, it looks cool! It brings to mind some of the terminal-based connections some have made, if I remember right.