From Node to Ruby on Rails

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

Our great sponsors
  • Scout APM - Less time debugging, more time building
  • SonarLint - Deliver Cleaner and Safer Code - Right in Your IDE of Choice!
  • JetBrains - Developer Ecosystem Survey 2022
  • joystick

    The full-stack JavaScript framework.

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

  • Opal

    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.

  • Scout APM

    Less time debugging, more time building. Scout APM allows you to find and fix performance issues with no hassle. Now with error monitoring and external services monitoring, Scout is a developer's best friend when it comes to application development.

  • haven

    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...

  • motor-admin-rails

    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.

  • rspec-mocks

    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

  • torch.rb

    Deep learning for Ruby, powered by LibTorch

  • tensorflow-ruby

    Deep learning for Ruby

  • SonarLint

    Deliver Cleaner and Safer Code - Right in Your IDE of Choice!. SonarLint is a free and open source IDE extension that identifies and catches bugs and vulnerabilities as you code, directly in the IDE. Install from your favorite IDE marketplace today.

  • django-unicorn

    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/

  • foal

    Elegant and fully-featured Node.Js web framework based on TypeScript. :rocket:.

    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

  • redux-toolkit

    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

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts