thank you for your reply and i agree. i think the level of abstraction in c# may be too high for my liking. i know that sounds like a weird thing to say but i cant describe it any other way
i think i may have been too hard on c# in my previous post. it's a really nice language for what it is but i think what i dont like is the object orientated mindset about it. the language, and all learning materials that teach you how to use it so far, teach/force you to think in a object oriented way and i've been constantly struggling with that. it seems to make things more complicated than they needed to be. it forces you to think about structuring/organising your entire project, and any future extensions to it, right from step 1, and thinking of every little thing as an object. it feels like im writing a ton of code without it actually doing anything. some saying goes like 'premature optimisation is the root of all evil', well i think oop is basically premature obsession with code reuse and extensibility. it's not fun to work with. i can see how that makes more sense in an enterprise environment with big teams and long term maintenance. but i just want to learn to make something cool. i see now why oop is so frowned upon by some. to the point, even in the Nim Official Tutorial (i think was part II) it mentions that it has support for minimal OOP, but it emphasises doing things in a procedural mindset. i think i need to start looking for more non-/anti-OOP style learning materials
