Menu
Community /Pin to ProfileBookmark2. 
@NogDogMar 12.2015 — #It's always good to learn something new, but you need to balance that against getting things done on time and within budget. So you need to set your priorities, analyze your specific needs, then figure out which tools will do what you need best. And they're just tools: there's nothing magic about a claw hammer versus a ball peen hammer -- it's how the carpenter uses them that really matters.
As far as I can see, PHP is not going away, and with PHP 5.5+ and a framework like Laravel, it provides a rich programming environment. So does Ruby on Rails, or C#/.NET, or Java, or Python, or whatever. The only thing besides personal preference that might sway me would be how easy to you want this app to be for anyone to use anywhere -- which becomes a strong argument for PHP -- versus this is just for your needs and you can pick your deployment environment and configure it as you need, (and pay for licenses for M$ environments), in which case it's totally up to whatever works well for you. @NogDogMar 12.2015 — #
Almost every hosting company provides options for some sort of LAMP stack: Linux, Apache, [B]PHP[/B], and MySQL; so if your application runs in that environment (e.g. like WordPress does), you'll have the widest support base for deployment almost anywhere (and it's all open-source, so the hosting costs stay low). If you use the PDO extension in PHP for your database access, that can make the "M" part negotiable, allowing support of other DBMS's with little change to your code other than a configuration setting or two (if done right).
The moment you decide to build and deploy in something else (e.g. Linux with Ruby/Rails or M$ Server with C#/.NET) you start reducing the deployment options, so you need to weigh the benefits you see in using those technologies against the limitation of who can deploy it where. (Obviously, this is not that much of an issue if you are building it just for you to deploy, e.g. your own something.com that will be the greatest thing since google.com. ? )
New application in PHP
Hello,
Sorry if this is not the correct forum since I have multiple questions but PHP is my main one.
I want to write a small web application that needs to work through a mobile browser. I am knowledgeable in HTML, CSS, JAVA, PHP, SQL and some javascript.
I have a few questions:
1.
I have read that PHP is not the best option anymore. Should I use PHP or try something new ? what are the new trends ?
I do not want to host my own webserver and database and once I am done with the application, I will want to run different instances of it for multiple people. I have been looking at [url]https://www.openshift.com/
3.Could I write something completely in java but still work on a mobile browser ?
Sign in
to post a comment5 Comments(s) ↴
0
@NogDogMar 12.2015 — #As far as I can see, PHP is not going away, and with PHP 5.5+ and a framework like Laravel, it provides a rich programming environment. So does Ruby on Rails, or C#/.NET, or Java, or Python, or whatever. The only thing besides personal preference that might sway me would be how easy to you want this app to be for anyone to use anywhere -- which becomes a strong argument for PHP -- versus this is just for your needs and you can pick your deployment environment and configure it as you need, (and pay for licenses for M$ environments), in which case it's totally up to whatever works well for you.
0
@NogDogMar 12.2015 — #Can you provide me with some examples of some good/user friendly deployment environment ?[/QUOTE]
Almost every hosting company provides options for some sort of LAMP stack: Linux, Apache, [B]PHP[/B], and MySQL; so if your application runs in that environment (e.g. like WordPress does), you'll have the widest support base for deployment almost anywhere (and it's all open-source, so the hosting costs stay low). If you use the PDO extension in PHP for your database access, that can make the "M" part negotiable, allowing support of other DBMS's with little change to your code other than a configuration setting or two (if done right).
The moment you decide to build and deploy in something else (e.g. Linux with Ruby/Rails or M$ Server with C#/.NET) you start reducing the deployment options, so you need to weigh the benefits you see in using those technologies against the limitation of who can deploy it where. (Obviously, this is not that much of an issue if you are building it just for you to deploy, e.g. your own something.com that will be the greatest thing since google.com. ? )