Originally appeared on Tim Riley.
This week I finished a particularly satisfying piece of work: adding request body parsing to Hanami Action. This finishes the story we started back in Hanami 2....
Originally appeared on Tim Riley.
This week I finished a particularly satisfying piece of work: adding request body parsing to Hanami Action. This finishes the story we started back in Hanami 2.3, where we significantly improved Hanami Action’s formats handling. Now you can also use formats to ensure your bodies are appropriately parsed for your expected media type handling.With this change, Hanami Actions can now serve as fully standalone mini Rack apps, along with everything you’d expect from params handling. It also means we can do away with the one-step-too-far-removed-and-awkward-to-configure body parser middleware that until now we’ve needed in full Hanami apps. Step by step, things get cleaner and better…
I had the pleasure of reviewing a range of things…
In this episode, we look at a few different ways of improving the speed of a page. There are many paths to take. Some of them leaves a lot of optimizations on the table, whereas others are prematu...
In this episode, we look at a few different ways of improving the speed of a page. There are many paths to take. Some of them leaves a lot of optimizations on the table, whereas others are premature and adds complexity. https://www.driftingruby.com/episodes/optimizations
Originally appeared on Drifting Ruby Screencasts.In this episode, we look at a few different ways of improving the speed of a page. There are many paths to take. Some of them leaves a lot of optimi...
Originally appeared on Drifting Ruby Screencasts.In this episode, we look at a few different ways of improving the speed of a page. There are many paths to take. Some of them leaves a lot of optimizations on the table, whereas others are premature and adds complexity.
We just open-sourced wreq-ruby, the first production-ready Ruby HTTP client with real browser TLS/HTTP2 fingerprinting. It emulates the exact signatures of Chrome, Firefox, Safari, Edge, Opera, an...
We just open-sourced wreq-ruby, the first production-ready Ruby HTTP client with real browser TLS/HTTP2 fingerprinting. It emulates the exact signatures of Chrome, Firefox, Safari, Edge, Opera, and OkHttp, so your requests pass as real browser traffic. Built in collaboration with the original wreq maintainer, powered by Rust with BoringSSL. Until now, Ruby had no production-ready solution for this. Pre-compiled native gems available for Linux and macOS.