Looking for a firm determination and reason to learn Laravel?-PHP Tutorial-php.cn

Statement: This question is based on some questions that I have opened my mind to. Please forgive me if there are any mistakes.

What exactly has Laravel subverted in PHP? Is it just to promote Composer? Do these features of Laravel violate the original intention of PHP? PHP was originally characterized by being lightweight, and now it has added namespace and package management. And what are the practical domestic application projects of Laravel? Is it just to develop an ultimate blog like WordPress? And I didn’t find many Laravel-related application projects on GitOsChina. You wouldn’t tell me that there are many on GitHub. You can’t ignore the development and contribution of the domestic Git community just because GitHub is famous. GitOsChina is also very popular in China now. As an influential Git service community, the promotion of Composer will inevitably lead to the increase and poor use of various dependency packages of the project, so that PHP will inevitably become more and more out of scale. What I understand as something that can be widely used is definitely a Swiss Army Knife like JQuery. Because it is lightweight, fast, and flexible, we can use it to expand and develop many things to meet our own needs. There is the BootStrap front-end framework as well, and frameworks like this can become widely popular and fully developed and utilized. I think Laravel's craftsmanship has caused it to be very inflexible, have a difficult learning curve, and so on. In the end, it has become the pet of only a very small number of geeks and fanatics.

X Supplement 20160621 00:36
X------------------------------------- -------------------------->

First of all, thank you for your sincere replies. I have learned a lot from your replies. Here is what I would like to add:

I agree with @飞龙’s point of view:

php is no longer the simple php. I have learned too much about java and lost some of the flexibility that a scripting language should have. Your understanding of php is still in the 3x era.

This is what I have to say about namespaces and package management:

PHP is originally characterized by being lightweight, and now it has added namespace and package management

I hope you won’t be too literal-minded and deviate from my general point of view. I have not limited the namespace and package management to Lavavel. Besides, Lavavel is not capable of allowing PHP to make changes. There is no comparison between Python, Node.Js and PHP. After all, the design purpose and original intention are different, and others have had the concept of package management for a long time. PHP has already lagged far behind in terms of package management. In my opinion, there are many Chinese projects in China. People only use Laravel to make blogs. The blogs they create cannot be compared with WordPress, and there is no comparison. WordPress still supports 3x, and I don’t see anyone insisting on using Composer. Another thing is that the word Lavavel is not very good. Chinese people find it difficult to remember, at least for me.

Maybe I am still stuck in the 3x era like @飞龙 said, even if it is just like @JellyBool said, it is an excuse for me not to make progress.
But I think in everyone’s opinion, JQuery and BootStrap are indeed flexible frameworks, and they cannot be criticized together because of my problem.

There is no intention to bring GitOsChina in. Please don’t mislead others and let others mistakenly think that GitOsChina is not good. For people who are not good at English or cannot surf the Internet scientifically, such as GitOsChina, Coding.net, etc. Such a platform at least provides a learning channel. At least it is where I started to get involved with Git. It cannot be said that people who are not good at English should not learn programming.

Based on everyone’s opinions, my personal idea is to get to know and get in touch with Laravel first depending on the opportunity. If there are many pitfalls at the beginning and I can’t get started for a few days and can’t figure out the door, then I will have to wait for it to arrive. When JQuery becomes really popular in China, I will slowly learn it.

The following only represents the individual’s current level of understanding and does not involve any other groups, organizations or interests

What suits you is the best Like

X Supplement 20160621 08:30
X------------------------------------- -------------------------- >
The following only represents my personal opinion on my current level of understanding. If you don’t know, you don’t know. Based on the basic concept of knowing and not understanding, it does not involve any other groups, organizations or interests

Domestic admirers of Lavavel should not keep talking about Lavavel with a condescending air. They talk about craftsmanship, artist spirit, lightweight, concise and elegant, PHP's latest features and so on all day long. It’s like saying that you must follow me to do 5x, 7x, etc. Why don’t you use Composer? I only use Composer. Are you still doing 3x? To attack old rookies like me, it looks like if you don’t learn the new features of PHP right away, you won’t have to use it and you won’t be able to mix in this circle. Look down on domestic frameworks, look down on DreamWeaver CMS, and look down on WordPress. I even look down on GitOS China. How much effort and sweat others have made to have a decent Git service in China, and how much the domestic programming environment has been improved. Don’t talk about GitHub all day long. Not everyone has the opportunity to go abroad. , not everyone understands Git. What is the programming environment in China and what is the environment abroad? Everyone should be very clear about it. Most people in China are still forced to code for that little salary. Domestic service platforms have domestic services. The reason for the existence of the platform is that it is not you who has the final say whether others develop well or not.

