musaffa

I use Ruby to create API servers these days. For a couple of APIs, I used Rails API. Now I use a combination of dry-rb, rom-rb, roda and other pure ruby libraries to create APIs. There's a growing movement within the community to move Ruby off Rails.

Before the API thing, I also developed websites with fullstack Rails. The experience with fullstack Rails and Rails API have helped me a lot to understand the requirement of a backend framework. I'm forever endebted to Rails for this.

I'm waiting for DDG to integrate dates in the search results. Date is crucial to understand how new or old the content is. This is one of the reasons why I'm not using it.

I use Neovim on daily basis. It works really well. It requires tremendous efforts and love to transform a huge archaic code base into a much modern one. Thanks, Neovim team!

Python 2 to Python 3 was a disaster. Matz has made it clear in his speeches that he wont do the same mistake in Ruby. Performance and better memory management will hopefully come in the upcoming 2.5, 2.6 and 3.0 releases. What I want from all those changes is that all my current projects should just work.

In the world of Hype, I still use Ember at the frontend and Rails API at the backend.