Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am not sure if the question fits SO's guidelines, but I would like to know if there is a specific situation where I can use micro-frameworks. Going by the nomenclature, it's suitable for small projects. But we can never tell if a project, which is small in nature at the moments, won't grow large later. Does this mean we can use micro-frameworks only for REST APIs and stuff (which are almost always smaller part of a large project) ?
It really depends mostly on your needs. If I want to create something that takes few hours and it's more or less just "Hello world" with some spice, I use Silex. If I need something even slightly bigger, I grab Symfony2 and spend next hour configuring it (just because it's probably worth spending more time on it). But it'd be naive to think it's as simple. I know people that roll bigger frameworks even for the tiniest projects, just because they can one day grow. Other people do them in micro-frameworks and just rewrite them if they need to. Just sit with your team and write down pros and cons of using micro-framework in given situation, that should work the best.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I know this isn't a very good question to ask because people may give bias answers, but was wondering if someone could list the pros and cons of using PHP vs NodeJS as a backend language in developing the average text-based online RPG.
The RPG will store its data in a MySQL database and will have typically 10-20 players online simultaneously.
For the long-run, which language would you think is more suitable?
I have several years of experience in PHP and barely any experience in NodeJS. It seems PHP has really good synergy with MySQL but I've been really hearing good things about NodeJS. Also, what design approach should I take (i.e. MVC).
Would be great to hear from someone who has a lot of experience in both languages.
Node.js is not a language. The language is Javascript.
Both are perfectly good choices, the main difference is the asynchronous approach of everything nodejs related. This increases the performance and scalability, but it's harder to debug and uglier to write and read (Learn about the callback hell). You need to get the asynchronous concept very well if you want to have the advantages people usually credits nodejs with.
This being said, you can program asynchronously with PHP, but it's far less common.
So if you are confident with PHP, you need the results fast or don't want to experiment go with it. If you want to learn or experiment, go with Node.
If the limit is 10-20 simultaneous players the performance shouldn't be such a a problem.
About the design approach, I would leave the details for last. MVC is very common and you will probably use something like that to organize your code but the choice depends on lots of factors and you should probably think about this after having the use cases / stories of your application defined and limited.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I am about to build the backend for my startup, which will be mainly offering a REST service, but HTML content will become available later. I am an experienced PHP developer and was thinking about building it in PHP first, but many people try to convince me to switch to Ruby. I would love to, but I have the following concerns:
I want to create a prototype quickly, learning a new language costs me a lot of time.
Right now I do not have a second developer who has Ruby expertise, so if I am stuck searching for a bug somewhere, it is worse than being stuck in PHP, where I know a bunch of people to get assistance from.
Some of the arguments people are making in favor of Ruby are:
It is easy to find good developers for Ruby, because the language itself is a filter.
Using a framework like Sinatra would speed up my development time drastically
Ruby is fun
What would you do?
The questions are :
do you prefer fun, or efficiency ?
do you have time to wait before being efficient ?
why not just recruit a good php developer ?
Even if there are bad developers on the market, there are also good developers
And I should add it's not that hard to see if a developer is good or not.
you say language is a filter ; don't you think it'll be enough of a filter to just make things hard when it comes to finding a ruby developer ?
If you're betting your money on this startup, take the road that you know. Getting to market quickly and having a support structure may be a lot more important than switching to a fun language.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I'm new to PHP and am trying to more of an overview before I jump into the code sometime tomorrow.
What advantage does using a framework like CodeIgniter or CakePHP or Zend provide over using 'plain vanilla' PHP?
The framework takes care of the stuff that everyone's done a hundred times - authenticating users, talking to databases, handling file uploads, validating forms.
It saves you time, because you don't have to write it again.
It saves you headaches, because it's probably designed better than you would off the cuff and because it's already been thoroughly debugged.
It makes it easier to collaborate, because anyone who knows the framework has a step up on understanding your program.
It makes programming more fun, because you can focus on writing the interesting bits, not the slugwork.
Any framework has the advantage of solving problems that just about any programmer would encounter without using a framework.
There are many common problems that you and I would face regardless of whether or not we're building software for banking, media, news, etc, and instead of reinventing the wheel, you can springboard off of the hundreds and thousands of hours of developer experience by using code that has been tried and tested in a multitude of different production environments.
The motto is this: Don't reinvent the wheel. Your job is to meet a business goal, not solve problems that other people have already solved for you.
One advantage is: Design decisions are made for you.
One disadvantage is: Design decisions are made for you.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 12 years ago.
Improve this question
I'm a new graduate and yave just started working a few weeks past as a web programmer. I've kind of been thrown in at the deepend and have been put straight on a project that appears on the face of it to be relatively simple, but there a lot of little intricacies that are making it quite difficult.
What sort of work rate will employers be expecting a new graduate to work at? My employer hasn't said anything but I feel like I am taking much longer than they anticipated - perhaps even regretting that the have employed me in the first place. Also, I am asking for help with logic and some best ways to tackle some problems and I also feel they think I should know more than I should. Again what would an employer be expecting from the level of a recent graduate.
I want to be as good as I can and learn as much as possible but I constantly feel under pressure as I keep thinkin I should be getting through mug more work than I currently am. Is this a common feeling in new programmers and how would my employer approach it if I wasn't performing up to their expectations. Like I said, nothing had been mentioned but I do feel they are wondering why they bothered to hire me.
Some advice on this from experienced developers would be great.
"Rate" is a hard thing to quantify when talking about software - as you note, some simple things aren't easy, and some complicated things aren't hard. In general, the most important thing is to communicate with your employer. You may be afraid to talk about the problems, but it's much easier to talk about them now than to keep your mouth shut and only announce problems when your project is due.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 13 years ago.
Improve this question
I've heard of GAE and even though it doesn't support PHP, people have gotten around this limitation by using Quercus I think (I haven't tried it, but supposedly it works). But what factors should I consider when evaluating whether it's a match for me? For example, what made you not go with GAE? Or if you went with it, what are you not happy about?
thanks
Edit:
Thanks to those who saw value in the question and defended it. I've seen questions here that were much less programming-related than mine and which were left open. In terms of it being a dupe, it isn't in anyway. That other question was specifically about PHP support; mine is about why not GAE in general (the php was a sidenote). I doubt the guy that yelled "dupe" even read both questions to see how mine is obviously so much different. You can vote it reopened if you still see value in it. Some good answers were already coming in, too bad the 5 of you killed a Perfectly Good Thing. I voted for a reopen, 4 more people could hop on if interested.
Because GAE is less flexible and tightly coupled to Google's framework.