In terms of craftsmanship, is Lavavel as craftsmanlike as Java's many popular frameworks? Is it as simple and elegant as Python's many popular frameworks? Don't abuse these words to exaggerate and praise it, making it mysterious. If the package management is not easy to understand, write more information to make it easier for everyone to understand. If the learning curve is difficult, simplify and optimize the entry methods. If the execution process is not easy to understand, then improve and refine the process analysis. If the Chinese support is not good, write more Chinese language packages and Chinese information. Write as little as possible and write more Chinese information. These later admirers can work together to complete it. I do not rule out that there will be me in the future, but the premise is that everyone knows how to get started easily. Apache, Nginx, and Mysql may not be easy for everyone to use. You need to know how to configure it from the beginning. The one-click environment will come faster. Using the one-click environment does not mean that you will not learn the configuration knowledge. It just lowers the threshold for us to get started. For example, people who are used to using VIM editor say it is great, but it is difficult for ordinary people to get started. It is not easy to use it at first and they are turned away. SublimeText avoids the problems of getting started very well, so it is more Widely popular and admired.

This question has been closed, reason: Unable to obtain exact results

Reply content:

Statement: This question is based on some questions that I have opened my mind to. Please forgive me if there are any mistakes.

X Supplement 20160621 00:36
X------------------------------------- -------------------------->

First of all, thank you for your sincere replies. I have learned a lot from your replies. Here is what I would like to add:

I agree with @飞龙’s point of view:

php is no longer the simple php. I have learned too much about java and lost some of the flexibility that a scripting language should have. Your understanding of php is still in the 3x era.

This is what I have to say about namespaces and package management:

PHP is originally characterized by being lightweight, and now it has added namespace and package management

The following only represents the individual’s current level of understanding and does not involve any other groups, organizations or interests

What suits you is the best Like

In fact, we can’t blame PHP for becoming so complicated now.

When PHP was born, it was also when the WEB was relatively in its infancy. At that time, a small CMS was enough for the website, with simple logic and a small overall scale. No matter how you compiled the code, it would not go too far. The PHP scripting language at this time has solved most of the problems. Even using HTML and PHP mixed coding methods will not make people feel much discomfort. If I remember correctly, this style of coding is called "spaghetti programming".

As the WEB becomes more and more complex, the mixed coding method has become a bit inadequate. The result is that a page has n number of alternating codes of PHP and HTML, which has caused subsequent coders (including myself) to become more and more complex. It’s getting confusing, and it’s not possible to use include to extract some common codes, so the concept of templates appears, and the more representative one is smarty. At this time, you can write the logic into a PHP file, and then load another A template file serves as the presentation layer. This file only contains some necessary PHP logic code, which separates the logic code from the presentation code.

However, the WEB is developing too fast, and soon the code responsible for processing the logic part becomes huge again, including request processing, database connection, and some more general logic. The back-end engineers collapsed. , the more I write, the more bugs there are. So someone wrote a framework to separate these logics, and a number of frameworks such as Codeigniter appeared. Most of these frameworks will use a single entrance to ensure that the logical part is taken over by it, and then separate the MVC layer so that they can perform their respective duties and the code will flow smoothly. But at this time, PHP is no longer the original PHP. It is no longer PHP that can be started in 24 hours. Although you can still use spaghetti programming, even now, but such programming will at least be despised. , so many PHPers were forced to learn a new programming method, euphemistically called: layered programming. But to be honest, programming is much more comfortable if the layers are separated. (Owner, since you are a bit opposed to the Laravel programming method, I guess you should be programming in this type of MVC layered framework. If I say that this also violates the concept of PHP fast programming, can you return to the most original programming method? ? It’s just a guess, don’t mind if you guess wrong)

