Statement: This problem is caused by the wide opening of my brain and some questions. please forgive me for anything wrong. What did Laravel subvert PHP? is it just to promote Composer? does Laravel's features violate the original intention of PHP? PHP was originally characterized by lightweight...
Statement: This problem is caused by the wide opening of my brain and some questions. please forgive me for anything wrong.
What did Laravel subvert PHP? is it just to promote Composer? does Laravel's features violate the original intention of PHP, which is originally characterized by lightweight components, now we have added the namespace and package management. What are the actual domestic application projects of Laravel? Is it just to develop an extreme blog like WordPress? In addition, GitOsChina does not find many Laravel-related application projects. you will not tell me that there are many such projects on GitHub, the development and credit of the Git community in China cannot be ignored because GitHub is famous. GitOsChina is now also an influential Git Service community in China, the promotion of Composer will inevitably lead to the increase and bad use of various dependent packages of the project, so that PHP will inevitably become increasingly out of magnitude. What I understand can be widely used is definitely a Swiss Army knife like JQuery. it is lightweight, fast, and flexible, and can be used to expand and develop many things, to meet our own needs, as well as the BootStrap front-end framework, such frameworks can be widely used and fully developed and used. Laravel's craftsman spirit, I think, will cause problems such as its inflexibility and difficulty in learning curves, and finally become a pet of only a few geeks and enthusiasts.
X supplement 20160621
X -------------------------------------------------------------- ++>
First of all, I would like to thank you for your sincere reply. I have learned a lot from your replies. below is what I want to add:
I agree with @ Fei Long's point of view:
Php has long been not the concise php. it has learned too many java things and lost the flexibility of some scripting languages. Your understanding of php remains in the 3x age.
I am talking about namespaces and package management as follows:
PHP is a lightweight feature, and now adds namespaces and package management.
I hope you don't want to chew on it too much. from my big point of view, I didn't place the namespace and package management on Lavavel. besides, Lavavel won't be able to make PHP changes. Python, Node. javaScript and PHP feel that there is no comparability. after all, the design purpose is different from the original intention. In addition, many people have long had the concept of package management, and PHP has long fallen behind in terms of package management, in my opinion, many Chinese projects in China only use Laravel as a blog. the blogs they make cannot be compared with WordPress, in addition, WordPress still supports 3x and no one else must use Composer. Another point is that Lavavel does not seem to be easy to remember, at least for me.
I may say that @ Fei Long is still in the era of 3x, even though @ JellyBool is an excuse for me not to be enterprising.
But in my opinion, JQuery, BootStrap is indeed a flexible framework and cannot be sprayed together due to my problem.
You have no intention of bringing GitOsChina in. do not mislead others and make others mistakenly thinkGitOsChinaPoor. for those who are not good at English or cannot access the Internet scientifically, platforms such as GitOsChina and Coding.net provide at least one Learning Channel, at least from which I started to access Git, I can't say that I don't want to learn programming if I am not good at English.
Based on your comments, my personal idea is to get familiar with Laravel first. if there are a lot of pitfalls at the beginning, I will not be able to get started for a few days, then I will learn about it only when it becomes popular like JQuery in China.
The following is only an opinion that represents the level of understanding of an individual, and does not involve any other group organization or interests.
What suits you is the best Thumb ups
X supplement: 20160621
X -------------------------------------------------------------- ++>
The following is only a point of view on the level of understanding of individuals. based on the basic concepts that do not know, do not know, do not understand, or do not understand, do not involve any other group organizations or interests.
Lavavel's domestic advocates should not talk about Lavavel as an old man. they put the craftsman, artist spirit, lightweight, simple and elegant, and PHP's latest features all day long, it seems that you must follow me for 5x and 7x. why don't you use Composer? I only use Composer. are you still engaged in the 3x set! To crack down on old Cainiao like me, it's like you don't want to go to school with the new features of PHP, so you don't need to mix it in this circle, looking down on the domestic framework, looking down on the dream CMS, looking down on WordPress, and even looking down on GitOSchina, how much effort and effort others have made to have a decent Git service in China, how many programming environments in China have been improved? don't take GitHub all day long. Not everyone has the opportunity to go abroad. Not everyone knows Git. what is the domestic programming environment, the foreign environment should be clear to everyone. most people in China are still forced to code their wages. the domestic service platform has the principle that the domestic service platform exists, it's not up to you to say what others are doing.
In terms of craftsman spirit, do Lavavel have many popular Java frameworks such as craftsman spirit? are there many popular Python frameworks concise and elegant? do not abuse these words to exaggerate and respect, it's mysterious. If the package management is not easy to understand, write more information for everyone to understand. if the learning curve is difficult, it will simplify the optimization entry method and refine the process analysis if the execution process is not easy to understand, if the Chinese language is not supported, write more Chinese language packs. if there are few Chinese materials, write more Chinese materials. these later advocates can work together, and I will not be excluded from the future, but the premise is that you need to know how to get started. Apache, Nginx, and Mysql are easy to use. maybe everyone needs to know how to configure them at the beginning, and the one-click environment is not fast, using a one-click environment does not mean that you cannot learn the configuration, but it only lowers the threshold for getting started. For example, people familiar with the VIM editor say it is good, but it is very difficult for general people to get started. it was not easy to use at the beginning and was rejected, sublimeText is a good solution to the problem, so it is more popular and highly respected.
The problem has been disabled. cause: the problem cannot obtain the exact result.
Reply content:
Statement: This problem is caused by the wide opening of my brain and some questions. please forgive me for anything wrong.
What did Laravel subvert PHP? is it just to promote Composer? does Laravel's features violate the original intention of PHP, which is originally characterized by lightweight components, now we have added the namespace and package management. What are the actual domestic application projects of Laravel? Is it just to develop an extreme blog like WordPress? In addition, GitOsChina does not find many Laravel-related application projects. you will not tell me that there are many such projects on GitHub, the development and credit of the Git community in China cannot be ignored because GitHub is famous. GitOsChina is now also an influential Git Service community in China, the promotion of Composer will inevitably lead to the increase and bad use of various dependent packages of the project, so that PHP will inevitably become increasingly out of magnitude. What I understand can be widely used is definitely a Swiss Army knife like JQuery. it is lightweight, fast, and flexible, and can be used to expand and develop many things, to meet our own needs, as well as the BootStrap front-end framework, such frameworks can be widely used and fully developed and used. Laravel's craftsman spirit, I think, will cause problems such as its inflexibility and difficulty in learning curves, and finally become a pet of only a few geeks and enthusiasts.
X supplement 20160621
X -------------------------------------------------------------- ++>
First of all, I would like to thank you for your sincere reply. I have learned a lot from your replies. below is what I want to add:
I agree with @ Fei Long's point of view:
Php has long been not the concise php. it has learned too many java things and lost the flexibility of some scripting languages. Your understanding of php remains in the 3x age.
I am talking about namespaces and package management as follows:
PHP is a lightweight feature, and now adds namespaces and package management.
I hope you don't want to chew on it too much. from my big point of view, I didn't place the namespace and package management on Lavavel. besides, Lavavel won't be able to make PHP changes. Python, Node. javaScript and PHP feel that there is no comparability. after all, the design purpose is different from the original intention. In addition, many people have long had the concept of package management, and PHP has long fallen behind in terms of package management, in my opinion, many Chinese projects in China only use Laravel as a blog. the blogs they make cannot be compared with WordPress, in addition, WordPress still supports 3x and no one else must use Composer. Another point is that Lavavel does not seem to be easy to remember, at least for me.
I may say that @ Fei Long is still in the era of 3x, even though @ JellyBool is an excuse for me not to be enterprising.
But in my opinion, JQuery, BootStrap is indeed a flexible framework and cannot be sprayed together due to my problem.
You have no intention of bringing GitOsChina in. do not mislead others and make others mistakenly thinkGitOsChinaPoor. for those who are not good at English or cannot access the Internet scientifically, platforms such as GitOsChina and Coding.net provide at least one Learning Channel, at least from which I started to access Git, I can't say that I don't want to learn programming if I am not good at English.
Based on your comments, my personal idea is to get familiar with Laravel first. if there are a lot of pitfalls at the beginning, I will not be able to get started for a few days, then I will learn about it only when it becomes popular like JQuery in China.
The following is only an opinion that represents the level of understanding of an individual, and does not involve any other group organization or interests.
What suits you is the best Thumb ups
X supplement: 20160621
X -------------------------------------------------------------- ++>
The following is only a point of view on the level of understanding of individuals. based on the basic concepts that do not know, do not know, do not understand, or do not understand, do not involve any other group organizations or interests.
Lavavel's domestic advocates should not talk about Lavavel as an old man. they put the craftsman, artist spirit, lightweight, simple and elegant, and PHP's latest features all day long, it seems that you must follow me for 5x and 7x. why don't you use Composer? I only use Composer. are you still engaged in the 3x set! To crack down on old Cainiao like me, it's like you don't want to go to school with the new features of PHP, so you don't need to mix it in this circle, looking down on the domestic framework, looking down on the dream CMS, looking down on WordPress, and even looking down on GitOSchina, how much effort and effort others have made to have a decent Git service in China, how many programming environments in China have been improved? don't take GitHub all day long. Not everyone has the opportunity to go abroad. Not everyone knows Git. what is the domestic programming environment, the foreign environment should be clear to everyone. most people in China are still forced to code their wages. the domestic service platform has the principle that the domestic service platform exists, it's not up to you to say what others are doing.
In terms of craftsman spirit, do Lavavel have many popular Java frameworks such as craftsman spirit? are there many popular Python frameworks concise and elegant? do not abuse these words to exaggerate and respect, it's mysterious. If the package management is not easy to understand, write more information for everyone to understand. if the learning curve is difficult, it will simplify the optimization entry method and refine the process analysis if the execution process is not easy to understand, if the Chinese language is not supported, write more Chinese language packs. if there are few Chinese materials, write more Chinese materials. these later advocates can work together, and I will not be excluded from the future, but the premise is that you need to know how to get started. Apache, Nginx, and Mysql are easy to use. maybe everyone needs to know how to configure them at the beginning, and the one-click environment is not fast, using a one-click environment does not mean that you cannot learn the configuration, but it only lowers the threshold for getting started. For example, people familiar with the VIM editor say it is good, but it is very difficult for general people to get started. it was not easy to use at the beginning and was rejected, sublimeText is a good solution to the problem, so it is more popular and highly respected.
In fact, it cannot be blamed for the complexity of PHP.
When PHP was born, it was also when the WEB was relatively elementary. at that time, a small CMS of the website was enough, and the logic was simple and the overall scale was small, no matter how the code is compiled, it won't be too biased. At this time, the PHP scripting language solves most of the problems. even using HTML + PHP hybrid encoding does not make people feel uncomfortable. If I remember correctly, this encoding method is called "spaghetti programming ".
Then, as the WEB becomes more complex, the mixed encoding method is a little inadequate. The result is that there are n more PHP and HTML code on a page, as a result, the coding staff (including their own) became more and more headers, and some general code could not be put forward by using include. as a result, the template concept appeared, which is representative of smarty, at this time, you can write the logic into a PHP file and load another template file as the presentation layer. this file only contains some necessary PHP logic code, this separates the logic code from the display code.
However, the WEB development is too fast, and the code responsible for processing the logic quickly becomes very large, with requests, databases, and some general logics in place, the backend engineers all crashed, and the more bugs they wrote. So someone wrote a framework to separate these logics, so a batch of frameworks such as Codeigniter appeared. Most of these frameworks use a single entry to ensure that the logic part is taken over by it, and then the MVC layer is separated to allow them to perform their respective duties and the code is smooth. However, at this time, PHP is no longer the original PHP, and it is no longer a 24-hour getting started with PHP. although it can also be programmed using pasta, it can even be used now, but such programming will at least be despised, so many PHPer are forced to learn a new programming method called hierarchical programming. But to be honest, the separation layer is indeed much more comfortable in programming. (Lord, since you are a little opposed to Laravel programming, I guess you should be using this type of MVC layered framework for programming. if I say this violates the idea of PHP fast programming, can you return to the original programming method? If you guess it wrong, don't mind .)
Later, even now, the WEB is not simply a requirement for sharing knowledge, SNS, e-malls, B/S service software, as backend engineers, think about big headers. So someone jumped out to solve various problems. how can this problem be solved? What problems can be solved. Let me give you an example at will. for example, it is not a problem to write an electronic mall with a majority of the old framework Codeigniter. Although the logic-side code may be a little long, it can be tolerated, but when you look back at the code one day, you find that the V-side code is still available, and the logic is clear. it is just a presentation, and there is nothing to optimize. the M-side is also possible, it is nothing more than writing some SQL statements. even if the SQL statements are too complicated, it is also a matter of database design. then you can look at the C end, and you can't bear it, here, we are responsible for receiving various GET and POST code, code for processing various logic computing, code for verifying data, and various code for loading data M to load V, each function is less than a hundred lines, so you plan to extract the logic part of the code, so that the C end is only responsible for reading user input data and loading M and V. As for the logic operation part, split another Service layer. this split not only simplifies the C-end, but also reusable some services. When you start the split, you suddenly find that there is no place to put this layer in the library. I think it is just a place to place an independent library, not a place to layer. put it in M, I think it destroys the meaning of MVC, but there is no way. The rules are not dead. use them if they can be used. However, if you use a relatively new framework and all of them comply with the PSR encoding specification, you can create a folder as a layer, and then use it on the C side without damaging the existing structure, the best thing is that if the code you write can be effectively decoupled, you can share what you write with others in combination with composer, this is also one of the highlights of many new frameworks.
Then I will not say much about it. if PHP is always stuck, we will always use the script-based programming method that we used a long time ago and will be eliminated one day later.
Of course, I really want to talk about it. various new frameworks bring many new features, so it's too difficult to learn ......
Here is the focus: The above is purely a personal discussion. Some places do not have detailed research, it may be wrong, just a few tea points. If you can point out the error, you may not like it.
Well, the front is ready for tearing. The following are personal opinions and do not involve any other group organizations or interests.
1. Laravel does not subscribe to PHP, but it only uses many new PHP features.
2. not to promote composer. composer is the product of the PHP community, but you don't know it.
3. Laravel features are totally different from the original intention of PHP. namespaces are the product of PHP, and namespaces do not violate the so-calledLightweight
The characteristics behind each technology are to solve problems in a specific scenario. Simply put, to solve class and method naming conflicts, the namespace is introduced. I personally think that those who maintain the PHP source code on github make the right decision to add PHP to the namespace. Maintain the so-calledLightweight
Features are not an excuse for your unthinking. If a language cannot be more suitable for solving problems as the times change, the language will not survive.
4. I personally think WordPress and Laravel are basically incomparable.
5. sorry,GitOsChina is an influential Git Service community in China.
I can't agree with this sentence. To be open-source, Github will inevitably open up 100,000 streets in all other git Service communities (exaggerated rhetoric ). If it is not open source, it is a business project of the company. basically, all the options are self-built git Services.GitOsChina is an influential Git Service community in China.
. I personally think GitOsChina will not be able to survive for long (Welcome to face it), because GitOsChina's ecosystem is really frustrated.
6.The promotion of Composer will inevitably lead to the increase and bad use of various dependent packages of the project.
For the moment, I am not sure that I am the only one who can read and write projects.
7.In this way, PHP will inevitably become increasingly unordered.
Can the lightweight content you are talking about remain unchanged? That's just an interface that is not enterprising.
8.It must be a Swiss Army knife like JQuery. it is lightweight, fast, and flexible.
Jquery is not a good choice. Now Jquery is hard to get the same vitality as before, because the development of the front-end is more inclined to MVVM such as Vuejs.
9.As well as the BootStrap front-end framework, such frameworks can be widely used and fully developed and used.
. If you want to find a CSS-oriented framework like Bootstrap in the PHP community, it's not Laravel.
10.Laravel's craftsman spirit, I think it will cause problems such as inflexible learning curve and difficulty.
. On the contrary, Laravel is very flexible, if you understand IOC.
11.Finally, become a pet with only a few geeks and geeks
. Anyone who pays attention to the PHP community and has seen the outside world should have no such idea.
12.What are Laravel's actual domestic application projects?
. No, I wrote a https://laravist.com.
So my point is: in this case, you don't have to study Laravel at all. after all, what suits you is the best. Everyone has different pursuits.
No one needs to spray you
After reading your questions, I have some thoughts. I cannot agree with some of the conclusions. A conclusion built on incorrect assumptions is not credible, so I just give a rough view of your problem and hope to learn together.
Laravel is undoubtedly an excellent framework, but the author has never said that he is "subverting" or wants to subvert anything. The author is such an ordinary otaku who will accompany his family. thank you for your code, while developing your own frameworks, you will be interspersed with your own entrepreneurial projects, a series of deployment services derived from the Laravel framework, SASS, and consultancy services. I have been in touch with Laravel for more than half a year, and I don't seem to see anyone who says this framework is revolutionizing anything. it is estimated that the people who talk to you like this are either brain-dead or exaggerated words, in terms of procedures, it is good to ignore such exaggerated words. Laravel is built on the meticulous and selfless contributions of the PHP community's predecessors. it uses open-source projects of many other developers, including the Symfony component, as the underlying dependencies, whether Laravel or the libraries on which it depends, these are not completely re-engineered, nor are PHP's proprietary writing methods. every dependent community has many similar implementations.
The direct relationship between Composer and Laravel is not great. The former is a dependency management tool developed by the community to a certain extent and helps developers maintain a large number of dependent libraries and version updates. for example, if you write a Web application by yourself, it is likely that you need to complete many aspects such as routing, ORM, request and response, verification, and template engine. now, you don't want to write it yourself, at this time, you will think of introducing other active and well-documented libraries for your use. when your program features enough, you may send emails, file system abstraction, and queue interfaces, in all aspects, you must stand on the shoulders of our predecessors to speed up your development and let people who are good at doing what they do. In this case, Composer is the only tool that ensures that you maintain dependency updates, conflicts, and rollback. When the community develops to a certain stage, even if there is no Composer, there will be Overture and Singer. So far, Composer has become a de facto industry standard for the PHP community. Your ignorance of him only shows your laziness and ignorance. even if you search for a PHP project on Github, you will not think that Composer is promoted by a framework.
If you say "Laravel's features violate the original intention of PHP", you 'd better understand what you think it is and what is the original intention of PHP.
PHP's selfless maintainers and commercial companies have never said that PHP is lightweight, and I don't know what simple means in your mouth. if you add a feature, dependency management tools in the community are lightweight, so the language with a large number of users is probably not lightweight. Getting started with PHP is simple, but it doesn't mean you can write code in a silly way, but it's a matter of course. Nowadays, developers have a very bad idea. Sublime is called lightweight, PHPStorm is called heavy, files are called lightweight, and files are called heavy. But what I can tell you is that the addition of a function and the complicated discussions that have been invented, countless people think carefully, and there are urgent needs in many development practices. You can't sit around and question the original intention of others. A language or tool that makes you feel lost in heart failure, so that you think it is against common sense. Don't worry, he will be eliminated, because most people are not stupid, the market naturally removes useless products.
It is unclear about domestic projects. most of the programming tools you use today are not produced in China. if you can, don't just focus on them, there are still a lot of great materials. By the way, Laravel is a framework that has a great impact on human programming style. please use it with caution. Otherwise, it may be difficult to go back to the Times of writing noodle code.
WordPress is a rich plug-in content system. I don't know much about it, but I feel that he and Laravel are not in a field at all, and their respective directions are different.
GitOSChina has no influence, including all such services in China. it thinks that adding a forum and an outsourcing market is micro-innovation, and then it is localized. in essence, it's all about earning low-cost domestic developers' money. A person who uses Github is not likely to use what you said. First, developers on Github are the largest in the world, and they open source the most of their products as an organization of large companies. They gather millions of people on the planet's smartest, on the other hand, how do you lie to the coder of Party A's money in China? There is only one Git community in the world, maybe two, but the other is definitely not what you said. a big community is a temporary gathering of things that people use Gitlab to set up in a rush. "You cannot ignore the credit of the Git community in China because Github is famous.
"The promotion of Composer will inevitably lead to the increase and use of various dependent packages of the project, so that PHP will inevitably become increasingly out of magnitude .", I was a little hasty to judge the importance of files and the number of dependencies. one page of code, written slag, can eat more resources than 10000 pages, even heavier. PHP enabling Opcache is a semi-compiled language, but there should be no significant difference between dozens of files and dozens of files in most systems.
"It must be a Swiss Army knife like JQuery ". JQuery is not a Swiss Army knife either. it is just a compatibility solution derived from the unthinking and enterprising products headed by IE, which is developed in the early days of browser development and with imperfect standard support, so that you can use it in different environments, unified API writing. Of course, his role is also true today. And it will become popular for a long time in the future because of its unified interfaces. However, you cannot name anything that is big and complete as a Swiss Army knife.
The craftsman's spirit is just the claim on Laravel's website that elegance is the same. The author always wants to eat, and there is always a word that reminds you of this framework. Based on my experience with two more complex frameworks, Laravel is a very simple framework. if you have an OOP foundation, you can develop it immediately after reading the documentation, in addition, when viewing the source code, I may find that the author did not write any surprises in the document from time to time. I may lament that he can take into account various complex application scenarios on the basis of ease of use. Laravel is not a pet of the "few geeks". In the past three years, Laravel has ranked No. 1 in the popularity of the global PHP framework. since 2015, the number of users and attention have also increased, for details, you can go to index.baidu.com to check their search indexes and drag them all to see the growth curve. Even if the training institutions that produce code monkeys in mainland China are full of places (higher education implementation is not in place and profit-driven), a framework and training institutions cooperate in depth and leave a framework without code writing, laravel is gradually being accepted by more programmers who want to grow themselves to a new height.
I don't want to write it in half, because it is difficult to wake up a sleep person. A profession that creates content every day, but regards new things as the biggest enemy. I also use my only knowledge to make unreasonable inferences that I cannot tell the cause and effect. Although everyone has the right to express their opinions, I feel that when I encounter something I cannot understand, the first thing I should do is to learn and understand, rather than making some conclusions that are hard to persuade others.
I personally think you have misunderstoodlaravel
Andcomposer
Is that you passlaravel
Yesphp
Yescomposer
Similar dependency management tools
Ascomposer
The introductionAdd and use various dependent packages of the project
I suggest you check node npm, python pip, ruby gem, and so on to see if they cause misuse,
Someone may say laravel copiedrails
Indeed, they are very similar. laravel can be said to be a full-stack development framework that can be quickly implemented.web
Development, introduce the best solution in the web, introduce the most reasonable technology, for example, introduce composer dependency management
What is your inflexibility? Why is it not flexible?
As for the learning curve you mentioned, it is true that laravel's learning curve is relative to other frameworks.Relatively high
But this is also relative. a higher learning curve means faster development efficiency after you learn it well.
It is recommended that you do not need to be on the cloud. if you do not think it is good, you can choose a suitable framework.
If you do not think it is good, you do not need to find any reason to learn laravel.
Is Laravel revolutionizing PHP just to promote Composer?
PHP5.3 already has Composer. in addition to larevel, there are many projects that use Composer.
Whether or not Laravel's features violate the original intention of PHP. PHP is a lightweight feature and now adds namespaces and package management.
This is exactly the characteristic of a modern mature language, andPHP is not a lightweight language.
What are the actual domestic application projects of Laravel? Is it just to develop an extreme blog like WordPress?
Larevel has been launched for several years. many projects in China are developed using it. you have never heard of it. In addition, WordPress is a small CMS instead of a blog.
In addition, GitOsChina does not find many Laravel-related application projects. you will not tell me that there are many such projects on GitHub, the development and credit of the Git community in China cannot be ignored because GitHub is famous. GitOsChina is now an influential Git Service community in China.
Yes? I have never heard of GitOsChina, which is "famous", but no one knows about Github in the developer circle. In addition, larevel is used in more and more projects at home and abroad.
The promotion of Composer will inevitably lead to the increase and bad use of various dependent packages of the project, so that PHP will inevitably become increasingly out of magnitude.
Nodejs, python, and other languages also have their own package manager. I have never seen any misuse.And PHP itself is not a lightweight language.
What I understand can be widely used is definitely a Swiss Army knife like JQuery. it is lightweight, fast, and flexible, and can be used to expand and develop many things, to meet our own needs, as well as the BootStrap front-end framework, such frameworks can be widely used and fully developed and used.
None of the things you mentioned are lightweight and seem to me heavy or bloated.
Laravel's craftsman spirit, I think, will cause problems such as its inflexibility and difficulty in learning curves, and finally become a pet of only a few geeks and enthusiasts.
This is your personal opinion. What are the very few? Go to Github and search for the number of projects using Larevel?
If you thinklarevel
If there are such shortcomings and shortcomings, you can change to another framework,There is no need to follow suit..
Or that sentence:What suits you is the best.
Laravel is complex, but not applicable to normal users.