I'm doing a free C-course at the university right now, but my actual goal is to learn C# to make games with unity.
Do you guys think it makes sense to learn C first with guidance and C# on my own afterwards?
Learning C first and C# afterwards?
It always makes sense to learn C.
Bump.
I've been learning C for 3 months now, I completed the online course and I've been learning about algorithms since then.
Does it make sense to learn C# now or should I go with c++ that is much more similar.
I just want to make GUI desktop applications, no gaymes or anything.
I learned C++ then C#. However I didn't get a good understanding of OOP until I made some shit in C#, even though I had a solid foundation with C++. Perhaps it would be better to start in C# if you're going to be making games, but you have already started your C course so just go through that first. Doesn't really matter in the end imo.
Embrace Qt and fuck everything else.
Will do, thanks. Any resources you recommend about Qt? I normally watch YouTube courses and complement my knowledge with some book.
>watch YouTube
You'll never be a good coder.
Don't use some homebrew neckbeard garbage download VS and start learning WinRT/UWP
You know, like a normal fucking person would
Am I wrong if I say that Java gives better understanding of C# than C? (Of course, learning C# directly is best if that is your goal).
If you want to make games with Unity and C# then go and do it.
C is always good because you can learn about pointers and how memory works, but it isn't necessary for what you want. It isn't going to give you a huge advantage when learning C# (especially in the context of using it with Unity).
Also stop thinking in terms of "I want to learn language X" and instead "I want to do/make this". Languages are tools, pick the best one for the job.
Though I should add if you have never programmed before then learning C with some guidance would be a good idea. It'll teach you the fundamentals.
>coder
And you will never be a good programmer.
>hating the verb to code
That's the best way to recognize a code monkey. I'm a proud coder.
Learn both. Be glad that you have a reason to learn C. I am a C# dev and it is really hard to find motivation to learn othet languages mow when C# and .NET are developinv really fast, now you have xamarin, azure and so on.There is always something more to learn to improve my C# and I do not have time to learn C. So do it while you can because once you have a proper job life gives you not much time for learning because of family etc.
So learn C while you can!
>However I didn't get a good understanding of OOP until I made some shit in C#
Did you attempt to learn OOP in c++?
learning a 'language' isn't like learning a real fucking language, its more like moving to a new area and picking up a new accent and some local dialect words here and there.
if you have a solid foundation in principals of how computers work, processor pipelines, memory architecture, datastructures and algorythms you can pretty much understand anything.
you shouldn't be 'learning c' you should be learning foundation principles of how to structure a piece of software and interact with a processor in what just so happens to be c
going to c# shouldn't be a major mindfuck if you understand the purpose of oop (pro-tip: there isn't one lol j/k) and are prepared to spend maybe an hour familiarising yourself with the boilerplate shite.
except functional programming. thats like learning chinese or some shit. like wtf i hate monads now
>learning foundation principles
What good resources are there out there to learn them?
For GUI applications for Windows desktop c# is king.
Wpf allow you to easily and quickly write good interfaces in xaml.
Look it up.
WPF is dead in the water already
Sad really. WPF is really fucking good once you truly understand it and worked with it for a while. They should have designed it with more than just muh windows apps in mind. Like a real cross-platform, cross-device UI framework. But I guess their change of mind (open sourcing .NET, C#, ...) came too late.
none.
there are no 'good' resources to learn anything online.
there used to be a great resource called the 'library' that had 'books' where you could read things.
about 10 years ago i had a dig though a bin that my library was getting rid of andgiving away ratehr than burning. I got some great books that detailed in excruciating fashion the inner workings of computers. They were being removed from stock because they were believed to be out of date which is rediculous because the key core concepts that were explained are as true today and a great learning curve.
anyway i am rambling.
when i was at school they told me to read
ISBN-10: 0130204358
ISBN-13: 978-0130204356
but i didn't have the money to buy it so i didn't bother, i can't recommend it.
if you want to learn how computers work then go to school and take a class on it.
if you want to learn how to write software go to stackoverflow and search what you want to do, guarantee someone else has done it.
or just fucking bash it out and see what happens, experiment, make mistakes. i cut my teeth writing image processing routines in C based on a hardcopy of matlab helpfile describing operations. wicked fun i'll tell you that. find something interesting, figure out how to do it. thats how you learn. pick up some tricks and shit on the way.
if you write something then be proud of it for about 30 seconds then post it to codereview on stackexchange and have internet strangers tell you how absolutely shit you are and more importanlty how you can improve.
is UWP really replacing WPF? How is it different from it?
Better scaling, you can compile directly to Xbox, Windows Mobile and Hololens...
>is it good to educate myself
ranjid, go back to your shitting street
No. Java is obviously a lot closer to C# than C is.
You know, it's glaringly obvious that you're a Microsoft shill when you write shit like that.