Later, or even now, WEB is no longer just for simple knowledge sharing, but also for SNS social networking, electronic shopping malls, and B/S service software. As a back-end engineer, it’s all a lot to think about. So some people jumped out to solve various problems. How to solve them? If there are any problems, just solve them, haha. Let me give you an example. For example, using Codeigniter, a framework that most people consider to be somewhat old, to write an e-mall is not a big problem. Although the logic code may be a bit long, you can get through it if you tolerate it, but one day you can look back. When you look at the code, you find that the code on the V side is still OK, the logic is relatively clear, it is just a display, and there is nothing to optimize. The M side is also OK, it is just writing some SQL statements, even if the SQL statements are too complex Well, that is also a matter of database design. Then you look at the C side and feel a little unbearable. There are codes responsible for receiving various GET and POST values, codes for processing various logical calculations, and various codes responsible for verifying data. There are various codes for loading data M and loading the V side. Each function contains at least hundreds of lines, so you plan to extract the logic part of the code and let the C side only be responsible for reading user input data and loading M And V, as for the logical operation part, let's remove another Service layer. If this part is removed, not only will the C side be simpler, but some services can be reused, killing two birds with one stone. When you start to dismantle it, you suddenly find that there is no place to put this layer. Put it in the library. You feel that it is just a place to place independent libraries, not a hierarchical place. Put it in M, and you feel that it destroys MVC itself. The meaning is similar, but there is nothing you can do about it. The rules are not dead. If you can use them, just use them. However, if you use a relatively new framework, they all follow the PSR coding standards. You can create a folder as a layer at will, and then use it on the C side without destroying the existing structure at all. The best thing is that if The code you write can be effectively decoupled, so with composer, you can share what you write with others. This is one of the cool things about many new frameworks.

Then I won’t say much more. If PHP really stagnates and everyone always uses the scripted programming method from long ago, sooner or later it will be eliminated.

Of course I do want to complain. Various new frameworks have brought many new features, which are too difficult to learn...

Here’s the key point: The above is purely a personal complaint. There are some places that have not been verified in detail. They may be wrong. Just treat them as a snack. It would be great if you can point out the mistakes. I don't like trolls.

Well, the front is ready for a fight. The following represents only my personal views and does not involve any other groups, organizations or interests

1. Laravel does not subvert anything in PHP, it just uses many new features of PHP.

2. It’s not to promote composer. Composer is originally a product of the PHP community, but you just don’t understand it.

3. The characteristics of Laravel are completely different from the original intention of PHP. Namespace is a product of PHP, and namespace does not violate the so-called characteristics of 轻量. Behind every technology is to solve a certain problem. The problem in this scenario, to put it simply, is that namespaces were introduced in order to resolve naming conflicts between classes and methods. I personally feel that those who maintain the PHP source code on github made the right decision to add namespaces to PHP. Maintaining the so-called 轻量 features is not an excuse for not making progress. If a language cannot become more suitable for solving problems with the changes of the times, the language will have no vitality after all.

4. Personally, I feel that WordPress and Laravel are not comparable at all.

5. Sorry, I really disagree with this sentence GitOsChina是国内很有影响力的Git服务社区. To be open source, Github must be far behind all other git service communities (rhetorically called it an exaggeration). If it is not open source and is a company's commercial project, the basic choice is to build a self-built git service, so I am not optimistic about it at all GitOsChina是国内很有影响力的Git服务社区. Personally, I don’t think GitOsChina can survive long (welcome a slap in the face), because the ecology of GitOsChina is really depressed.

6. Composer的推广势必会造成项目各种依赖包的增加和烂用, at present, I disagree, do you want to abuse people who read and write projects?

7.这样PHP必然会变得越来越不经量级Can the lightweight you mentioned mean immutable? That’s just an unprogressive interface

8.肯定是像加JQuery一样的瑞士军刀，由于它的轻量级、快捷、灵活, when it comes to lightweight, Jquery is really not on the list. And it is difficult for Jquery to gain the same vitality as before, because front-end development is currently more inclined to MVVM such as Vuejs.

9.还有BootStrap前端框架也是，像这样的框架可以广泛流行并得到充分发展和利用. If you want to find a framework in the PHP community that emphasizes CSS like Bootstrap, it must be Laravel.

10.Laravel的工匠精神，我想会造成了它很不灵活，学习曲线难等等问题. On the contrary, Laravel is very flexible, if you understand IOC.

11.最后成为只有极少数部分极客和狂热者的宠物. Anyone who pays attention to the PHP community and has seen the outside world should not have this idea.

12.Laravel的国内实际应用项目到底有哪些. No talent, I wrote one myself https://laravist.com

So my point of view is: According to this situation, you don’t need to learn Laravel at all. After all, the one that suits you is the best. Everyone has different pursuits.

No one wants to spray you

After reading your question, I have also gone through some thinking process, and I cannot agree with some of the conclusions. A conclusion based on wrong assumptions is not credible, so I will just express a superficial view on your question and hope to learn together.

