Best Place To Learn JS With Unity

Hi, I want to start learning javascript so I can use it with unity. I don't know where to start and it just seems so complicated. Anyone know a good place that teaches it well?

 

You should take a look at this.

 

I fear that this will just confuse him even more.

There are quite a few Unity books out there. Most of them uses Unity's Javascript.
Another good start is here: http://docs.unity3d.com/Manual/CreatingAndUsingScripts.html

 

I don't know, I think it's a good idea to learn right up front that 'unityscript/unity javascript' is NOT the same thing as 'javascript' (and maybe even that javascript is not java either...).

Otherwise it might be confusing down the line when they're wondering why real javascript and unity javascript aren't interchangeable.

And then of course, there'll be the usual suggestions to not learn unity javascript, and to learn C# instead.

 

Happy to oblige. Unless you have a good reason to learn JavaScript then C# is better.

Either way the scripting tutorials in the learn section are a great place to start.

 

But which one is easier to learn. I have no experience with either.

 

Then go C#.

C# will take you about half an hour longer to get comfortable writing scripts. Its slightly more difficult to learn from scratch.

JavaScript will take you hours to debug the various typing issues present in the language. Its easy to start learning JavaScript, but its more difficult to learn to use JavaScript properly.

 

Agreed. And this goes for javascript in general, not just unity javascript.

Javascript, in my opinion, survives on the fact that it's SUPER easy to pick up and learn and get coding immediately.

BUT, as your code grows, it because unwieldly and crazy to chase down all the strange bugs that crop up from the loosey goosey nature of it. Making mastering it harder.

C# has a steeper learning curve up front, but javascript's curve quickly becomes steeper as you progress.

But then as you get into the more advanced parts of C#, accomplishing certain tasks become a ton more easy. The complex design stuff can be accomplished with very little effort in the language. Stuff that with out the already gathered up skills from coding with it wouldn't make sense. Stuff that doing in javascript becomes unholy complicated, to near impossible (I mean it's technically possible, just so absurdly obtuse that you wouldn't even do it).

 

Welcome at the language faith war again. And as usual filled with nonsense and myths.

I haven't found a single thing yet that i couldn't do with Unity JS. And when it comes to Unity tutorials, there are still more Unity JS tutorials and books around.

Fact is, you can do the very same game with both languages. It will run in the same speed, it will look equal, and you will need roughly the same time to develop it. Some things goes easier and faster in JS, some things goes easier and faster in C#. And you cannot say which game was made with C# or JS afterwards.

Switching the languages is not really a big deal once you have learned the concept, and in case there is really a need to. So the more important question is: which language is easier to use for Noah 492 to learn this concept. And he explicitely asked for JS advice. Not for somebody to convince him to C#.

 

So we actually agree to a degree.

I said JS was easier from the get go, for the beginner. You say the same thing.

I said that there are things that in the more advanced cases near impossible, or are convoluted to perform in U/JS. You not only agreed, you gave an example!

I said that C# is more difficult up front, but is easier in the long run. You don't deny this at all, and nearly imply that you agree by saying that most users making just a "usual game" won't run into these issues.

I don't care if you use U/JS. Hunky doory, that's your choice.

I merely stated the other option, and highlighted reasons why.

You AGREED with those reasons.

You just come to a different conclusion based on them.

Guess what... OP might come to their own conclusion as well.

Whose faith war is it again? Because it ain't mine, C# is one of 26 languages I write regularly. I don't really have much faith to just C#. S***... I write javascript (regular javascript) quite often.

 

Then you should know that a language is just a tool. But still you hijack this thread to try to convince the poster from C#, unasked. And this thread hijacking of JS threads to get a word placed about C# and that it is so much better is some kind of e-sport at this board. And i find it highly disturbing.

He already did. This thread was about where to get help for learning JS. Not what language is better.

--------------------------------------------------------------------------------------------
Two deleted messages later we have some loose ends, so ...

The named example here was that i needed to grab and use a MSDN C# code to call a Windows file browser. And i also stated that this is not a JS problem, but a Unity limitation, since Unity's Runtime does not offer an access to Windows File browser at all. Unity is a Mono based multiplatform game engine, not a Windows C# ide.

 

I have seen this thread before...

Anyway, I switched to C# because importing certain assets with JS can be a real pain. The cool assets seem to be written in C#.

 

Tiles he was objectively looking at it, also some other ups for C# is that C# skills learned for unity are useful outside of unity as well since it is a standard programming language used for many things.

