Want to move to backend ( PHP, Ruby, Nodejs etc )

If you decide to go PHP and are looking for a good IDE, then PHP Storm is really good. I tried a few but none of them were as clean and responsive as it is.
 
@DrJohnZoidberg thank you for the advice, jip I saw php storm well this confirms it then (:
 
Learn PHP,
Don't bother with a framework for now, get used to the language first.
Learn how to accept a html form post and save the values to a databse or something.
Have some sort of application you want to write, do a "Todo" app.

Once you've done it in straight php, then try a framework, roll the dice and go for it, maybe you land on Yii, maybe you land on codeignitor.
Create your same Todo app again, see how the framework speeds it up and helps you along.
Roll the dice again, and create your Todo app again, in a new framework.
Repeat as many times as you want until the framework you're using makes sense.

I first started with CakePHP and didn't understand any of it..
Moving to Yii made things a lot clearer.
Working with Node and Express have been pretty easy.
on the side I'm doing RoR and it's not too difficult to pickup.

What I'm getting at is this was all a progression from the basic to the more 'advanced but easier to use' stuff. Each time I changed framework I learnt a new trick or two and understood more of how they work.
Eventually you'll find one per language that you like more than the rest and then you can specialise. just because 'Frank' says they like X, doesn't mean you will too..

Also, don't forget wordpress, there's lots of work out there for wordpress developers.
 
I hate bs replies like this, I want to start somewhere point me towards a backend language worth learning.


Use Java or C#. These are very well rounded languages, buckets of support, very relevant in the job market and they can fo everything from front end, backend, services, whatever.

...and go with c# if the choice is yours. Java is a potato language :whistle: :twisted: /hides
 
Use Java or C#. These are very well rounded languages, buckets of support, very relevant in the job market and they can fo everything from front end, backend, services, whatever.

...and go with c# if the choice is yours. Java is a potato language :whistle: :twisted: /hides

Always punting .NET, hey.
 
Always punting .NET, hey.


Given the choice between those two? Yes.

Don't think OP will find much use for Go atm. I could punt Python too. But I absolutely cannot punt your PHP...ever.
 
I always wanted to learn ASP.NET, but the damn thing is 2GB+ to download.
I use Node.JS and PHP (Laravel 5). I have never looked back ever since.
Laravel 5: General Back-end stuff, routing and basically any back-end tasks you can think of. It also has a wonderful ORM called Eloquent (which I love) and Blade Templating Engine, which pretty much eliminates the use of AngularJS. Laravel 5 is the way to go for personal/enterprise development.
Node.JS: Outshines all other technologies when it comes to real-time applications. Chat App, Gaming Back-end, Robotics etc are all well suited for Node.JS. Other technologies can accomplish this, but Node.JS gives a more natural approach. Google something called 'long polling'.
IMO. Don't start of with RoR. Start with something a bit simpler like PHP.
Which programming language is the best? That cannot be answered. Each language is suited for a specific problem.
 
Last edited:
Node.JS: Outperforms all other technologies when it comes to real-time applications. Chat App, Gaming Back-end, Robotics etc are all well suited for Node.JS. Other technologies can accomplish this, but Node.JS gives a more natural approach. Google something called 'long polling'.
That's a very bold claim to make
go-gopher3.png
 
You should look at PHP...oh wait that is what everyone is saying. Hmmmmm. You could check out codecademy to get a feel for some languages. I was first exposed to PHP on there myself.
 
Someone also mentioned using CodeIgniter. Don't use that. I was also planning on using CI, until I heard that development is not as active.

Incorrect.

CodeIgniter was created by EllisLab, and is now a project of the British Columbia Institute of Technology

3.0.1 was released yesterday in fact.
 
Incorrect.

CodeIgniter was created by EllisLab, and is now a project of the British Columbia Institute of Technology

3.0.1 was released yesterday in fact.


I've forgotten about CodeIgnitor. Remember playing with it years back. The alternative was Cake...or something like that.
 
Incorrect.

CodeIgniter was created by EllisLab, and is now a project of the British Columbia Institute of Technology

3.0.1 was released yesterday in fact.

Sorry, that was a bit ignorant from me. I've just had a look at their wiki and indeed, they have transitioned. Should have done research before quoting that.
 
Sorry, that was a bit ignorant from me. I've just had a look at their wiki and indeed, they have transitioned. Should have done research before quoting that.


And the part where you said a templating engine renders Angular obsolete?
 
And the part where you said a templating engine renders Angular obsolete?

"which pretty much eliminates the use of AngularJS" I was referring to using it with Blade. You can do general stuff that would otherwise be done in AngularJS (the "pretty much" part). I did not at any point mention that it will render AngularJS obsolete
 
"which pretty much eliminates the use of AngularJS" I was referring to using it with Blade. You can do general stuff that would otherwise be done in AngularJS (the "pretty much" part). I did not at any point mention that it will render AngularJS obsolete


"eliminates the use of" is the same as obsolete..maybe too strong a synonym, but whatever. The only part it replaces is the templating part to a certain extent (client vs server side). It's a silly comment imho, unless I misunderstood you.
 
"eliminates the use of" is the same as obsolete..maybe too strong a synonym, but whatever. The only part it replaces is the templating part to a certain extent (client vs server side). It's a silly comment imho, unless I misunderstood you.

The first synonym that came to mind is 'to cancel out' or in your case 'obsolete' for general stuff. Nevertheless, here's why you should not use Blade: https://scotch.io/quick-tips/quick-tip-using-laravel-blade-with-angularjs. It create confusion, conflict and if the feature is already there, why would you want to use AngularJS?
Also, read the part on 'Ideal Scenario'. If you're using AngularJS use that throughout your app and the reverse is true for Blade.
 
no, just no.

I mix Thymeleaf (a server side templating engine, analogous to Blade) with AngularJs ALL the time.
I often do not want to write SPA, but do want "SPA behavior" on various server side rendered pages
 
no, just no.

I mix Thymeleaf (a server side templating engine, analogous to Blade) with AngularJs ALL the time.
I often do not want to write SPA, but do want "SPA behavior" on various server side rendered pages

OK. So this is getting a bit too deep. Yes, I know, you can use AngularJS with templating engines. I have worked on web projects where I rendered the entire thing on Blade. But if Blade is able to support a simple feature, you wouldn't need Angular. But on the other hand you would replace it's use with AngularJS if something lacks. Using AngularJS and Blade makes no sense to me. Just use one technology and stick with it. Why add complexity by using two technologies?
 
Last edited:
OK. So this is getting a bit too deep. Yes, I know, you can use AngularJS with templating engines. I have worked on web projects where I rendered the entire thing on Blade. But if Blade is able to support a simple feature, you wouldn't need Angular. But on the other hand you would replace it's use with AngularJS if something lacks. Using AngularJS and Blade makes no sense to me. Just use one technology and stick with it. Why add complexity by using two technologies?


Are you a student or somebody newish to development?
 
Top
Sign up to the MyBroadband newsletter
X