vdombr

3 ms·

1. 1.▲
   by vdombr 1mo ago

   And I'm personally not happy with that. To manually test something, we have QA, to shape business requirements, we have a business analyst and a product owner. Now a developer needs to be a 3-in-1 person?
2. 2.▲
   by vdombr 2mo ago

   It was mostly HTTP/JSON tests with some sort of validation, basic auth and logging. I think Ruby is used the most for this. I see many companies switching from Ruby to Go or FastAPI for this basic web services stuff, and I have no idea
3. 3.▲
   by vdombr 2mo ago

   Thanks! That was exactly my point. The ruby community has made many performance improvements since 2.0, including JIT compilation, fibers and ractors.
4. 4.▲
   by vdombr 2mo ago

   It’s more like goroutines or other lightweight concurrency mechanisms. If threads are OS-level concurrency primitives, fibers are scheduled within Ruby itself, which makes them much more efficient than threads. In fact, I got the following