3 ms·
It depends where you're at with the PHP stuff. If you're using a LAMP stack (as you mention) but using something like MAMP/XAMPP and keeping it simple, staying
by rbosinger 11y ago
It depends where you're at with the PHP stuff. If you're using a LAMP stack (as you mention) but using something like MAMP/XAMPP and keeping it simple, staying away from the terminal or PHP frameworks like Laravel, etc then most of this other stuff will be hard for a bit. Ruby on Rails is always talked about as being "easy" but it's really not at first if you're lacking knowledge of things like package managers, command-line tools, deployment that involves application servers and deployment scripts, MVC patterns, etc.
I'll say this: if you've been sticking to PHP to avoid all these things I mentioned then you'll do yourself a favor by picking almost anything (I'd say Rails or a Node stack) and getting into it. Once you get the concepts of these stacks you can use that knowledge to jump to other stacks a lot easier as well. Eventually it all feels kind of similar. You'd even be fine to stick to PHP but would be a much better PHP developer after nailing some of those concepts.
- Raed667 11y agoI'm quite familiar with the CLI, composer, Lumen, Slim, Symfony, Laravel.. This is not the issue. The thing is that I'm stating to feel that PHP bundles are getting "outdated". Where in Django or RoR you could set-up an oauth server and link it to your app in 20 minutes, in PHP the quality of the bundles and documentation make using stuff like that "hard". I'm starting to see that maybe Node (sails.js) + Angular are probably a good starting point.