Hi Esteban,

This is Gencer <https://github.com/gencer>. I'd like to answer solely to 
this question. *I'm not affiliated with Sequel or any organization that 
funds it, If any.*

I started Rails by performing some performance tests. It was already 
delightful. Then, as usual, I asked myself a wonderous question: Could this 
performance results can be **much** better?

Then, I started to look for alternative gems. Like alternative for Storage, 
Alternative for Rack Server (Puma in this case), ActiveRecord etc.. Most 
important factor for me was Database. I needed something;

1. Elastic
2. Performant
3. Independent from Rails framework: *Seriously*. This is something you 
should *always* consider.
4. Supported by solid crowd(*) with high quality.
5. Fun to code, easy to remember.
...
99. Syntax.. (See: 5.)
..
601. Writing it be fun and should make me *happy*.
...
 
Answer found: *Sequel*.

Performance results increased 5x. Plus, I could do anything I want with 
Sequel. Without many additional extensions. Plus, With Rails or without. 
Elegant syntax. Almost every SQL script can be written in mighty pure Ruby 
syntax using Sequel. Honestly, I hardly remember using RAW SQL used in our 
Sequel codes. I already in love with Ruby but Sequel makes me: *Wow*.

And here we go; *Dependencies*. What about Devise, What about Doorkeeper 
(oAuth2 Provider) and so on... Some of them was very immature, broken or 
very old. So, What I did? I did what I can. *Contribute... *
heartcombo/devise 
<https://github.com/heartcombo/devise/pulls?q=author%3Agencer+>, 
nbulaj/doorkeeper-sequel 
<https://github.com/nbulaj/doorkeeper-sequel/issues?q=author%3Agencer>, 
TalentBox/sequel-rails 
<https://github.com/TalentBox/sequel-rails/issues?q=author%3Agencer> and 
many more...

*This is how community grows.*


*> What have been your big issues with Sequel? Has anyone ever migrated 
from Sequel to ActiveRecord?*

My company. *Me*. And I never ever think to go back for ActiveRecord. 
Sequel is a *masterpiece*.

Sequel used on our company since 5 years more than 20+ projects and we 
never ever had any problem. Never feel anything missing.

*> It looks like sequal-papertrail 
<https://github.com/lazebny/sequel_paper_trail>, a gem for tracking changes 
to models, is five years out of date.*

 Well, umbrellio/sequel-bulk-audit 
<https://github.com/umbrellio/sequel-bulk-audit>. No regrets here for this 
either even I have contributions there Performance improvements 
<https://github.com/umbrellio/sequel-bulk-audit/pull/4>! (You may see nor 
merged but they already taken my changes into account and commit the 
changes themself...)

Now lets talk about those. Seriously, Sequel Community is small. Small but 
highly quality. *Alive*. Your startup company working with is probably one 
of them. Sequel itself is a gem. Not a Ruby gem but a *gem*. Most people 
fears about compatibility, maintainability and etc about Ruby gems outside 
of Rails.. Have you ever look at GitLab's Source code lately? They use 
ActiveRecord and they have many patches for it. Heck, In fact they have 
many patches for Rails' all modules :) Last I remember, we highly unlikely 
patch the Sequel. Is patching a bad thing? *Absolutely not*. But this means 
no serious business stick with default. Somehow, they just make things fit 
in their business. Simply; Lets stop worrying about other gems like 
Sequel's popularity or Maintainability of their extensions and focus on *What 
we can achieve with it*.

TL;DR: We/I quite faced with some problems but we just did overcome: 
Contribute and keep things alive.

(*) Jeremy Evans, is himself, is one man squad. If someone asks me how 
should a software developer be, Jeremy Evans would be the answer. *Believe 
me*. (*Another person in this class would be Matt Fausey from Chilkat 
Software. - No ads soever!)*

I am a developer who live in Edge. I don't know you but just enjoy the 
Sequel and write awesome things with it. In fact, we are just moving to 
Roda, Rodauth and etc.. More Sequel ecosystem... See: janko/rodauth-rails 
<https://github.com/janko/rodauth-rails>

Hoping this helps you *a bit*.

Sincerely,
Gencer.



On Tuesday, August 30, 2022 at 1:03:36 AM UTC+3 Esteban wrote:

> I just joined a startup that's been using Sequel instead of ActiveRecord, 
> and I'd never heard of Sequel before joining. I'm really impressed with the 
> stability and speed of Sequel over ActiveRecord. Good Job Jeremy.
>
> One potential issue I've noticed has been integration with gems which 
> assume everyone uses ActiveRecord. It looks like sequal-papertrail 
> <https://github.com/lazebny/sequel_paper_trail>, a gem for tracking 
> changes to models, is five years out of date. Devise, a gem for 
> authentication, occasionally has regressions 
> <https://github.com/heartcombo/devise/search?q=sequel&type=issues>.
>
> What have been your big issues with Sequel? Has anyone ever migrated from 
> Sequel to ActiveRecord?
>

-- 
You received this message because you are subscribed to the Google Groups 
"sequel-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sequel-talk/bf40a5bc-320f-4544-9280-fd883161e491n%40googlegroups.com.

Reply via email to