Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

ATOM-Group's avatar

It's quite ironic that a PHP framework provides the best possible front-end workflow tool...

I've been trying to learn modern JS and front-end workflow and I am having a shit of a time doing it because there are dozens of ways of doing it.

Gulp vs grunt vs bower. Webpack vs browserify. Different people recommend different module patterns:

require(...);

import X from Y

define(...., function())

Some people have all their examples in CoffeeScript. Some have all their examples in TypeScript. Ask 50 different developers what their gulp files look like, and you'll get 25 different gulp files and 25 different grunt files...

Not to mention dozens of frameworks with varying degrees of completeness and stability... it's utterly maddening. If front-end development is the surface of a stormy sea, PHP is like the stable, calm ocean beneath.

But what I've found interesting in all of this, is that Elixir is the most sane and simple front-end tool I've used yet, and it's built for use in a PHP framework...

0 likes
2 replies
JeffreyWay's avatar

Yeah, Elixir rocks.

If your app is very specific and needs a lot of unique configuration, you might be better off writing your own Gulpfile, but for your typical projects, it's so nice to be able to write mix.sass('app.scss'), and be done with it.

2 likes

Please or to participate in this conversation.