You shouldn't invoke setup.py directly

Re:You shouldn't invoke setup.py directly by k1rcher on Tuesday October 19, 2021 @11:36AM (#28919307)

I began my professional career writing Rails apps (previous experience in software was cobbled together Python and .NET scripts), and 1-2 years later made the full transition to Django and Python, mostly because my mentors and friends at the time were writing projects in Python. Plus, the job market for fullstack Python devs was much more lucrative at the time.

I must say though, I do miss Ruby and the syntactic sugar, packaging/dependency system, etc. The transition itself was also very painless. I’m keen on checking out the current state of Ruby and/or Rails 4-5 years later, as I’m sure much has changed!

The two main frameworks I use(d) have relative equivalents in both languages which is super nice (Flask and Sinatra, Rails and Django). Right now I’m in the FastAPI craze, but perhaps I’ll opt for Rails for my next personal project.

[ Parent | on HN ]

Re:You shouldn't invoke setup.py directly by sethhochberg on Tuesday October 19, 2021 @12:34PM (#28920087)

Honestly, I don't think you'll find it feels like much has changed at all - modern Rails is still pretty consistent with Rails 4+, modern Ruby is still pretty consistent with Ruby 2+. Its one of my favorite things about the language and framework combo, it feels like once we got past Ruby 1.9.3 and Rails 3 things have been pretty well locked in.

There are new niceties and improvements, but bundler is still bundler, everything is still an object, etc.

[ Parent | on HN ]