From Node to Ruby on Rails

1. joystick

   1 57 224 10.0 JavaScript

   A full-stack JavaScript framework for building stable, easy-to-maintain apps and websites.

   

   For those looking for a legit Rails-like experience in Node: https://github.com/cheatcode/joystick

2. Judoscale

   judoscale.com featured

   Save 47% on cloud hosting with autoscaling that just works. Judoscale integrates with Rails, Sidekiq, Solid Queue, and more to make autoscaling easy and reliable. Save big, and say goodbye to request timeouts and backed-up job queues.

   

3. Opal

   2 38 4,860 9.0 Ruby

   Ruby ♥︎ JavaScript

   

   Did you try opal?

   https://opalrb.com/

   If yes, what was your opinion? I never tried it since I'd rather just work in two languages.

4. haven

   3 17 691 7.8 Ruby

   Self-hostable private blogging (by havenweb)

   

   You're welcome to adapt the AWS deployment scripts I setup for Haven[1]. I tend to adapt them when deploying other personal projects like the sites I've built for my family tree or privately hosting/sharing old family home movies.

   [1]: https://github.com/havenweb/haven/tree/master/deploymentscri...

5. motor-admin-rails

   4 14 795 6.5 Ruby

   Low-code Admin panel and Business intelligence Rails engine. No DSL - configurable from the UI. Rails Admin, Active Admin, Blazer modern alternative.

   

   I think the coolest thing about Rails is actually the great amount of high quality Ruby gems for Rails.

   For instance, you can bootstrap a powerful Admin panel for your Rails project in no time with https://github.com/motor-admin/motor-admin-rails gem.

6. rspec-mocks

   5 2 1,160 7.5 Ruby

   Discontinued RSpec's 'test double' framework, with support for stubbing and mocking

   

   It's nowhere near as equivalent, where's the behavior testing? Where stuff like allow_any_instance_of(...).to receive(...).and_return(...)? What about shared examples? How can you patch globally the current time?

   Have a look on the examples here https://github.com/rspec/rspec-mocks

7. torch.rb

   6 7 775 7.9 Ruby

   Deep learning for Ruby, powered by LibTorch

   

8. tensorflow-ruby

   7 3 381 3.0 Ruby

   Discontinued Deep learning for Ruby

9. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

10. django-unicorn

    8 54 2,499 8.4 Python

    The magical reactive component framework for Django ✨

    

    Django unicorn [0] looks like an interest concept too, similar to the htmx approach.

    [0]: https://www.django-unicorn.com/

11. foal

    9 18 1,917 7.3 TypeScript

    Full-featured Node.js framework 🚀

    

    I would guess commodity plumbing. There's a lot of work you have to do to get something like express on par with Rails or any other Rails inspired framework for which there are many in multiple languages even in nodejs.

    imo the one I like best in nodejs is Blitzjs https://blitzjs.com/

    FoalTS https://foalts.org/ is nice too and there are several other full stack frameworks like Nestjs, FeatherJs, and redwoodjs

12. redux-toolkit

    10 308 10,942 9.5 TypeScript

    The official, opinionated, batteries-included toolset for efficient Redux development

    

    We've been trying to generally discourage Redux users from using sagas in most cases. I've always felt that they were absolutely overkill for basic data fetching scenarios, and this is even more true now that data fetching libraries like RTK Query and React Query exist.

    Where sagas _do_ still make sense is highly complex async workflows, including responding to dispatched actions, "background thread"-type behavior, and lots of debouncing/throttling/etc.

    But yes, I've heard of plenty of cases where sagas made a codebase unreadable, and it's a shame that they get so heavily pushed by some early Redux users.

    FWIW, I've actually been working on designing a new "action listener middleware" that we'd like to ship in an upcoming version of Redux Toolkit. It started off as very simple callbacks, but by adding a few key primitive functions like `take`, `condition`, and `delay` I think we've been able to to come up with something that can handle maybe 75% of what sagas can do with a much smaller API surface and bundle size. I'd love to have you or anyone else using Redux take a look and give us some feedback on the current API design and let us know if there's other use cases it ought to cover:

    https://github.com/reduxjs/redux-toolkit/discussions/1648

Suggest a related project