Hello fellow members and UT,
Is it a good idea to split the scripting section into two (or more) subsections?
like this:
scripting
|
→ Javascript
|
→ C#
i think it will help people find answers easier, and it makes it more clear for helpers to give help in the right language (programming that is)
I voted no, because the languages aren’t all that different, and most of what happens in the Scripting section is about Unity related functions which are the same no matter what language you use.
What Dman said.
–Eric
That they can both utilize the same Unity classes/functions etc, doesn’t mean you can simple copy paste and be done with it. The rest of the logic needs to be scripted too, and that’s where the huge differences comes in 
I think this section should be more about the logic of scripting something and less about the actual code itself. So it’s fine how it is.
There really aren’t any “huge” differences when it comes to logic. They’re all pretty much the same in that regard.
–Eric
Another vote for keeping it as is.
First, splitting the scripting forum would just further fragment the forums and (for some at least) make it harder to browse threads and to keep up on everything.
Also, the differences aren’t huge, and whatever differences there are can easily be addressed right here in the scripting forum (in fact, this forum is perfectly suited to such discussions :).
On the one hand, a lot of new Unity users are also new to programming, and for them the differences between UnityScript and C# may seem pretty vast (largely because UnityScript hides some things from you that are always explicit in C#).
However, as one gains more programming experience, one tends to start to see programming languages as being more alike than different. Sure, switching paradigms entirely can take some adjustment, but UnityScript (especially in its current form) and C# are very similar.
From a learning standpoint, the emphasis should be on logic and problem solving rather than syntactical details, IMO. Obviously you need to understand the syntax and semantics of a language in order to use it effectively, but those are just details; the general processes you’ll go through in terms of solving problems and structuring your code will be essentially the same in either language.
No!
You run the risk of splitting the community, and since the problems themselves are often language independent, reducing the views a problem gets from people who are more than capable of helping.
IDIC.