Laravel is undoubtedly an excellent framework, but the author has never said that he "subverts" or hopes to subvert anything. The author is just an ordinary otaku, spending time with his family, thanking the code, and developing his own framework while interspersed with My own entrepreneurial project, a series of deployment services derived from the Laravel framework, SASS, consulting services, etc. I have been working with Laravel for more than half a year, and I haven’t seen anyone say that this framework subverts anything. I guess the people who tell you this are either crazy fans or people who are accustomed to using exaggerated vocabulary. Regarding programming, I have encountered Just ignore these exaggerated words. Laravel is built on the meticulous and selfless contributions of predecessors in the PHP community, and uses many other developers' open source projects, including Symfony components, as underlying dependencies. Whether it is Laravel or the libraries it depends on, these are not completely new things. It is not a unique way of writing in PHP. Every dependency community has many similar implementations.

Composer and Laravel are not directly related. The former is a dependency management tool that naturally arises when the community develops to a certain extent. It helps developers maintain a large number of dependent libraries and update their versions. For example, if you write a Web yourself Applications are likely to need to complete many aspects such as routing, ORM, request and response, verification, template engine, etc. Now suddenly there is one aspect that you don’t want to write yourself, then you will think of introducing other actively maintained and well-documented libraries. For your own use, when your program has enough functional points, it may be email sending, file system abstraction, queue interface. In all aspects, you have to stand on the shoulders of predecessors to accelerate your own development and let people who are good at it do what they do. . At this time, Composer is the only tool to ensure that you maintain dependency updates, conflicts, and rollbacks. When the community develops to a certain stage, even if there is no Composer, there will still be Overture and Singer. As of today, Composer has become the de facto industry standard in the PHP community. Your lack of understanding of it only shows your own laziness and ignorance. Even if you go to Github to search for PHP projects, you will not think that Composer is promoted by a certain framework.

You said "Laravel's features violate the original intention of PHP", then you'd better explain clearly, what do you think its features are, and what is the original intention of PHP.

PHP’s selfless maintainers, as well as the commercial companies behind it, have never said that PHP is characterized by lightweight. I don’t know what you mean by lightweight. If you add a feature, the community will rely on it. Management tools are lightweight, so among the languages with a large number of users, there are probably no lightweight ones. Getting started with PHP is easy, but that doesn’t mean you can write code in a stupid way and take it for granted. Today's developers have a very morbid mentality. They call Sublime lightweight and PHPStorm heavy. They call small files lightweight and heavy files. But what I can tell you is that the addition and invention of a feature has gone through complex discussions, countless people’s careful thinking, and has precipitated many urgent needs in development practice. You can't just sit there and question other people's original intentions. If a language or tool really makes you feel heartbroken and loses confidence, so that you think it is against common sense, don’t worry, it will definitely be eliminated, because the vast majority of people are not stupid, and the market will naturally eliminate useless products. .

I don’t know about domestic projects. Most of the programming tools you use now are not produced “domestic”, so if you can, don’t just look around you. There is still a lot of great information in the English results. By the way By the way, Laravel is a framework that has a great impact on people's programming style. Please use it with caution, otherwise it may be difficult to return to the past era of writing noodle code.

WordPress is a plug-in-rich content system. I don’t know much about it, but I feel that it and Laravel are not in the same field at all, and they pursue different directions.

GitOSChina is not very influential, including all such services in China. They think that adding a forum and an outsourcing market is micro-innovation, so they localize it. In essence, they are all made by domestic developers who are incompetent. Money, what a thoughtful Chinese language, you don’t have to use your brain at all. A person who always uses Github is unlikely to use what you are talking about. First of all, Github has the most developers in the world. They open source the most products as large companies and organizations. There are millions of the smartest people on the planet gathered here. On the other hand, these people in China are thinking about how to defraud Party A of money all day long. Coders, do you expect him to actually do technology? The world only needs one Git community, maybe two, but the other one is definitely not what you said, a large community that was hurriedly set up by a few people using GitLab. "You cannot ignore the contribution of the domestic Git community just because Github is famous." No one is deliberately ignoring them, they can't see it at all.

"The promotion of Composer will inevitably lead to the increase and poor use of various dependency packages in the project, so PHP will inevitably become more and more immaterial.", It is a bit hasty to judge the importance based on the number of files and dependencies, one page Even poorly written code can consume more resources and weigh more than 10,000 pages. Although PHP is a semi-compiled language when opening Opcache, on most systems, there should be no significant difference if there are dozens more files or dozens less.

"It must be like a Swiss Army Knife with JQuery". jQuery is not a Swiss Army Knife. It is just a compatibility solution derived from the early development of browsers, incomplete standard support, and unprogressive products led by IE, allowing you to unify API writing in different environments. Of course, his role today is also the same. And it will be popular for a long time in the future because of its unified interface. But you can’t call a big, comprehensive thing that can hold everything in it a Swiss Army Knife.

