Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
Assuming you're in PHP you must be a back end dev, so makes no sense to learn complex workarounds for front end while you'll never use them at back end. You could get more profit from learning laravel, lumen, symfony and so than putting your hands on a front-end library/framework.
Even those I'm full stack myself but I'm more on the front end and also learned about laravel for example so if you got the time take a look to those trendy SPAs using react, angular, svelte to see what is the reason to be for each and where they can fit best if you want to know more
Because I am a lone developer, I had to learn both front-end and back-end. I picked React and Laravel to build a serious project that currently has a client candidate.
However, for back-end, I don't want to restrict myself to PHP, because I see Node.js is interesting to use at back-end. Using PHP means that we have to deal with Apache or Nginx with their different configuration complexity. Whereas Node.js (and the newcomer called Deno) is a platform that also serves as a web server that may not require complex configuration.
As for front-end, actually I am also interested in Angular, seeing that it is said to be suitable for large scale apps; unfortunately I don't have enough time to resume learning on it.
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
Thanks for reply.
One of the reason that preclude me from learning new stuffs/technologies is time (energy too). Currently my time is already occupied with a serious project that will force me to read more Apache documentation and probably Nginx doc too. As I said I am interested in Node.js and have a desire to build a prototype using some parts at back-end in my current Laravel project. It seems that I couldn't realize it, at least in near future.
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
Well you'll use either Apache or nginx so simply check the differences and pick one and go with that at this point. Learn about what you use and finish your product dev cycle, it does not matter if it's not the best, you'll be able to refactor later
Some comments have been hidden by the post's author - find out more
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.
Assuming you're in PHP you must be a back end dev, so makes no sense to learn complex workarounds for front end while you'll never use them at back end. You could get more profit from learning laravel, lumen, symfony and so than putting your hands on a front-end library/framework.
Even those I'm full stack myself but I'm more on the front end and also learned about laravel for example so if you got the time take a look to those trendy SPAs using react, angular, svelte to see what is the reason to be for each and where they can fit best if you want to know more
Because I am a lone developer, I had to learn both front-end and back-end. I picked React and Laravel to build a serious project that currently has a client candidate.
However, for back-end, I don't want to restrict myself to PHP, because I see Node.js is interesting to use at back-end. Using PHP means that we have to deal with Apache or Nginx with their different configuration complexity. Whereas Node.js (and the newcomer called Deno) is a platform that also serves as a web server that may not require complex configuration.
As for front-end, actually I am also interested in Angular, seeing that it is said to be suitable for large scale apps; unfortunately I don't have enough time to resume learning on it.
If you learn well a stack, you'll be able to pick knowledge on any other much more easily than knowing half of one, keep it going!
Thanks for reply.
One of the reason that preclude me from learning new stuffs/technologies is time (energy too). Currently my time is already occupied with a serious project that will force me to read more Apache documentation and probably Nginx doc too. As I said I am interested in Node.js and have a desire to build a prototype using some parts at back-end in my current Laravel project. It seems that I couldn't realize it, at least in near future.
Well you'll use either Apache or nginx so simply check the differences and pick one and go with that at this point. Learn about what you use and finish your product dev cycle, it does not matter if it's not the best, you'll be able to refactor later