</Considers investing time in proper mastery>.
That's a classic example.It is less verbose to create a simple class.
It's less verbose to create a class but it hides the important fact that not every class has to be a monobehaviour.
The time it takes to create a proper C# class is no different (Unity creates it based on a template for you) - the cost of a limited mindset, at least in my experience - huge.
Lastly, your brain recognizes code patterns and fluff - it's not like you actually read every line every time you see a class.
So yeah, this fits my opinion [though I don't think I've mentioned it yet this thread] UnityScript is for Scripting, C# is for programming.
Though while we are at it, why include System.Collections?
Nope - look at your code it's near identical. Furthermore the including of the using and class servers no purpose as you've already covered it. Don't make me accuse you of double counting :PIt is less verbose to access components
First time I've seen that function used.It is less verbose to deal with Types
I need to point out that all you've pointed out are trivialities 'making simple things simpler'. Powerful things like events, extensions, linq, structs, lambda, properties, ref/out etc. are harder to do/less clear in US IIRC.
I tried to go back to US for a client. Problem was is everything I'm used to doing was so poorly documented it was too costly to be worth the while.
I'll just repeat what I said earlier. I do network programming. It's very complicated [hence my love for C#]. However I sit down and analyse the performance of every single action - down to the BIT on occasion. I've yet to run into a performance bottle neck that required micro-optimization but constantly struggle to manage the interactions between my systems.Time is an asset - no doubts. Fast made, readable, reusable code, fast, maintainable code, add yours. Perhaps coding is about balancing between those desirable outcomes. I still believe that real time applications should have fast code as a priority but I respect your POV. Perhaps I should add that a priority doesn't mean the only priority, to make my POV clearer.
There are situations where performance is important - but wait until you can actually PROVE that that's so before wasting time on optimizing.
Dude, this is my sword :PI cannot keep up with this, you write too fast ! Swords down :P
Man that was a long time ago.