In the end its just a tool, I work with many programming languages as well, and sure I got my favs but your also not going to see me pushing for python to be used somewhere when I know a strongly typed language would be better for said use, or vice versa.

In the case of unity I objectively think that C# is the better choice being a real language with its own set of resources, access to 3rd party libraries that can be integrated and because of some of its features like events, delegates and interfaces lend them self's well to game programming.

Not to mention the added confusion of unitys js acting nothing like what js is elsewhere, since in unity it is class based with typing in a explicit manner vs if you are familiar with it from the web. It approaches OOP in a very different way with prototypes and typing is rather implicit

 

And again we have a thread that started as a question about Unity's Javascript and turned into a *C# is so much better dude* thread. Full with myths and untrue statements to let C# shine. This is really sad.

 

No untrue statemeants I mentioned some things C# can handle better, there are a few for unityscript as well like its less verbose way of dealing with coroutine's.

 

Well, i could start a debate now where imho the untrue points are, which are by the way not necessarily told at your end, and we could go on with the eternal debate what is better, JS or C#. It exists since the two langages exists.

But that's exactly what i complain about. This thread is hijacked now.

This was initially a thread where to get learning resources for Unity's Javascript. Now it is a thread how well C# is, and why folks have switched over. And any further searcher will find everything but a useful answer to the question where to get learning resources for Javascript.

I have seen this pattern here again and again. A question about Unity's Javascript comes up. But instead of an answer to the question folks jumps in and declares C# as the better language. And makes any further useful answer impossible.

 

It looks like this thread is hijacked primarily by your complaining.

 

I have answered the initial question right at the beginning. But i haven't seen you answering the initial question yet. Just your C# blah blah and your attack here now.

So who is hijacking here?

 

I actually wonder if this is the case anymore. I don't remember the last time I found a blog post or tutorial that was written in UnityScript.

People are simply offering suggestions - you're welcome to do the same instead of accusing everyone of being a part of some grand anti-UnityScript conspiracy. Maybe it's just me but it feels like the only threads in the Scripting section that you contribute to are ones like this - so the prophecy seems self-fulfilling ultimately...

 

Well to get back on topic, no matter which language you choose you should have a clear goal of what you want to accomplish while learning the language, but make sure that goal is within a time frame and scope that you can soon see the results of what you have learned. This will keep you much more motivated to continue on.

I also i am inclined to belive most new tuturials are for C# these days, and from my experience with freelance and exposure to 4 differnt studios that use unity it has all been C#. Though take the tuturial bit with a grain of salt, since im not the type to go looking for them and dont know what is avialbe at the moment.

 

There's also no reason to not just start here: http://unity3d.com/learn/tutorials/modules/beginner/scripting

Which also includes code in every supported language so the conspiracy theorists can rest easy.

 

easy - don't learn js. JS is a second-class citizen and not going to be well supported in the future of Unity. Learn C#.

You can make all the discussion you like about it, but js doesn't have a future here.

 

I'm also thinking the same way. "There are more tutorials and better community support for UnityScript" is a common myth. It might have been true a few years ago, but its not true now. Most of the learn tutorials are in C#. Most of the live training sessions are in C#. I watched considerable portions of the last two Unites via YouTube, I didn't see one presentation in UnityScript. On answers you are just as likely to get a result in C# as in UnityScript. C# also has decent support on stack overflow and MSDN for general programming topics that are not specifically related to Unity.

UnityScript is far from dead, indications are there will be continued support for it far into the future. But its not the standard language for developing in with Unity anymore. In general my advice for new comers should be to learn C#, unless you have a good reason not too. Good reasons could include existing familiarity with JavaScript, existing code bases in UnityScript, studio and customer requirements ect.

 

JS (Unityscript) is being phased out - Boo is already soft-removed, ie not officially supported. JS will follow and with current trends probably won't be in Unity 6. The reason for this is only a tiny % of Unity users actually use Unity JS, and it's never been able to reach feature parity with C#.

It's just better to future proof yourselves with a strong focus on C# - it's a better language, far more features and almost the same.

It's dead. It's still twitching and there's no indications that there will be continued support for it far into the future but don't take my word for it

Well Javascript on the web isn't compatible with Unityscript, and that's one of the gotchas right there.

 

How times have changed...

http://forum.unity3d.com/threads/ma...unity-4-and-non-functional-in-unity-5.131902/

 

And why is that so? Because lots of JS thread gets hijacked by C# fanboys since years. And instead of doing something against it you even cheer about it. Well done.

Still at 20% even with all the language bashing.

So basically you say Js can only rotate a cube, while C# can rotate a cube, wash your cloths, and bring you your emails too? F*** yeah! \o/

