Happy Ending Update!
I’m excited to announce that I’ll be working with graph.cool on chromeless! There’s more details to come on Monday, but wanted to share that this story ended quite well. I’m going to leave the post unaltered as I think it’s a good reminder to me to not jump to conclusions so quickly. Miscommunication is a pretty easy trap to fall into.
Below is the original text from my post. Keep in mind I was pretty let down at this point in time, but have made great ammends.
When most folks talk about GraphQL features, a few things tend to surface commonly. Things like GraphiQL, declarative data, and consolidated network calls are distinguishing factors that I’m sure you’ve heard of.
The first-ever GraphQL summit is already over, and I was lucky enough to attend and hear all the great things people have to say (including from one of the authors of the specification, Lee Byron). It’s hard to boil down all the knowledge into a single post, but I’ll do my best to distribute what I saw as incredibly valuable in both maintaining and starting a GraphQL service.
I’ve recently went down the rabbit-hole wrapping a massive API with FaceBook’s GraphQL specification. Aside from learning a ton about my company’s API’s, I walked away with a lot of lessons on good conventions doing this work.
require('../../../some/dir/file_i_want.js') makes you feel somewhat uncomfortable. Though this may work in early-stage projects, and is pretty easy to do, there is pain that comes when refactoring or moving this module. That, plus it’s now harder to search and replace all the instances where
file_i_want.js is used since all the
require‘s vary just a bit. Ideally, what if we could just do
React is an open source library for “building User-Interfaces”, open sourced by Facebook. If you’re familiar with the traditional MVC pattern, React would be the “V” layer of that paradigm. I would even go so far to say that if you’re not careful, React can also become the “C” layer as well. I’ve built a pretty slick deal site with it, and I can say with fair certainty that I think that React is the way forward and all other frameworks will follow a similar pattern soon.
Sicksync is a project born out of the need to “mirror” a file-system quickly. I had issues with
scp as my workflow requires me to VPN to the east-coast, and back to my developer machine in LA. This wasn’t super ideal, and for small file changes (where you need a quick feedback loop), I was waiting up to 5 seconds to see changes happen in the browser. Booh!
Sinon actually already has a nice API for doing this out of the box without any prototype mucking:
map, and even
filter. However, there is one method that has been hiding under the radar (at least for me) for quite a while now. It’s one that functional-reactive-programming tends to use somewhat often, and that method is