4 ms·

I'm a fan of sidkiq but holding out using a different more atomic redis command for 'pro' is pretty lame - it's closer to 'intentional gimping' than 'open-core'

I'm a fan of sidkiq but holding out using a different more atomic redis command for 'pro' is pretty lame - it's closer to 'intentional gimping' than 'open-core'.

nikanj 10y ago
Demo-, trial-, hobbyist- and home-editions of software have always been intentionally gimped. From a pure engineering point of view, there's no inherent reason to not give everyone the "best" bits.
dasil003 10y ago
Obviously choices have to be made, I don't understand how you can begrudge the guy his living. It's certainly better than random hot developer tool startup that takes VC funding, grows like crazy, then either implodes, gets purchased, or changes their policies so you get screwed by depending on them. With Sidekiq I feel pretty good about relying on it compared to a lot of stuff out there.
- siliconc0w 10y ago
  I don't begrudge anyone. You can choose a commercial license and get paid. But people don't choose commercial licenses because they want adoption and free support of their tools. I have nothing against 'open-core' with 'expansion-packs' that actually target niches and require development effort - switching redis commands doesn't meet that requirement for me and thus is fails into the category of 'intentional gimping' which I think takes advantage of your community who isn't getting any of that 80k/mo. That said, Sidekiq is, by no means, egregious here but it's a problem which deserves to be called out.
sudhirj 10y ago
It's called running a business. And because it's open source, anyone is free to fork Sidekiq and make a version that uses the atomic Redis commands. What people are choosing to pay for is Mike.
asymmetric 10y ago
You can fork Sdekiq and add the Redis command yourself - actually I'm wondering if someone has already done it.
mperham 10y ago
Sidekiq fetches jobs same as how Resque fetches, which is based on what is easy to do in Redis: LPOP. It's been that way since day one. Adding reliable fetching is much, much harder than you think. It's taken me years to get it right.

I'm a fan of sidkiq but holding out using a different more atomic redis command for 'pro' is pretty lame - it's closer to 'intentional gimping' than 'open-core'.

nikanj 10y ago

Demo-, trial-, hobbyist- and home-editions of software have always been intentionally gimped. From a pure engineering point of view, there's no inherent reason to not give everyone the "best" bits.

dasil003 10y ago

Obviously choices have to be made, I don't understand how you can begrudge the guy his living. It's certainly better than random hot developer tool startup that takes VC funding, grows like crazy, then either implodes, gets purchased, or changes their policies so you get screwed by depending on them. With Sidekiq I feel pretty good about relying on it compared to a lot of stuff out there.

siliconc0w 10y ago
I don't begrudge anyone. You can choose a commercial license and get paid. But people don't choose commercial licenses because they want adoption and free support of their tools. I have nothing against 'open-core' with 'expansion-packs' that actually target niches and require development effort - switching redis commands doesn't meet that requirement for me and thus is fails into the category of 'intentional gimping' which I think takes advantage of your community who isn't getting any of that 80k/mo. That said, Sidekiq is, by no means, egregious here but it's a problem which deserves to be called out.

sudhirj 10y ago

It's called running a business. And because it's open source, anyone is free to fork Sidekiq and make a version that uses the atomic Redis commands. What people are choosing to pay for is Mike.

asymmetric 10y ago

You can fork Sdekiq and add the Redis command yourself - actually I'm wondering if someone has already done it.

mperham 10y ago

Sidekiq fetches jobs same as how Resque fetches, which is based on what is easy to do in Redis: LPOP. It's been that way since day one. Adding reliable fetching is much, much harder than you think. It's taken me years to get it right.