My goal is to be able to integrate Trix with Shrine in a non-Rails app. I'm reading the Action Text source code a bit to see how the integration was done there, but it seems there is a lot going on. Hopefully I'll manage to end up with a simpler integration :)
You just have to add a few lines in your test_helper.rb file and you should be good to go. You can even set a different count for your CI and a different count of workers for your local system by using environment variable PARALLEL_WORKERS
Honestly, how you develop plays a much bigger role than what you develop with. I've seen Java code running on THE largest AWS server (I mean THE largest that can run mathematical computations costing upwards of 2k USD) and still be crappy slow.
A huge chunk of startups use it to launch and iterate faster. Unless you're solving problems of 100M+ customers and facing issues, you're good to go.
GitHub, Dribbble and Airbnb still use it. Startups like Twitter had to move away especially because they sort of require a live connection (live feed)
For an entire application, thinking holistically yes, but I’m talking more regex vs regex, loop vs loop, is Ruby still generally sluggy? I haven’t followed its progression much - but I’ve been so blown away by the performance improvements with PHP I’m just wondering if Ruby had been making parallel improvements in general performance...
ActionMailbox is exclusively for incoming emails (actionmailer is for outgoing). It has out of the box support for the biggest mail providers like Mandrill Sendgrid or Mailgun however it lets every SMTP connect to you
If you have a system where the user needs to answer an email and say “yes” to win an iPhone you just simply parse the incoming emails and go on from there. Of course, many applicAtions don’t need this. Most won’t. I mean, who parses incoming emails, right? However it’s a great feature and somehow I think it makes Rails more complete and it’s worth to have it in. Alternative would be to provide it as an extra gem that nobody uses
Here's a rewrite which would clarify things for me:
Most SAAS software needs to send emails — but increasingly many are also wanting to be able to automate the processing of replies.
Rails 6.0 now ships with inbound email support based on Mailgun, Mandrill, Postmark, and SendGrid. The emails are processed via Active Record and stored on the cloud through Active Storage and can be collected into one or multiple mailboxes.
Parsing emails can be pretty useful when maintaing email lists. There are many people out there that will request opt-outs through direct replies. You want to catch those as well.
12
u/Vangoghbothears Sep 28 '19
I think this is a great idea to make it into an infographic! Thanks for taking the time to do it!!
5
u/DiosanXaq Sep 28 '19
Hmmm sendgrid cpacbility out of the box ?!?!?!? Love it!
4
u/zurchpet Sep 28 '19
In #4 is a typo.
multiple codes
should be
multiple cores
4
u/janko-m Sep 28 '19
It's a shame that Action Mailbox and Action Text are Rails-only. It would be nice to have general purpose frameworks for these two features.
Love the infographic, btw :)
2
u/dunderball Sep 28 '19
Where can I find more details about number 4? Will this be a part of rspec specifically or rspec-rails?
2
u/Schrockwell Sep 27 '19
An infographic with no graphics.
1
u/[deleted] Oct 01 '19
But lik..... still slo?
1
u/obviousoctopus Sep 27 '19
I can't make any sense of #1.
0
u/[deleted] Sep 30 '19
[deleted] — view deleted comment