Craftsmanship is just what is claimed on the Laravel website, and so is elegance. The author always has to eat, and there is always a word that reminds you of this framework. Judging from my experience of using two more complex frameworks, Laravel is a very simple framework. If you have a basic OOP background, you can develop it immediately by reading the documentation. Moreover, when viewing the source code, you will often find that the author has not written anything at all. When you see the surprises in the document, you will sigh that it can take into account various complex usage scenarios on the basis of ease of use. Laravel is not the pet of "a few geeks". In the past three years, Laravel has steadily ranked No. 1 in the popularity of the global PHP framework. In mainland China, the number of users and attention have also increased since 2015. For details, you can go to index.baidu .com and look at their search index, drag over all time and look at the growth curve. Even though there are training institutions all over the mainland that produce code monkeys (higher education is not implemented in place and they are driven by profit), a certain framework has in-depth cooperation with training institutions, and in the land where no one can write code without a certain framework, Laravel is slowly growing Be accepted by more programmers who want to grow themselves to new heights.

Halfway through writing, I didn’t really want to write anymore, because it’s so difficult to wake up someone who is pretending to sleep. A profession that requires creating content every day, but it happens to regard new things as its biggest enemy. He also used his only knowledge to make unwarranted inferences that he could not explain the cause and effect of. Although everyone has the right to express their opinions, I feel that when you encounter something that you cannot understand, the first thing you should do is learn and understand it instead of proposing some conclusions that are difficult to convince others.

Personally, I think you misunderstood the relationship between laravel and composer. I’m glad that you got to know laravel through php and there is a composer similar dependency management tool
As for it’s because of composer The introduction of 项目各种依赖包的增加和烂用, I suggest you take a look at node's npm, python's pip, ruby's gem, etc. to see if they have caused abuse,

Some people will say that laravel has copied rails. Indeed, they are very similar. Laravel can be said to be a full-stack development framework, which can quickly web develop and introduce the best solutions in the web. Reasonable technology, such as the introduction of composer dependency management
As for what you mean by inflexibility? Where do you see the inflexibility?
As for the learning curve you mentioned, it is true that laravel’s learning curve is compared to other frameworks较高, but this is also relative. A higher learning curve means that after you learn it well, you will develop faster.

It is recommended that you don’t follow what others say. If you feel it’s not good, you don’t have to learn it. It’s not bad to choose a framework that suits you.
If you feel bad, there is no need to look for any reason to learn laravel.

What exactly has Laravel subverted in PHP? Is it just to promote Composer?
PHP 5.3 already has Composer. There are many projects using Composer besides larevel.
Do these features of Laravel violate the original intention of PHP? PHP was originally characterized by being lightweight, but now it has added namespace and package management.

This is exactly the characteristic of a modern and mature language, and PHP is not a lightweight language.

What are the practical domestic application projects of Laravel? Is it just to develop an ultimate blog like WordPress?

larevel has been launched for a few years, and many domestic projects are developed using it. Just because you haven’t heard of it doesn’t mean you haven’t. In addition, WordPress is no longer a blog, but a small CMS.

And I didn’t find many Laravel-related application projects on GitOsChina. You wouldn’t tell me that there are many on GitHub. You can’t ignore the development and contribution of the domestic Git community just because GitHub is famous. GitOsChina is now also a very influential Git service community in China

Really? I haven't heard of the "famous" GitOsChina, but Github is well known in the developer circle. And there will only be more and more projects using larevel at home and abroad.

The promotion of Composer will inevitably lead to the increase and poor use of various dependency packages in the project, so PHP will inevitably become more and more immaterial.

Nodejs, python and other languages also have their own package managers, and I have never seen any abuse, and PHP itself is not a lightweight language.

What I understand to be widely used is definitely a Swiss Army Knife like JQuery. Because it is lightweight, fast, and flexible, you can also use it to expand and develop many things. Our own needs, as well as the BootStrap front-end framework, a framework like this can be widely popular and fully developed and utilized.

None of the things you mentioned are lightweight, in my opinion they are all heavy or bloated.

Laravel’s craftsmanship, I think, has caused it to be very inflexible, have a difficult learning curve, and so on. In the end, it has become the pet of only a very small number of geeks and fanatics.

This is your personal opinion. What is a minority? Go and search on Github. How many projects use Larevel?

If you think larevel has such shortcomings and deficiencies, you can change to other frameworks. There is no need to follow others blindly .
It’s still the same sentence: What suits you is the best.

Laravel is relatively complicated and most people can’t learn it.