Mike Perham, Creator of Sidekiq: From Employment to Independence
codecodeship.com
Mike Perham, Creator of Sidekiq: From Employment to Independence
1–10 of 115 posts
Re: Mike Perham, Creator of Sidekiq: From Employment to Independence
#2I guess Matsumoto should have charged for Ruby. I'm sure Mike Perham and Derek Kraan would have been glad to pay for that and that the Ruby community would be in a strong and healthy shape.
Re: Mike Perham, Creator of Sidekiq: From Employment to Independence
#3I guess Matsumoto should have charged for Ruby. I'm sure Mike Perham and Derek Kraan would have been glad to pay for that and that the Ruby community would be in a strong and healthy shape.
Well Sidekiq is free to use. It's only the pro version that he charges and the free version code is open source.
I don't see the problem in having that kind of business model, it still allows the community to thrive and offers entreprises a way to have premium support.
Plus it allows him to invest more time in maintaining the free version.
Re: Mike Perham, Creator of Sidekiq: From Employment to Independence
#4I guess Matsumoto should have charged for Ruby. I'm sure Mike Perham and Derek Kraan would have been glad to pay for that and that the Ruby community would be in a strong and healthy shape.
To be fair to Mike, Sidekiq is absolutely free. He sells an enterprise version for money, that comes with support.
Re: Mike Perham, Creator of Sidekiq: From Employment to Independence
#5I guess Matsumoto should have charged for Ruby. I'm sure Mike Perham and Derek Kraan would have been glad to pay for that and that the Ruby community would be in a strong and healthy shape.
To be fair to Mike, Sidekiq is absolutely free. He sells an enterprise version for money, that comes with support.
And he only started because companies were telling him it would be easier if they could just pay him.
Re: Mike Perham, Creator of Sidekiq: From Employment to Independence
#6Earlier quoted context omitted.
To be fair to Mike, Sidekiq is absolutely free. He sells an enterprise version for money, that comes with support.
And he only started because companies were telling him it would be easier if they could just pay him.
Anyone who has a free thing, sell something that produces an expendable invoice or receipt. Makes it easy to use company funds to pay for company work. “Buy me a coffee” buttons don’t really cut it.
Re: Mike Perham, Creator of Sidekiq: From Employment to Independence
#7I guess Matsumoto should have charged for Ruby. I'm sure Mike Perham and Derek Kraan would have been glad to pay for that and that the Ruby community would be in a strong and healthy shape.
People need to eat man, doing something for free is a luxury not many possess. We can see how messed up the financial situation is for a lot of Open Source devs and their lives would be better if they were charging money instead of subsisting off grants and donations.
I don't even necessarily disagree with your point that without being free those things wouldn't have taken off but we need to find a way to strike a balance in the developer community.
Sidekiq having a free version and an enterprise version walks an okay middle line imo.
Re: Mike Perham, Creator of Sidekiq: From Employment to Independence
#8I guess Matsumoto should have charged for Ruby. I'm sure Mike Perham and Derek Kraan would have been glad to pay for that and that the Ruby community would be in a strong and healthy shape.
Well Sidekiq is free to use. It's only the pro version that he charges and the free version code is open source. I don't see the problem in having that kind of business model, it still allows the community to thrive and offers entreprises a way to have premium support. Plus it allows him to invest more time in maintaining the free version.
I have no problem paying for the Pro version, but one if its marketing pitches is "enhanced reliability", which is a wild marketing spin on "the free version will lose jobs in fairly common scenarios".
In sidekiq without super_fetch (a paid feature), any jobs in progress when a worker crashes are lost forever. If a worker merely encounters an exception the job will be put back on the queue and retried but a crash means the job is lost.
Again, no problem paying for Pro, but I would prefer a little more transparency on how big a gap that is.
Re: Mike Perham, Creator of Sidekiq: From Employment to Independence
#9I guess Matsumoto should have charged for Ruby. I'm sure Mike Perham and Derek Kraan would have been glad to pay for that and that the Ruby community would be in a strong and healthy shape.
Not by Matz, but there are paid versions of Ruby out there.
Re: Mike Perham, Creator of Sidekiq: From Employment to Independence
#10Earlier quoted context omitted.
Well Sidekiq is free to use. It's only the pro version that he charges and the free version code is open source. I don't see the problem in having that kind of business model, it still allows the community to thrive and offers entreprises a way to have premium support. Plus it allows him to invest more time in maintaining the free version.
I have no problem paying for the Pro version, but one if its marketing pitches is "enhanced reliability", which is a wild marketing spin on "the free version will lose jobs in fairly common scenarios". In sidekiq without super_fetch (a paid feature), any jobs in progress when a worker crashes are lost forever. If a worker merely encounters an exception the job will be put back on the queue and retried but a crash mea…
how often do your workers crash? i rely heavily on sidekiq and don't think I see this very often, if ever.