java. But it's not springboot. It's Play framework.
Now if he should be concerned to work only on springboot based or any java opportunity that handle jvm is sufficient? Like jee development, play framework,etc..
Frameworks will change over time depending on company/team preference. Its up to your friend to learn to adapt the other framework or convince them to use the same framework as your friend's
Oh ok. But provided, there are lots of springboot based java jobs usually, he is concerned and bit worried whether he could switch to springboot gig in future if he works on play now?
Again, that's nothing to be worried about. I use a lot of frameworks all the time and I change and adapt over time.
IMHO. 80% - depends on the background, and 20% depends on the local market. If he has 3+ years of solid experience, it doesn't matter then. Consider tech stack and if it's not legacy, salary, company and product, etc. It won't matter much which framework it is. I totally agree with AgentQ in this case. But if he is a newcomer, with <1 year of experience (even maybe with 2, this may be individual), I'd recommend to stay away from 2 things - legacy and/or exotic frameworks. It will be simply worse for your career options, compared to if you pick something more popular and classic and work with it at least 1-2y. After that, interviewers won't consider the exact framework much, but more other techs - which fields you worked in, databases, clouds, what kind of problems did you solve, performance optimizations experience, and so on. Now specifically regarding play. It's not mainstream, but at the same time it's not way too exotic. I recommend to prefer spring-boot offers. E.g. if he has 2 similar positions with similar conditions, then SB is a better choice career wise. But if he has SB offer with lower salary and worse other terms, but play position with better terms, then I recommend to go for better position with play.
Thank you so much. This is really making sense.
Обсуждают сегодня