So why do we hate JavaScript and Node.js? This is elegant.

>>62372664
>arrows going everywhere
spaghetti code

>>62372943

But the arrows can only go in and out of the components.

>>62372943
It's planar graph, my dude. Spaghetti requires tangled arrows.

File: flux-simple-f8-diagram-explained-1300w.png (139KB, 1300x708px) Image search: [Google]

139KB, 1300x708px

>>62372943
OP's picture just has a poor layout.

Flux architecture is actually very elegant and simple to follow.

>>62373015
Looks like MVC familia.

>>62373049
MVC is more complicated and harder to debug.

Nice thing about flux is everything only flows in one direction.
And (ideally) the entire state is stored in just one place.

>>62373116
I honestly don't see the difference except that this enforces one way data flow?

>>62373193
It's not a world shocking difference that totally throws out decades of software development, If that's what you were expecting.

More an improvement on MVC.

Also not limited to JS, btw.

>>62373237
Well React/Flux evangelists could've fooled me. Still no one's ported this to any other platform, but I'm sure that's just the momentum behind JS at the moment.
It really is a shame that native toolkits are all stuck in the late 80s in terms of programming paradigms.

JS represents the normie-sation of programming. So people who know only JS reinvent the wheel and try to force it into places it doesn't belong. JS on microcontrollers is absurd. And know what we used to call a transpiler? A compiler.

There's no other reason all these technologies would be based off a flawed language made to sell a browser.

>>62373285
I think using a framework/toolkit at all is the problem.

I use standalone tools that I happen to like, and tie them together in my architecture of choice.
But I could easily switch out some tools, or even change the architecture (I probably won't do the latter mid project though).
Kinda like the Linux philosophy.

>>62373352
The problem is that JS, especially after ES6, is "good enough."

Expect JS to gain even more market share before the backlash starts to have any impact.

>>62372664
node.js is kinda clever. It's a good idea to have javascript on the backend as well.

>>62373368
Yep, it would be great. Part of it is legacy and part of it is that JS is just better at gluing things together.
Just my perspective from a shitty enterprise software dev.

Side note: Fuck OO, and reflecting the world in your object model. It's a poison that's given everyone 15+ years of shit libraries.

>>62373637
>It's a good idea to have javascript on the backend as well.
Why?

>>62373775
To get those frontend devs to do work on the backend without making them learn more languages. As a business solution it's great.

>>62373775
Switching back and forth between languages introduces unnecessary confusion.

I stopped writing the backend in Python for this reason.

>>62373775
Lets you re-use some code (especially nice for data serializing since it can go both ways)
And it's easier to switch between working on front and back end.

>>62373775
Front end devs already know JS. JS for backend potentially enables businesses to flood the employee market, driving down wages.

File: 1405381737120.jpg (64KB, 600x558px) Image search: [Google]

64KB, 600x558px

>>62372664
>Mixing templates and js code