It’s fish shell, and yeah my dotfiles are public: https://github.com/dickeyxxx/dotfiles
I’ve seen autojump before, fasd looks useful but it doesn’t look like it supports my shell (fish).
My argument for why I think gh is better though is because it’s not just helping you navigate faster, it forces you to structure your projects in a predictable way while also helping you navigate faster. It’s not that I clone…
This article is almost 2 years old now, so take that into account. I’ve also been almost entirely been doing CLI development since I wrote this, so I don’t know much about the state of the world of front-end development anymore either. This approach might still be good with Angular 2 and other tools now available, maybe not. I’m not sure.
My limited understanding of GraphQL is that it is still all HTTP, which should work well with our platform. There isn’t anything I’m aware of that would prevent you from using GraphQL on Heroku. In fact, I think we might even use GraphQL internally for some things, though nothing I’ve directly worked on.
I would try it out, maybe write a blog post about how well it works or doesn’t work.
Those are all thread and process models that do not support nearly the same level of concurrency as you get with continuation-passing style or promises. That would require something like twisted.
If you like Ruby, stick with Ruby. It’s not going anywhere anytime soon. There are still developers paid to write Perl and ColdFusion today. This article is a criticism of Rails, and criticisms could be drawn towards any language or framework. Don’t take it as an admonition against using it. (Especially not using Ruby, which this article isn’t about)