thank you so much for your contributions, i've been using sinatra since version 1.4 or so back in 2011, that was when i first started using ruby to develop most

thank you so much for your contributions, i've been using sinatra since version 1.4 or so back in 2011, that was when i first started using ruby to develop mostly dynamic web apps and rest apis. back then i just felt rails was too heavyweight and liked the simplicity and freedom from choosing what i used in my stack, my favorite stack ended up being sinatra/haml/sequel, it was so easy and fast to get projects up and running, rspec was also pretty nice for testing. the reason why i eventually went away from ruby was two-fold, the primary reason being performance, i was using event machine for asynchronous work, but it felt like it was an after thought, not really that powerful and a bolt on after the language matured. with golang this was built in from the beginning into the language. the second reason, which is almost as equally important, was the deployment, with golang, all i have to do is copy a binary over to my servers, i don't even need a compiler or runtime interpreter, it simplifies my server deployments. but with ruby, i had to leverage rbenv and deploy this everywhere. i still recommend that folks use ruby if you need something developed quickly that's quite powerful, the libraries are extensive and great, and sinatra is excellent because it gives you the freedom of choice, unlike rails, which i used a lot also, but felt that rails was too heavyweight, it tried to force everything on me.