ioquatix | 1 year ago | on: What's New in Ruby on Rails 8
Have you actually benchmarked this and published the benchmarks somewhere?
ioquatix's comments
ioquatix | 2 years ago | on: Philosophy of Coroutines
https://github.com/socketry/async uses coroutines and I think in general it’s been a great model with very few downsides in practice.
ioquatix | 2 years ago | on: Every Signature Is Broken: Insecurity of Microsoft Office’s Ooxml Signatures
Sounds like a useful feature to me.
ioquatix | 3 years ago | on: All programming philosophies are about state
"All Programming is about State". All code is state. All state is code. It's turtles all the way down.
ioquatix | 3 years ago | on: Efficient IO in Linux with io_uring [pdf] (2019)
It's adopted by Ruby: <https://github.com/socketry/io-event> which is used by <https://github.com/socketry/async> which is part of the Ruby 3+ Fiber Scheduler for light weight concurrency. It shows promising performance.
ioquatix | 4 years ago | on: Async Ruby
The fiber scheduler also hooks into the `Timeout` module to provide safe(r) timeouts using the event loop.
ioquatix | 4 years ago | on: Async Ruby
Every task is a promise you can wait on for the result. Concurrent fan out is trivial.
ioquatix | 4 years ago | on: Async Ruby
That's pretty accurate.
ioquatix | 4 years ago | on: Async Ruby
The gem namespace was transferred to me some time around 2017.
ioquatix | 4 years ago | on: Async Ruby
ActiveRecord does work but it’s hugely limited because they have explicit per-thread resource pools which we can’t get around very easily.
ioquatix | 4 years ago | on: Async Overloading
> When designing an API in Rust which performs IO, you have to make a decision whether you want it to be synchronous, asynchronous, or both.
Why must that be true? Why can't you write the interface once, and have concurrency be an implementation detail?
ioquatix | 4 years ago | on: Carbon dioxide peaks near 420 parts per million at Mauna Loa observatory
So what are we going to do about it?
ioquatix | 4 years ago | on: Chinese paddlefish, one of the world's largest fish, declared extinct
Extinction :(
ioquatix | 4 years ago | on: Ruby 3 JIT can make Rails faster
Nope, they are totally different. However, the DB gem is an interface/driver similar to PHP's PDO, while AR is a set of drivers, interfaces and high level ORM interfaces. In theory, one could probably use DB as a driver under AR. One person even basically uses AR to generate SQL and then executes it with the DB gem, which I thought was pretty clever.
ioquatix | 4 years ago | on: Ruby 3 JIT can make Rails faster
The fiber scheduler solves this as concurrent execution is now built into the core of Ruby 3.
ioquatix | 4 years ago | on: Ruby 3 JIT can make Rails faster
Also, it turns out the `pg` is also partially non-blocking. But AR may need to improve their connection pool implementation.
ioquatix | 4 years ago | on: Ruby 3 JIT can make Rails faster
Non-blocking Postgres https://github.com/socketry/db-postgres
Non-blocking MariaDB https://github.com/socketry/db-mariadb
ioquatix | 5 years ago | on: Git as a NoSql Database (2016)
Yes, it was. It was originally a front end and back end (query server) for CouchDB. But CouchDB 2 really went in a different direction to what I expected with query servers so I gave up and decided to pivot in a different direction with the code base.
ioquatix | 5 years ago | on: Git as a NoSql Database (2016)
For the lolz: https://github.com/ioquatix/relaxo
ioquatix | 5 years ago | on: Why Wasn't Ruby 3 Faster?
This problem is being addressed in Ruby 3.
page 1