Irony off, here we are at the myths again. Even nowadays you have the same access to the Unity API with both languages. You can still make the same game with both languages.

I have kept my hands away from language threads for a long time now. And the very first thread where i touch it again after months gets hijacked from the C# fraction as usual. Now ask again how comes that you can read my name in hijacked threads so often. Maybe because there are so many hijacked threads around?

Nah, that would be too easy ...

 

Man your just being dam argumentative for the hell of it. There are way more upsides, support and devlopmenant wise to just use 1 language and C# is the one that is already a proper language with the most mature feature set of the bunch.

Also the multi language a really divides up the amount of support or community help people will get. Since if someone is asking for help solving a problem I will jump in of its in C# since I like the problem solving, but most won't go through the effort of trying to remember the syntax and gotchas of a other language to do so.

Also not to mention everyday there is tons of topics about people needed to convert code from 1 language to the next.

 

This is your opinion, which is fine. But it is definitely not mine. I don't need folks like you to tell me what opinion is allowed, i have my own.

Multilanguage is what made Unity big. The 50/50 between JS and C# for a long time did not come out of nowhere. And as told, even with the massive language bashing nowadays it's still 20/80.

And this has to do with what?

 

Hi Noah492, I am also newbie when I tried to learn scripting in Unity I started picking up UnityScript over C# because everyone says its easier that C#, but that is not the case; to me it was opposite C# was much easier to understand than javascript. In C# first you will understand than you code it; while in UnityScript you will do it and than you will trying to figuring out what you coded[in my point of view as a beginner guy to scripting].
but again is up to you and if you want to learn Javascript/UnityScript the best source is to start with Walker Boys Studio they have everything you need to learn unityscript from scratch.
Good luck!

 

No - it's because I read almost every thread posted in this section and I rarely see you contributing to other ones. These types of things usually don't come up and if they do you seem to be right in the middle of instigating them.

Postulating that Unity is making decisions about their future language support because "fanboys" are "hijacking" threads in order to drive the usage of UnityScript down sounds a hell of a lot like a conspiracy to me.

I'd venture to guess that the same number of people who care about the fact that you like UnityScript is roughly the same as the number who care that I like C#. Use whatever language you want, but the ironic thing is that by freaking out about fanboyism and accusing people of not being helpful you've become the least helpful person in this thread. The only one who has derailed the conversation is you.

Seriously - just stop. If you have a counterpoint to the suggestion of "Hey, if you're new to programming in general then you might find it easier to learn C# because MSDN and the internet in general can provide insight outside the scope of Unity" then simply state it and stop with the other BS.

 

I have long stopped to contribute anything at this board here. I avoid this forum usually for good reasons. This is not a friendly place anymore.

There are luckily other, much friendlier places. And that's where you can find me.

It's not Unity that makes the decision. They just react to the values. But they tolerate this stinking methods here.

Of course people keeps more and more their fingers away from JS. But not only because it is weaker, but because you will get a slap here every time you talk about JS.

Indeed, use whatever you want. But this still includes JS. And does not mean "as long as it is C#"

Why? Because i point with the finger at stinking methods? I wish even more people would do that to stop all this nonsense in the world. Too much people are quiet where they should be loud.

I would be as loud when i would see JS users hijacking C# threads. Just that this doesn't happen.

That's the magic word to keep me going. I am a Unity user as you. And have the same rights to share my opinion than you.

Seriously, you suggest to learn C# by MSDN first before even touching Unity? Just to forget 99% of the learned material immediately afterwards because you will never ever need it for your game in Unity? Yeah, sounds like perfect logic from the angle of a C# lover. That's the difference between programming and developing a game. Two different goals. The one wants to use a language. The other wants to develop a game.

My suggestion is to learn in Unity. Not by MSDN and with other external sources. You pick Unity because you want to make a game. So that's the best place to learn it.

 

Not what I was suggesting at all. I mentioned it as a resource for the language which UnityScript does not have a comparable form of. That's all.

You truly are projecting because you're spending a lot of time attacking my opinion when you'll notice that I haven't endorsed one language over the other at any point in this conversation.

Stop acting like the folks here have an alternate agenda.

 

See, that's exactly what i wanted to point out. MSDN is not a really valid source. Not a single code snippet at MSDN will let your character controller move in Unity. MSDN is as valid as a Unity resource as the Javascript API for Unity's Javascript. The relevant part is the Unity API and the available Unity tutorials and books.

