No worries, add the RESTbundle and now your controllers are returning JSON or XML rather than Twig rendered html.
Around 2014-2015 I was worried that I missed the Angular or Meteor or Knockout or Ember or something..JS boat but then quickly realised my customers didn't care about JS frameworks and wanted business flows automated and solved.
Now I see NextJS or something solving problems Symfony solved 10 years ago and I just chuckle.
I feel like we're getting to the same point in software development. I'm seeing things presented as new that were done decades ago.
"JAMStack!" You mean, how we pretty much had to do things 20 years ago?
I have a similar story of study and my escape has been to learn more about software design instead of frameworks or libraries. For example; DDD teaches how to describe problem spaces and how to talk about solutions in a way that is independent of any particular language or framework.
My learning efforts now seem better spent on building a core set of knowledge that has broader applicability.
Learning functional programming has helped as well. Not that the language I'm learning is so much better than anything else but that it introduces me to new ways of solving problems.
I also want to invest in my writing. Good documentation is becoming more valuable to me as I age.
modern PHP? I would contend the OP is still a hipster, but at least he's pointing out that fashionable programming is really toxic for the industry as a whole. Boring technology is good because the ordinary, standard thing is meant to be exactly that, ordinary and standard. Leave the breaking changes, feature churn, evangelising, endlessly-revised howto articles, missing/outdated documentation, etc. where it belongs -- in the "innovative" software.
- I care less about specific tools and I'm way less dogmatic
- I'm more comfortable learning new tools quickly when it's necessary
- I realise that many new tools can be completely left out which greatly reduces the complexity of the project (you aren't always in a position to do this when you work with other people)
It's definitely an important factor to both notice at all and your decision in regards to it has lasting repercussions. In my experience, the majority of devs don't take the conceptual path, so I've tended to let them get excited about NewFancyLibrary and while I focus on more abstract things like architecture, modeling systems, and languages. Seems to work pretty good, since we're both happy with the arrangement.
This isn't to say that JavaScript isn't capable. It's plenty capable, and when combined with TypeScript, it's pretty powerful. I just think that it's not a great idea as a primary first-principles language.
