If you're a new programmer, I don't think you should start from OO. OO-based languages are built on procedural, structural and imperative programming foundations. Starting from OO may force you to see everything as an object even when it doesn't fit.

The less you start off with, the better your understanding will be, and then you should learn to expand your horizons with other programming paradigms: logical, functional, and many others.

OO is more an organizational method than a programming method; it still falls down to being imperative (do this; do that). OO is nice when you have a lot of types and few actions whereas non-OO languages are nice when you have lots of actions and few types. When there are a small number of types and actions, it really doesn't matter which organization method you use, but if you expect the types to grow, use OO. If you expect the actions to grow, don't use OO. If both are expected to grow to large numbers, there still isn't a good organization method yet.

Yes, functional. I wasted a good 15 years in the OO world and wish I'd never seen it.