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'm studying php programming and I'm pretty convinced I know base rules that permit me to move on pretty building good web application.It could be weird but from the beginning I started to build web application using frameworks.I know how php works (session,cookies,ecc...) but if you say me to create a web application without a framework I could have some problems because I don't have a mind schema to follow instead with framework I'm fell more comfortable because I follow simple pattern like MVC and I have everything clear in my mind. what I'm asking now is this situation is really convenient for a web programmer? I web programmer especially in the last times, have to be independent or dependent from frameworks?
It is perfectly possible to build a PHP application without any framework, but it is more time consuming.
If you want perfect control over every part of your code, don't use a framework. This option also lets you optimize your code fully.
However, using an existing framework may well be easier and less time consuming, in some cases at the expense of performance. I would say that the performance loss is negligible in most cases, but it really depends on the application.
Related
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 5 years ago.
Improve this question
I'm wondering if it is possible to create a web application where a user can sign up,login, and make payments without using a framework like Rails or Node.js, but rather html,css,php,mysql etc.
Is this even possible?
Yes, it is entirely possible to write any web application without framework. Keep in mind that frameworks are also written in their respective programming languages - therefore, you can achieve same results without one, but it will be more time-consuming and will need more work to "reinvent the wheel". A framework usually delivers many useful functionalities that are ready to use, but in the exchange you must comply to its standards, semantics and rules.
Many programmers of high-end applications choose to develop without a framework, because they don't want to be bound by those boundaries. Also, there are performance reasons - if you can fine tailor your application to your business requirements, it will probably run faster.
Also, please keep in mind that Node.js isn't a framework - it is a toolset that allows running JavaScript applications in OS enviroment instead of the browser.
It will take a lot of time but it sure is possible. These 'frameworks' are here to speed things up for you. I recommend you to take a look at a couple of MVC frameworks. For example: Laravel, Codeigniter and Symfony. These frameworks will do a lot for you(Think about security and routing) but you still have to write the biggest part of the logic yourself.
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 originally asked a biased question about which MVC framework is best suited for high traffic.
The answer to this question is that most frameworks can are designed handle such traffic. Choose the best MVC framework you are comfortable with.
Donald Ervin Knuth:
Premature optimization is the root of all evil (or at least most of
it) in programming.
Most of the tools we're using (including frameworks in general and Laravel in particular) are designed to speed up development process and then ease developers workflow.
The general rule here I'd say is build it first. By the moment your project becomes so big (read successful) that Laravel on PHP7 fails to deliver you certainly will be able to hire someone to tackle that problem.
Therefoe Laravel is a decent choice for a new project, like any other framework.
Ideally write your application logic in a framework-agnostic manner, i.e. keep Laravel out of your business logic - that requires some experience, but in the end you would even be able to switch frameworks.
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 9 years ago.
Improve this question
I've been coding with django for a few months now, and I have made good progress. But, I feel like I don't understand what's happening under the hood well enough to make the leap from beginner to advanced. For example, it's easy to manipulate the database via ORM in Django without having any knowledge of SQL. As another example, user authentication in Django almost only requires me to import a module and writing a couple of lines of code. I don't have to have any knowledge on sessions, database queries etc.
As I have done no prior web programming except Django, I was wondering if it would make sense to move to PHP (without a framework) and when I've learned the fundamental concepts of web development (cookies, sessions, SQL etc) return to Django development?
No, that wouldn't make any sense at all.
PHP is just one language for writing websites. It works in a certain way, but many of the things that you often see in PHP are not generally considered best practice. It's very unlikely to help you write a decent Python web app.
If you really want to learn how everything works, you could just as easily write a Python app using raw WSGI, or a micro-framework like Flask.
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 8 years ago.
Improve this question
I'm working on a rather intensive rewrite and given a choice of the following options:
JSP / Java running on Tomcat
PHP running under Apache
Ruby (running under I'm not sure, ROR?)
A couple of basic questions I would like to know about the above.
Speed is a concern. We have a MongoDB backed database, so we shouldn't need to be waiting on the database for information, but the frontend needs to be as fast as possible. The common saying speed isn't a concern doesn't really apply here. If you're processing 500k+ objects in one request it needs to be fast.
Scalability is another concern. Suppose our database blossoms out of control. Which (of the above) would provide the easiest method of handling this?
What are common downsides of Tomcat / JSP and Ruby? Is parallel processing easy to do with PHP or Ruby?
The goal is not to save money but to build a solid, fast, scalable system to continue development on for years to come.
I'll be honest, I'm a former Java developer (not JSP) turned PHP developer. My preference for anything is PHP but I also am a big believe in using the right tool for the job. The team is competent enough to write this is anything that we
Seems like any of them would be acceptable based on the limited info so far. The important things I've begun to consider when launching new projects are more about the ORM and framework than about speed. For every extra 40 hours of developer time I have to spend on a project I can provision and operate a new server for 1 year.
If you have developers that are better versed in the APIs for a particular language, that alone could (potentially) make your decision. If you can parallelize 500k things across 10 servers, and choosing language (and API/libraries) A over B will save you 10 weeks, then that is your breakeven point. Similarly, if one set of things is 2x as slow, and having 2 servers instead of 1 could double your processing speed, then it will only take 1 week of extra fighting in the "faster" language before all your performance gains are wiped out due to longer development time...
Ended up going with Play!
Reasons:
Quick startup
No redeploying / packaging
Straight forward MVC pattern
Groovy template / inherited views
Drop-in support for dependencies as JAR files
Development was never hindered by it. No one had to learn anything new besides where to put the controllers / models / views.
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 7 years ago.
Improve this question
I dont have experience in web programming. I so far I coded in c++ only. If I wanted to build a site similar in functionality to cafepress.com which route would be most suitable for me?
asp.net mvc or php mvc or just php?
Granted I am new at this, still the amount of options is overwhelming to a newbie. And there is no decent guideline as to pick which is more suitable for what kind of projects?
Since I am new at this, I have to learn one of these things. But I don't want to waste my time only to see these things go out of fashion. So, I am looking for these qualities :
must not go out of fashion in a few years. By this I mean, something that is hyped just because its new and has not found a universal acceptance yet
simple, easy to learn and don't over complicate
do not abstract how web works (asp.net webforms....ahem)
can be done by a small group 2-3 guys
I would suggest you to go for Cakephp or codeigniter which are damn good for making large and maintainable sites. PHP is open-source, cross-platform, has good community support to php and above mentioned frameworks, something not there in asp.net. Also in asp.net security holes are found regularly.
I like ASP.Net MVC so i would recommend that because C# is awesome and Visual Studio is the best IDE. But you should look at the languages and tools and figure out what suites you.