Neither have i. I complain about the thread hijacking, not the choice of language. And you complain about my complaints. Which forces me to complain about your complaints. Which forces you to defend your complaints, and so on.

We could stop here, since everything is already said a thousand times. But i could bet that we will see more answers soon.

 

This I can't let slide. MSDN is a very important resource for game development. Interacting with Unity and Unity's API is only half the job. You also have to do general programming tasks that are not covered by Unity's documentation.

I wouldn't suggest learning C# directly from MSDN, there is a lot stuff that Unity does differently. But once you've got the basics of Unity down its a great place to read up on the finer details of the language, and to learn general programming tasks.

UnityScript does not have an equivalent resource. If I'm wrong here a link to the resource would be most appreciated.

 

MSDN isn't a Unity resource. But, MSDN is a .NET resource which, because Mono is a cross-platform implementation of .NET, makes it incredibly valuable.

Sure MSDN won't tell me how to move my character in Unity but what if I want to load the speed of that character from a data file that sits somewhere on the user's hard drive? What if I want to do some pathfinding and need a Priority Queue implementation or I want to run the algorithm in a separate thread?

I would challenge you to find games made in Unity that exclusively used the Unity API.

 

I just knew that i have hit a wasp nest with MSDN ^^

It is a valuable source when you use C#, and do everything but a game. But that's the point already. Usually you use Unity to make games. It's a game engine. And Unity provides everything necessary to develop a game. When you want to develop non game content then you usually don't have a reason to use Unity.

Yes, that's right. It's a proprietary, Unity specific language that doesn't exist somewhere else With all its pros and cons. Which is no problem at all as long as you develop games and stay in Unity. And then again: When you want to develop non game content then you usually don't use Unity.

Load asset. And Navmesh. All there in Unity. No need to grab code from MSDN. As told, Unity is a game engine and brings everything needed to create a game.

Not sure if you're kidding me here since even a complicated MMO game in C# can get away with exclusive Unity API code and Unity onboard tools.

But maybe we misunderstand each other here, and you mean something completely different.

 

Ballocks.

Straight ballocks.

The .Net/Mono framework is the framework used by unity. A majority of the classes available in the .Net/Mono framework are available in Unity. I use them ALL THE TIME. MSDN is a fundamental resource for me at all steps... may I be writing U/JS or C#.

See, this is why I started posting in this thread in the first place. You just have BAD suggestions dude.

You entered this thread saying that it's probably not a good idea to distinguish javascript from Unity javascript, because it might confuse OP. That's horrible idea. OP should know up front that they aren't the same so that they don't cross information when researching how to write U/JS.

Then you say stuff like:

Yes. Learn the language! MSDN is the resource from the people who DESIGNED the language!

Do note... there is a BIG difference between a language, and a framework. Sure, there's large portions of the .Net framework that won't be used (i.e. WPF, WinForms, etc). But there are also huge portions of it that will still be used regularly.

They aren't going to forget 99% of what they've learned. I come from almost a decade of software development experience in far more than game dev in unity. Business software, web servers, etc.

I've done a lot of .Net development, in both C# and VB.Net.

And I use a lot of skills I brought with me from there. You can see a lot of them at work here in the open portion of my code base I use with my unity projects:
https://code.google.com/p/spacepuppy-unity-framework/source/browse/#svn/trunk/SpacepuppyBase

That there, a good deal of it would be annoying to accomplish in U/JS. Interfaces, events, generics, linq, lambdas, etc. Just not available to me in U/JS in the fully fleshed out manner they are in C#.

 

Now I know you're full of it.

None of those fulfill the requirements I put forth.

Show me an MMO that doesn't use System.Collections.Generic.List<T>.

Hell - go look at what Physics.OverlapSphere() returns you. A Collider[] which is a System.Array. Well gee - if I wanted to learn more about System.Array where would I go to do that?

 

And you really think your bullshit is any better?

You don't say!

Completely nonsense from my angle of view. But we already know that we have different approaches. So it's not really a surprise. You're a programmer, you think in programming categories. I'm a developer, i think in development categories. My goal is not to use a language. My goal is to develop a specific piece of software. A game in most cases. And i grab the easiest tool to reach this goal.

Languages changes as quick as you change the engine. Your next engine may use Blueprints. Or C++. Or Python. Or something completely different. The stuff from your old engines and languages that you needed to learn to reach your goal is of course not wasted, it has helped you to reach the goal. But everything you learned that goes behind this goal is wasted time. Learning time is working time. And time is money. Or life time.

