Flux solutions compared by example
Nowadays Flux (together with React.js) is one of the hottest topics in the tech world.
When people talk about Flux they mean more of a pattern than a framework. But Javascript community has already made a solid input into it and developed different approaches for working with Flux in order to bring some structure and “frameworky” feel. The first thing which comes to mind after some exploration – there are too much Flux libraries right now. In spite of that let’s try to compare some of them.
I had many laughs while reading this. All the lols. Especially:…
I had many laughs while reading this. All the lols. Especially:
“You get to know your useful tools, then you look around, and there are some handy new tools nearby and those tools show you the bottomless horror that was always right next to your bed.”
First run at a generalized “Something’s gone wrong!” mechanism for display inside WordPress
I’m finding that I need something like this in a lot of projects, so I figured I’d build something out that could be reused and shared between plugins, the idea is a class that can be called inside a plugin or theme unless already active.
https://github.com/PressForward/pressforward/blob/3.1.x/includes/specimen-box.php
Next step is to take it as its own repo for others to pull and use.
“Too often I see smart people stuck at the beginning of something. Flow rewards starting. Look for a…”
“Too often I see smart people stuck at the beginning of something. Flow rewards starting. Look for a familiar pattern, and go. Sometimes your initial idea doesn’t work out and you have to start over. And that’s ok. It’s way better to try something, fail and fix it than it is to still be stuck at the beginning.”