In my case, when I started my current project I was new to programming and working alone. Those constraints meant that I needed technologies that had a fast learning curve, great documentation, and the ability to build quickly. Rails checked all those boxes, and Heroku abstracts away most DevOps concerns, so I can focus on the app itself.
For experienced programmers (familiarity), large teams (clarity/explicitness/decentralization), or businesses with legacy infrastructure (interoperability), the constraints are different.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think in terms of constraints.
In my case, when I started my current project I was new to programming and working alone. Those constraints meant that I needed technologies that had a fast learning curve, great documentation, and the ability to build quickly. Rails checked all those boxes, and Heroku abstracts away most DevOps concerns, so I can focus on the app itself.
For experienced programmers (familiarity), large teams (clarity/explicitness/decentralization), or businesses with legacy infrastructure (interoperability), the constraints are different.