I'm not only doing the code. I do the graphics too. I compose the music too. I do leveldesign, storyline, everything from the first idea to the final game. That's why i cannot afford to learn everything. I've become a master over the years to really just learn what i need to reach my goal. You may live eternal, but my life time is limited you know.

And that's why i use Unity. It has everything needed already. That's where my advcice comes from. That's the difference between using a language for the sake of using this language, and developing towards a goal like a game. A language is just a tool. Learn what is necessary to reach your goal. Not everything available. This will just kill you.

Fact is, you don't need a single MSDN line in Unity to develop a game. Even complicated ones can be done with just the onboard solutions. It's imho completely bullshit to waste the time to learn stuff that you will never ever use in Unity. Languages and development tools changes as quick as your undertrouser. I've gone through a dozen over the years, and have happily forgotten most of it already.

 

So you are kidding me. Okay.

Physics.OverlapSphere is part of the Unity API. And an array does the same job than a list. Also part of the Unity API. That List is faster and more comfortable is another issue. It should definitely be part of the Unity API since it also works with JS.

 

Everything about this statement is false. You do realize that the "Unity API" is everything contained in the UnityEngine, UnityEditor, etc namespaces correct? Everything else is part of .NET/Mono and is documented on MSDN. System.Array and System.Collections.Generic.List<T> are not part of the Unity API.

 

You do know that U/JS is accessing the same framework C# is. That Array is part of .Net/Mono! Not the Unity API.

Whatever, I don't care. You're troll, tootles.

 

Enough said, I'm out.

 

I'm not saying it's the same, i say it does the same job. Remember, my point was that you don't need MSDN to develop in Unity.

See one answer below.

That Unity uses Net/Mono is another chapter. Array exists in the Unity Scripting API. : http://docs.unity3d.com/ScriptReference/Array.html

And the Unity Scripting API is the relevant part for me.

Ah this warm feeling at this board. Guess why i rarely write something here anymore

 

Warm feelings, you were the one to bring this on, if you just left the suggestion of C# use alone there would have been 1 or 2 posts about it max, not a whole thread.

Also you accuse us of giving false statements but said a few things that are just straight up incorrect about array == a list and what is mono vs the api.

The troll part came naturally since your just in it for the fight, since you even try and counter the points that don't matter and you were wrong on anyways.

Edit: What do you consider a good community? One that just rolls over and takes your opinion as true when they believe it isn't?

The community here is helpful the few times I asked a question a got a consice anwswere ussualy from a dev. I have helped out a lot of people here and on the Skype group chat as well, providing they put the effort in and formed a question about the problem they are having.

 

One that turns on the brain, and doesn't blindly flame others for just having other experience and opinions without even listening and understanding the arguments.

But it is not THE community. Most of them are in fact very friendly and open. It's a few individuals like you. What you do here is pure personal attacks, the try to discredit me (look now he even bashes the whole community), and my opinion ( Jehova he said! A List is no Array! ) in every possible and impossible way, up to direct trolling, and calling me a troll then. And what makes you even more angry is that this strategy doesn't work at me. I am not quiet, i give contra. I still point at where it stinks. And so this thread continues.

We've been through all classical steps now here. Hijacking, denying the hijacking, trying to point away from the issue, flaming, trolling. The next step is most probably to derail the thread until it gets locked. Also a very common pattern. And a stinking one.

 

Your the one that started the derail, 2 people offered the opinion that C# could be a better language for starting due to reason x. If you ignored it, it would have been 1 or 2 posts or you could have even just countered if by saying i believe unityscript is the better option for reason y. But instead you get all paranoid and say. "Welcome at the language faith war again. And as usual filled with nonsense and myths."

Also a list is not a array, it is a different kind of data structure, both in name an in how it works.

 

You will not force me to join the versus debate. That's not my point at all. When you think C# is better then that's your opinion. And the try to convince you is wasted time.

My point is the hijacking. I pointed at the stinking method to hijack JS threads with a *C# is betta dude* comment, including untrue things about JS to discredit it. And that's where it should have stopped. Not after a debate what is better. Like, hey this is a JS thread, somebody asks for resources to learn JS, so could we please stay on topic?

As it is now we do have lots of threads where you search for JS informations, just to find *C# is betta dude* answers instead.

The derailing part happened afterwards, and especially in the last three or four postings with accusations and flaming.

Indeed, and i never said something different. To put it like i would have is one of those accusations again.

 

The point of the vs debate wasnt to convince me I'm saying if you didn't approach it in your 2nd post like it some huge conspiracy there would be no more than a mention or 2 of other languges unless the op showed interest in them.

So stop reading into what isn't there.