My single biggest problem with Ruby (really, the Rails ecosystem) is churn.
My single biggest problem with Ruby (really, the Rails ecosystem) is churn. The team in charge of Go maintains full backwards compatibility for both language and core libraries. Rails, in contrast, churns so quickly that if I let a project sit fallow for even six months, the entire packaging infrastructure has been swapped out from under me, the version of Ruby on my shared host is different, and my project no longer runs. Ain't nobody got time for that.
Posted by fixermark on Feb 5, 2015, 6:17 AM
Tags
Related issues
- its like owning a personal computer in 1986.
- Not at all, actually.
- A car battery with reduced range is still perfectly useable as a storage battery for a PV system.
- Here in Argentina we are in permanent summer time GMT-3 since a long time, but we should be in GMT-4.
- You should do some basic research yourself.
- Well, actually not.
Raise real-world problems, find people facing the same issue, and discuss solutions.8,000 issues0 comments
pricing (Other)
its like owning a personal computer in 1986.
NewNot at all, actually.
A car battery with reduced range is still perfectly useable as a storage battery for a PV system.
Here in Argentina we are in permanent summer time GMT-3 since a long time, but we should be in GMT-4.
You should do some basic research yourself.
Well, actually not.
I have a 2022 mini that I use constantly.
Two observation: 1.
My single biggest problem with Ruby (really, the Rails ecosystem) is churn.
My single biggest problem with Ruby (really, the Rails ecosystem) is churn. The team in charge of Go maintains full backwards compatibility for both language and core libraries. Rails, in contrast, churns so quickly that if I let a project sit fallow for even six months, the entire packaging infrastructure has been swapped out from under me, the version of Ruby on my shared host is different, and my project no longer runs. Ain't nobody got time for that.
Comments (0)
No comments yet. Start the discussion.