Tools are sometimes supplied in such a way that they can be misused.
For instance - you shouldn't put your shoes on backwards even though "technically" it's possible. At first it might be cool, or if you're lazy it might save you some time, but down the road it will hurt you ... and the shoes ... think of the shoes!
Scripting inside web applications is a very common practice. But it does not lend itself to maintainable code or "future proof" code.
Some golden rules are keep the logic, view and data all separate.
When properly thought out - you should never need to actually script anything.
Down the road when you want to do unit testing...but your views contain logic...you will be kicking yourself after you realize you cannot make simple, common sense assertions.
Also - if someone looks inside a controller and expects to find logic and it's not there - they will be cursing your name when they have to hunt around the application for where you decided to stick it.
Scripting methods lend themselves to obfuscation and duplication.
-> You can play with it yourself in your spare time, do some projects from scratch and revisit them in a month.
-> You can learn the hard way and use scripting methods regardless of what others say.
-> You can save yourself some valuable time and focus on proper application architecture and design.
Remember, the web development industry is littered with the corpses of developers who refused to learn from people who had to mud through the trenches and save themselves some time and agony.