At the moment I'm mostly in the same boat as you - PHP w/Laravel, Vuejs for front-end magic. I've also got quite a bit of Python kicking around and some golang & nodejs.
Most of the stuff I do is web apps for back-office functions and PHP (esp with Laravel) makes it really straightforward to get a lot of the boring CRUD stuff done in very few lines.
It's also nice to be consistent across apps w/regards frameworks so I'm not spending half a day thinking 'where the eff is that coming from?' when I have to fix/add a feature to something I haven't touched in months. So we tend to default to the same setup unless there's a very, very strong reason not to. That's a big part of the reason we settled on a 'full-fat' framework so that we limit the 'well, this project uses package-x, but this one pulled in package-y' to do the same thing.
I've also got a pretty big 'science' app that is mostly PHP plus about 10,000+ lines of Python, 5,000 lines of JS/node with some C & some TCL. That's a bundle of fun.... o_O
We're also looking to move to a Docker/Swarm/K8s setup for all the code to save the increasing hassles of keeping php/pyhton/whatever/code/libraries updated inside 'regular' VMs. But that's a whole other journey :-/
The science project is the control system for a nanotechnology fabrication plant. It sounds way, way more exciting than it actually is ;-)
I've been using Docker with CI/testing (using Gitlab) for a while now - it's been pretty nice. Just taking the plunge to production is a bit more scary!
It's just a very different way of working. Having to think a lot more about storage, containers/apps appearing and disappearing, handling 'split brain' network issues etc. Compared with 'I have a VM with my app and DB' :-)
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.
At the moment I'm mostly in the same boat as you - PHP w/Laravel, Vuejs for front-end magic. I've also got quite a bit of Python kicking around and some golang & nodejs.
Most of the stuff I do is web apps for back-office functions and PHP (esp with Laravel) makes it really straightforward to get a lot of the boring CRUD stuff done in very few lines.
It's also nice to be consistent across apps w/regards frameworks so I'm not spending half a day thinking 'where the eff is that coming from?' when I have to fix/add a feature to something I haven't touched in months. So we tend to default to the same setup unless there's a very, very strong reason not to. That's a big part of the reason we settled on a 'full-fat' framework so that we limit the 'well, this project uses package-x, but this one pulled in package-y' to do the same thing.
I've also got a pretty big 'science' app that is mostly PHP plus about 10,000+ lines of Python, 5,000 lines of JS/node with some C & some TCL. That's a bundle of fun.... o_O
We're also looking to move to a Docker/Swarm/K8s setup for all the code to save the increasing hassles of keeping php/pyhton/whatever/code/libraries updated inside 'regular' VMs. But that's a whole other journey :-/
Wow. May I ask what this "science" project is?
And I'm also going to learn how to use Docker in the near future. I actually have a project that may require it now.
The science project is the control system for a nanotechnology fabrication plant. It sounds way, way more exciting than it actually is ;-)
I've been using Docker with CI/testing (using Gitlab) for a while now - it's been pretty nice. Just taking the plunge to production is a bit more scary!
What's scary about using it in production?
It's just a very different way of working. Having to think a lot more about storage, containers/apps appearing and disappearing, handling 'split brain' network issues etc. Compared with 'I have a VM with my app and DB' :-)