Ironically, you are posting this question to a site which uses Rails, IIRC. So it is at least as relevant as your question, as of this date.
I read from other responses that this should be framed as "will this Rails job hurt my employability later?" I think this question is highly suspicious for the assumptions it makes. If I could give a yes or no answer to this question, it would mean that the only skill relevant to future jobs is whether you knew particular frameworks well (for example, Django instead of Rails). And in fact, (if you can) I would run far away from jobs which had framework experience as hard requirements (instead of "nice to have"s). It means they are tied too closely to the framework. Which also means that future versions of your app will be spent entirely on migrating between framework versions... not very interesting problems, especially not to the business. Or perhaps, the business will choose never to upgrade framework versions for the same reason.
Programming is more important than calling the right framework pieces. It is fundamentally about translating human solutions into technological solutions. If you can do that using one framework, you can also do it with a different one. Or with no framework at all.
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.
Ironically, you are posting this question to a site which uses Rails, IIRC. So it is at least as relevant as your question, as of this date.
I read from other responses that this should be framed as "will this Rails job hurt my employability later?" I think this question is highly suspicious for the assumptions it makes. If I could give a yes or no answer to this question, it would mean that the only skill relevant to future jobs is whether you knew particular frameworks well (for example, Django instead of Rails). And in fact, (if you can) I would run far away from jobs which had framework experience as hard requirements (instead of "nice to have"s). It means they are tied too closely to the framework. Which also means that future versions of your app will be spent entirely on migrating between framework versions... not very interesting problems, especially not to the business. Or perhaps, the business will choose never to upgrade framework versions for the same reason.
Programming is more important than calling the right framework pieces. It is fundamentally about translating human solutions into technological solutions. If you can do that using one framework, you can also do it with a different one. Or with no framework at all.