Given that Custom script action
is JASS because 1 syntax (the wrong use of words, alignment, arrangement, wording) can easily terminate the process, thus making the trigger does not work (and the map can't be saved normally (the "broken" trigger is disabled first before saving)).
Now, that is JASS.
Because in GUI, you can
never have a disabled trigger (other than the deletion of Variables and such)
Now, let's compare the usefulness
Everything in GUI can be made into JASS, but not everything in JASS can be made into GUI
For example, this trigger (we take the most simplest example of all, adding ability):
-
Custom script: call UnitAddAbility(Caster, 'Aloc')
Trigger above shows that the Caster (local variable) gets a Locust ability through the use of Custom script (JASS)
But in GUI, you can't access this feature such as adding Locust, removing 'Amov', removing 'Aatk' and so on
Also, to those who said "What can you do in JASS, I can make it into GUI", try make a system that is advance enough without using Custom script (Custom script = JASS, a scripting syntax, GUI is clicking + icon method). I bet you can't even start a 10% upon completing the system
Again, I will compare about features
You can use Unit - Move Unit (Instantly) action but that action will interrupt the current order of that unit, thus making the trigger a bit, flawed
In Custom script (JASS), you can use SetUnitX/Y which will
never stops the current order of that unit, thus we can make a fun and simple system by using this function
I'd say that JASS is pretty much more useful than GUI, only in terms of "friendly-user interface", GUI will win for sure.
It is up to you to choose which method (either clicking or typing) but each has its own pros and cons
JASS is pros on the system/trigger itself and has much more speed but for a new-learner, it's a bit hard to catch up with the interface and very, very less-user-friendly program
GUI is pros on making our work easier and doesn't have to remember each function and syntax, it will do it for you but its access is pretty much limited. This method is very much useful for the usage in real world (where we build machines that is easy to operate by user in this world (user-friendly)) meanwhile in JASS is much more useful towards programming the machine itself.
If we are to create a machine/tool, we will use JASS (C++, Java, etc) to create it and will present it in a form of GUI (Graphical-user Interface).
Look at Blizzard, they created the Warcraft III World Editor in GUI, to make people's work easier to understand and manipulate the data in it. But they did not create this tool by using GUI of course, they created it by using scripting syntaxing.
Next, let's take a look at an Antivirus System on your PC.
Once you have entered its interface, everything is easy just click click click and read here and there (straight-forward explanation words such as Scan, Delete, Quarantine, etc) (this is GUI, the method of clicking icons and easy readability)
But I'm sure they created it by using Scripting Syntaxing which is totally not GUI at all.
I'm not gonna flame or anything here, but let's take D4RK_G4ND4LF's system here for example, the
Trackables
As you can see in that thread, the usage of Custom script is
at large, if we replace (if we
can), the Custom script with the normal use of GUI action, that system won't be created as efficient as it is now (Custom script~)
So, your fate is here, choose between blue pill or red pill.
(This article is based on
the restrictions of using Custom script in GUI)