I am still proficient in JS, And I am struggling to continue researching the front-end or learning a server language?

I have been engaged in the IT industry for a short period of time and only one year. I feel that H5 has been very popular recently. I want to continue working on the front-end to learn a server language such as php or node, at present, I am still quite familiar with js-related interests. I can watch half of the PHP training videos. I suggest you add some advanced books or URLs to help me learn. Thank you! I have been engaged in the IT industry for a short period of time and only one year. I feel that H5 has been very popular recently. I want to continue working on the front-end to learn a server language such as php or node, at present, I am still quite familiar with js-related interests. I can watch half of the PHP training videos. I suggest you add some advanced books or URLs to help me learn. Thank you! Reply: Of course, the Web Front-end must master a server-side scripting language/runtime environment. The preferred choice is Node.




==2015/9/9 append =

@ Yu Zejiang honey reminded me to say a lot to Node:

Node is compiled by JIT. Calculate the time consumption ranking of the Fibonacci seriesNode is much faster than Ruby, pypy, Lua, PHP, and Python:

There are many front-end pitfalls, fast updates, and many opportunities. If you want to challenge it, consider the front-end.
PS: HTML5 is not H5 brainless node. js. First of all, you should deal with ECMAScript6, because it is already known as a trend, a standard, and a standard of the Enterprise Edition JavaScript.

Front-end React (ES6 has been embraced, the corresponding framework flux, relay, redux, etc.), Angular (2.0 embraces ES6, 1. x still supports ES5.1, But 2.0 is not compatible with earlier versions. Be careful when selecting this option)

Automated tools: gulp and webpack

Backend node framework express and sails

Apsaradb for mongodb, apsaradb for redis, and mysql

The last sentence is: "The frontend profession is twice as hard every 18-24 months." In this age of explosive growth of information, front-End water is getting deeper and deeper # _ # End-to-End typo. The HTML5 front-end backend is end-to-end, and its position in project development is the same as that in theory. However, it seems that many people think that the backend personnel are more arrogant. This is definitely a misunderstanding.
The backend has more rules than the front-end, such as c #, which is easier to use than javascript. However, the front-end knowledge system is very broad. In addition to the minimum html, css, and javascript, there are too many technologies to learn. The efforts made to become a front-end Master are far behind those of the back-end, and the network is spread, every two years, the front-end technology will be updated.
You need to locate at which end you can, but it is basically impossible to achieve both at the same time, go hand in hand, unless you have a big bull gene. Most people turn to the other end after a long time of backend or front-end. Learning Technology: reading books and practicing on your own will not make you grow too much. It is a nonsense to talk about the technical architecture in business scenarios.
My suggestions:
Based on the project you are currently participating in, first go deep into front-end technologies
1) try to investigate technical problems encountered in the project by yourself
2) communicate with your friends to incorporate their technical experience
3) Optimize Your project from multiple perspectives, such as code specifications, performance optimization, and modularization.
4) Go to github to read the code written by the experts during the period, and use the best method to reach the highest level.
5) Let's look at the front-end architecture knowledge, the best choice, and self-recommendation.
Http://muhu28.com
6) There are many ways to communicate with experts in the industry. There are many communication channels, such as online open classes and offline face-to-face communication.

I am optimistic that many people will often ask which question to learn. In my personal experience, do not look around and pick up the West. In the end, it is a half bottle. This is not a good deal.

In addition, I have learned more about backend implementation, participated in backend development, and worked as a full-stack engineer.
The front and back separation, disadvantages, adds a layer of communication path, some small companies prefer full-stack engineers, all engaged by one person,
Big companies have detailed division of labor, and often separate the front and back ends. Each has its own advantages and disadvantages, and the energy permits. There is no harm if you want to learn more.

Don't hesitate, brother. Focus on you. Come on, brother. You are the best. All the help materials play a role in actual practice, and the results will be rewarded only by trying to make projects. The front-end must be refined, and the back-end should at least be fine. After all, is the full stack a trend that can change the title by mistake ???