I'll volley with "Do you believe PHP is still relevant?". Wordpress and Facebook don't seem to be going anywhere any time soon. I came from the JEE world to the Rails world and I couldn't be happier that Rails is now "boring".
Focus your learning on foundation technologies (html/css/js, software design, etc.) and use the tools that are appropriate for your project.
Don't stick to the language, or the framework you're working with. Try to learn from the concepts, that you'll be able to reuse with other environments.
Treat the programming language and framework as a tool to solve a problem. Different the problem, different the tool.
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.
No, but the Title and your problem description are 2 different things.
Many things that you will learn while building websites will help you, along your web dev career, and a small part even if you move to another field/level. Exception is ofc the Ruby and Rails frameworks.
Also if you choose to stay in Ruby you will find many legacy projects, probably, but I would suggest to learn a new language every year.
i recently got a job as an ROR developer it is my first job. So i am little concerned that will i have a future in development if i moved out of this company or what i am learning now could give me my bread for the years to come.
If your skills are at the mercy of what framework is hot or not, you're pretty much toast in this industry IMO. You should be a Software Developer that incidentally uses RoR in his daily job, not the other way around.
Before this i used to work with Node.js and PHP so ROR learning ROR was easy for me (the basics at least).But what i am worried about will i get a job in companies that use other frameworks if am from ROR.
I dont see any new startups or lots of companies using ROR (may be i dont know)
But what i am worried about will i get a job in companies that use other frameworks if am from ROR.
I may have misunderstood, but why would it matter that you came from RoR when you try to get a job from a non-RoR company?
I dont see any new startups or lots of companies using ROR (may be i dont know)
If this is your assessment with your local job market, then maybe RoR is not the strongest presence there and searching for other keywords might serve you well. So yeah, Rails might not be relevant at your market.
There are still companies choosing to start with Rails so in that regard is still relevant. I'm not sure there are companies choosing COBOL as their development environment to start a business onto in 2018...
I would like to know from the OP what he thinks about relevancy or why he asked this question
This is pretty amazing. Both GitHub and Shopify are huge, billion dollar companies running on the original apps made over a decade ago. And they now both on the latest Rails, helping to push the framework forward 🙏🌟👏 twitter.com/eileencodes/st…
18:55 PM - 17 Aug 2018
Eileen M. Uchitelle @eileencodes
6263178
DHH
@dhh
Shopify and GitHub became worth 25 BILLION DOLLARS between them building on top of Rails. Now both of them have doubled down on Rails by getting their decade+ old apps on the very latest version. This is what success likes like, folks.
I'll volley with "Do you believe PHP is still relevant?". Wordpress and Facebook don't seem to be going anywhere any time soon. I came from the JEE world to the Rails world and I couldn't be happier that Rails is now "boring".
Focus your learning on foundation technologies (html/css/js, software design, etc.) and use the tools that are appropriate for your project.
Don't stick to the language, or the framework you're working with. Try to learn from the concepts, that you'll be able to reuse with other environments.
Treat the programming language and framework as a tool to solve a problem. Different the problem, different the tool.
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.
No, but the Title and your problem description are 2 different things.
Many things that you will learn while building websites will help you, along your web dev career, and a small part even if you move to another field/level. Exception is ofc the Ruby and Rails frameworks.
Also if you choose to stay in Ruby you will find many legacy projects, probably, but I would suggest to learn a new language every year.
Sorry i should have been more specific
i recently got a job as an ROR developer it is my first job. So i am little concerned that will i have a future in development if i moved out of this company or what i am learning now could give me my bread for the years to come.
If your skills are at the mercy of what framework is hot or not, you're pretty much toast in this industry IMO. You should be a Software Developer that incidentally uses RoR in his daily job, not the other way around.
Before this i used to work with Node.js and PHP so ROR learning ROR was easy for me (the basics at least).But what i am worried about will i get a job in companies that use other frameworks if am from ROR.
I dont see any new startups or lots of companies using ROR (may be i dont know)
I may have misunderstood, but why would it matter that you came from RoR when you try to get a job from a non-RoR company?
If this is your assessment with your local job market, then maybe RoR is not the strongest presence there and searching for other keywords might serve you well. So yeah, Rails might not be relevant at your market.
There are still companies choosing to start with Rails so in that regard is still relevant. I'm not sure there are companies choosing COBOL as their development environment to start a business onto in 2018...
I would like to know from the OP what he thinks about relevancy or why he asked this question
The Rails Ecosystem is Healthier than Ever
Ben Halpern
Rails 6 is also in the works.
So yeah, it's still relevant.
What do you believe?
Yes, what makes you think it isn't?
Yes, absolutely! ;)