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 am hearing by lots of programmer that Ruby lacks in performance with comparison to php.
So i try to find out the real picture behind that i saw this post Why do people say that Ruby is slow? .
There are many articles I found but most of them are too old to be considered for me in current scenario as ruby 2.1 already revealed. As a Ruby on rails developer I loved it. But want to know is this true and if yes how can we overcome this bottleneck in ruby .
So please put your thoughts on that
I think how you design your code and what software architecture you use has a larger impact on your performance than the underlying language. In my opinion programmers and software architects make software fast or slow. Ruby and PHP are both interpreted languages which can make code slower than compiled code because a compiler does certain optimizations.
But for both PHP and Ruby there exist bytcode caches and compilers.
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
What are the pros and cons of building your own web server, and the difference between building your own versus installing a 'pre-configured' web servers (such as: LAMP, WAMP, XAMPP, and other else). Is there any good benifits of building your own web server?
If you're gonna have your own server, would you rather build it on your own, or just download one from the internet? and Why?
Building your own web-server
Pros:
It will work exactly according to your taste
It will use the technologies of your choice
At the end you will know virtually everything about it, while with other webservers sometimes that is not possible
You will be famous if you implement something fantastic
Cons:
You will have to do a lot of complicated stuff which will delay the start of the task you wanted to work on in the first place
You on your own will not be capable to be even close to other webservers, developed by many programmers. You are one, they are legion
As times are changing, modern techniques will pour up and you will need to do a lot of work to adapt to the changes
Other webservers are free in many cases, while developing your webserver is very expensive: you pay with your sweat and tears
But the most important point is that before you start implementing your webserver try out others. Even if you reach to the conclusion that you want to write your own your experience with other webservers will help you a lot in planning yours.
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 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 never understood why PHP called "scripting language" rather than "programming language".
Is me introducing myself as "PHP programmer" is wrong I should be "PHP scripter"?
What definition of programing language and scripting language?
PHP can have complicated programs done and compiled into .exe files to run on windows.
Usually a language is called a scripting language if it's not compiled. But these days it doesn't matter anymore - PHP programmer is probably the more accurate term.
It's also matters what are you doing with the language. Even people who write in language that have 'script' in its name Java Script are called programmers as soon as they start doing something more advanced than simple DOM manipulations with jquery.
The only people I've lately heard that refer to them selves as scripters are bash-scripters :)
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.