Where do you go to learn completely new languages and ecosystems? I can’t find any resources for experienced devs out there.

• Ruby on Rails

  467 54,865 10.0 Ruby

  Ruby on Rails

  

  Well, consider it like this. You could use Go to build your own Ruby-on-Rails-esque Web framework. So, you might think, "Well, RoR is a framework that allows me to build MVC applications, so RoR must be architected with the MVC pattern." Well, no. Take a look at the source code of RoR itself and you'll notice that it's anything but MVC: it's its own architecture based on a bunch of design patterns to build a command line tool which generates an MVC framework code and then inteprets all that code when you start the Rails server (daemon / service). https://github.com/rails/rails

• Jekyll

  253 48,265 8.7 Ruby

  :globe_with_meridians: Jekyll is a blog-aware static site generator in Ruby

  

  Now, compare Rails with other Ruby projects like Jekyll (https://github.com/jekyll/jekyll) and Homebrew (https://github.com/Homebrew/brew) and you'll notice very big differences as how each project organizes its code.

• WorkOS

  workos.com

  sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• HomeBrew

  1,281 39,303 10.0 Ruby

  🍺 The missing package manager for macOS (or Linux)

  

  Now, compare Rails with other Ruby projects like Jekyll (https://github.com/jekyll/jekyll) and Homebrew (https://github.com/Homebrew/brew) and you'll notice very big differences as how each project organizes its code.

• golang-standards/project-layout

  195 45,717 6.4 Makefile

  Standard Go Project Layout

  

  To the drive the point home, you might even end up landing on this project sooner or later: https://github.com/golang-standards/project-layout. People have been quite upset about this project as there are no "standards" in the Go language: https://github.com/golang-standards/project-layout/issues/36 & https://github.com/golang-standards/project-layout/issues/117 While the intention behind the project are good and well meant, it's considered a harmful project by a good chunk of people as it shoehorns you into a narrow way or organizing Go code which isn't necessarily the most optimal way of organizing things for their particular problem domain.

Suggest a related project