Why Clojure Why Now?
Clojure is slow to start, it's not the fastest once it gets going either. It runs on the JVM and has interop with java which is my least favorite language. The stack traces are terrible, bugs are easy to create and large refactoring is difficult without a lot of well written, well thought out tests.
There's a lot to dislike about clojure, so why would I choose to write clojure and why would I start in 2016?
2015 In Review
2015 was kind of a crazy year for me, I mean I didn't jump out of a plane like I did in 2013, or get married in Hawaii like I did in 2014, it was crazy for different reasons.
First, my wife and I went to Australia and New Zealand, hiked up mountains, around lakes, camped in the middle of nowhere, saw amazing things, and had amazing experiences. That isn't to say that we didn't go other places domestically, like Havasu Falls, AZ, Yosemite and NY.
React One Way Data Flow
The one thing that makes the react way of doing things a better way than most is the one way data flow. It makes reasoning about your app simple, predictable and boring.
When new technology is exciting, that's probably a bad sign. But when it's boring, that means you should probably check it out at the very least.
Writing about modern web and app development is a moving target, my stack has changed in 6 months and it will probably change again in another 6.
So consider this the conclusion of modern web development.
And the start of an ever updating series of posts about what my current stack is like.
Stop what you’re doing. Seriously. Stop it.
The world has just changed in a significant way. Nothing is the same anymore.
React Native was fully open sourced and it is amazing. Writing mobile apps will never be the same again. In fact you shouldn’t write them without React Native anymore. Stop using Objective-C, stop using Swift, (unless you’re writing custom controls) and start using React Native.