>>105623052
>Should I do it? I got half a year, it's not even a guarantee I'll get it
Six months is a long time. Their needs might change in a quarter and a half and they could drop Laravel, so maybe you'll be out of a job regardless.
On the other hand, you have half a year to to bone up your resume and find another job.

PHP isn't a bad long-term bet if you're looking for job security. If you want to stand out from the competition, you could put up a website that does something novel and blog about working with the language(plus the frameworks you're using), which would make you way more appealing then the legion of boot-campers and vibe coders.
Personally, I think that in the next five years the focus is going to get even stronger on people who display a strong proficiency in their language and can also do Ops related work. Language knowledge because it's the best way to filter vibe coders(hip check questions like 'what's a call stack?') and Ops knowledge because infrastructure-as-code still hasn't become infrastructure-as-a-prompt and even when it does, it'll probably still create massive spend, plus more companies are moving away from AWS, Azure, and GCP anyway due to cost.
>>105623627
>Y no Perl?
As I said, I'm going off what my senior said with just using the language everyone else is using.
But from a cursory glance, I'll consider trying it if I have some large text-processing job instead of using shell scripts.
I've also wanted to give Lua a shot honestly, because having just one data structure(tables are associative arrays) in your language sounds peak.

Were the streamstars really that much worse than this cast?
Seriously asking.

>>507446661
I think anyone who isn't already demoralized is just in Lala land at this point

Having to face reality is too much of a red flag
I think the only time we'll see a real awakening is if the army has to fight Chinese in ship battles
It'll create such a schism that every boomers brain will instantly turn to mush