I wrote Sidekiq, which Oban is based on. Congratulations to Shannon and Parker on shipping this!
I had to make this same decision years ago: do I focus on Ruby or do I bring Sidekiq to other languages? What I realized is that I couldn't be an expert in every language, Sidekiq.js, Sidekiq.py, etc. I decided to go a different direction and built Faktory[0] instead, which flips the architecture and provides a central server which knows how to implement the queue lifecycle internally. The language-specific clients become much simpler and can be maintained by the open source community for each language, e.g. faktory-rs[1]. The drawback is that Faktory is not focused on any one community and it's hard for me to provide idiomatic examples in a given language.
It's a different direction but by focusing on a single community, you may have better outcomes, time will tell!
Thanks Mike! You are an inspiration. Parker and I have different strengths both in life and language. We're committed to what this interop brings to both Python and Elixir.
Faktory was a big influence/inpiration for Ocypod[0], a job queuing system I wrote a few years back (similarly language agnostic). Much appreciated for making it all open source.
Maybe you didn’t intend it this way, but your comment comes across as an attempt to co-opt the discussion to pitch your own thing. This is generally looked down upon here.
It was an off-the-cuff comment and probably not worded ideally but the intent was to discuss how Oban is branching off into a new direction for their business based on language-specific products while I went a different direction with Faktory. Since I came to the exact same fork in the road in 2017, I thought it was relevant and an interesting topic on evolving software products.
Knowing Mike and his work over the years, that is not the case. He is a man of integrity who owns a cornerstone product in the Ruby world. He is specifically the type of person I want to hear from when folks release new software having to do with background jobs, since he has 15 years of experience building this exact thing.
By “based on” I don’t mean a shared codebase or features but rather Parker and I exchanged emails a decade ago to discuss business models and open source funding. He initially copied my Sidekiq OSS + Sidekiq Pro business model, with my blessing.
This is absolutely true (except we went OSS + Web initially, Pro came later). You were an inspiration, always helpful in discussion, and definitely paved the way for this business model.
I’ve been using a nano iPad Pro for a year or so now and fingerprints have never once bothered me. The cleaning cloth works great. I love the nano screen as reflections are just not a problem any more.
I just bought an iPad Pro and really wanted the nano-texture, but that would mean I would also have to upgrade the storage and it made the device too expensive for me.
I bought a Paperlike 3 screen protector and it's ok. Not great, not terrible.
Yeah, the screen is a very costly upgrade but since I'm on it so many hours per day, I was willing to pay the price. Glare is just never a problem, no matter where I am.
"Flophouses" or SROs used to provide affordable housing for young people new to a city, single people, workers, etc but they depend on density and transit to be cheap. They were largely made illegal in the mid-20th century. Land use/zoning laws are why we've built nothing but car-dependent suburbs for the last 50 years.
They are still around but less common. Some progressive cities like Austin calls them a "Boarding House"[0] I'm not sure if there is a unit cap where something like your historical tenement housing could happen like in Manhattan. It's the same idea just a different format.
In Copenhagen, the vast majority of people park their bikes on the street using only a cafe lock (frame mounted, immobilizes the rear wheel). The bikes are generally nothing special, old rusty junkers, with one or three gears. E-bikes flatten terrain but also you need an indoor place to store it and they become a magnet for theft. A cheap bike you can ride to the Metro and leave in the elements is versatile in a way e-bikes are not. (I say all this as a massive e-bike fan living in a very hilly US city who recently visited Copenhagen and adored its bike culture.)
We once rented bikes in Copenhagen, they all looked like they were fresh from the junk yard. We had to try several to find ones where at least one of the brakes was still working. It was a horrible experience, and we tried several different places. That was after we found out that the public bikes that were supposed to be available all over the city had all been stolen.
No, but I think it’s because e-bikes have only come into widespread use in the last decade. It takes decades to build high quality infrastructure and those countries are the ones that could make bikes work for the general population before e-bikes were available.
I had to make this same decision years ago: do I focus on Ruby or do I bring Sidekiq to other languages? What I realized is that I couldn't be an expert in every language, Sidekiq.js, Sidekiq.py, etc. I decided to go a different direction and built Faktory[0] instead, which flips the architecture and provides a central server which knows how to implement the queue lifecycle internally. The language-specific clients become much simpler and can be maintained by the open source community for each language, e.g. faktory-rs[1]. The drawback is that Faktory is not focused on any one community and it's hard for me to provide idiomatic examples in a given language.
It's a different direction but by focusing on a single community, you may have better outcomes, time will tell!
[0]: https://github.com/contribsys/faktory [1]: https://github.com/jonhoo/faktory-rs
reply