Personal blog technology evolution stream account

One person’s point of view, it is inevitable that one side and mistakes, welcome to discuss and take ax,:)

Written in front

I used IK8 (the new show of the Netease class), blog China, Sina blog, Baidu space, I feel that I have written blogs in facts: I don’t have to manage the server, don’t write bloggers yourself, don’t use yourself to deal with domain name resolution, but also free And there is a platform-based communication ring.

But use with use, will find:

The domain name is not what you want, the link of the article is a number or a random string is not good, it is not good.

Post-released articles will change due to system upgrades, and the original link generates changes, affects the result. And after using a three or four domain domain name, the weight is relatively low.

The publishing content contains code, showing unfriendly, or having a problem.

When the content graphic is mixed, the picture shows the way to the dead, or it is a picture of the picture “Row”, the opening time is long, it is not easy to find the figure.

Style definition is getting lower and lower, and the officially upgraded, some of the past styles and code “fail”.

The background music and Flash are not free to use at the time.

Comments did not or lack of expression.

Later, various blog platforms were seriously commercialized or died in success, and the problems of the article were serious.

In summary: Dancing with shackles, not free; the data is in other people’s hands, and the safety is low.

So what to do, self-built blogs, after all, work, do it, you must first take care of them. Some people will say that the focus of the blog is in the article, but for me, in the process of writing blogs, achieving different best programs may be the highest.

During the front and rear ends

During this period, what is the front-end engineer, the front and back, everyone is a programmer.

The previous period is mainly based on pure static pages, and the later period is mainly used with dynamic scripting to mix output static resources (ÔÓ ÄÚ Áª ½Å ½Å ºÍ ºÍ ºÍ)).

The form of the database includes MSSQL / MySQL / SQLLITE / TXTDB / …

The SHTML + SSI server contains, various include mode template multiplexed + Simple CRUD Backstage + System Environment Configuration is a complete architectural solution.

Until now, you see some older programmers and old Neshouses are still using a very early text database or HTML page as a blog. (This type of website in Hong Kong, Macao and Taiwan and Education Network)

I remember the original department Leader @ СÂí once said: he should count the first front end of China. (Ali eaten China Yahoo, the position of the front-end development engineer appeared in the Chinese market.)

In the period of everyone habits, “front end” is called “front desk”, most pages are static, and a few use “dynamic pages” The website will use ASP / PHP / JSP, but in fact, the last two are not much.

It is worth mentioning that the Nine City Community has been pHP products.

I entered this later, the high school school, who did not hurt, at the time, started to buy a four-year-old 4 line (the actual double line) of the dream tourism technology.

It coincides with the PHP performance battle, and the server has no authorization fees, plus the such as big cow integrates the APMSERV and other environments, and does not need to perform system configuration in the O’Reilly book. Start Server. (The ASP NetBox build environment is of course simple, but the PHP trend is not reversible …)

The Sablog is called the fastest blog system at the time. The author has made a lot of database table design, DB Query, page output content control. When most bloggers do not use static, the static page is started.

It and the later Sablog-x contains the functions required for most blogs: archive, search, site map, custom page, custom route, RSS, pingback …

The emergence of Sablog has affected many people, of course, here it competing: pjblog, oblog, zblog is a relatively positive impact of personal blogs.

Age of the front and rear end

The blog in this period rarely sees the system based on pure static pages, most of which is a dynamic page rendering page structure, and the front-end resource that is introduced into units.

Since the ASP procedures are less and less, and those who use mysql as the database in the use of MySQL.

At this time, the dynamic script acts as a leading, and there is a lot of functions that we are still in use, such as: role control, user contribution, subscription (including mail push), article password protection, points download, statistics (download count, reading count, Access count …), anti-theft chain and stealing resources based on dynamic scripts, timed release, watermark signature, station chain prompt, etc.

The architecture scheme becomes the mainstream is the back-end + of the LAMP / WAMP + CMS type.

Weaving dreams, easy to wait, also passenger strings, a multiplayer blog system (now you can see them related to features …)

WordPress won’t know the fire from 1.x ~ 2.x, with an excellent visible editor (cut off the earliest MARKDOWN), and RSS support (AtOM / RSS / RSS2), Relatively rich plug-in topic libraries, as well as low-versions of environmental demand (minimum php requirements in the same kind), is widely accepted, including more interesting features, including multi-level user role permissions, and advocacy sharing links. The forefront growing era

Due to the problem of the life cycle of the program, most of the program systems designed earlier is consistent with the needs of the current era. Therefore, the either function can not be able to keep up, and is abandoned by the user, either rush to integrate the function, the system is getting bloated.

The blog users during this period emphasize speed and resource utilization than ever.

So, many of them were originally doing things, they were moved to the front end. The server starts a lot of interfaces. The front end began to pay attention to the method and build mode.

Architecture schemes and now look like, partial rear end separation, display layer and business separation, page structure and front-end resource loading majority is also controlled by the backend.

A variety of rendering front-end pages, the style of the style take over, everyone knows that JS and CSS can make the page change so fun, so the front-end scripts and styles have been abused at the site without thinking.

In addition, “Yahoo!”

At this time, Bootstrap / Pure / Semantic UI helped the front end to solve a part of the growing workload, on the one hand, dug, the lack of structured structure and too customized big pit.

After discovering that the server response is fast, the front end can further evolve after the CDN or the front end resource can bring the best experience.

The era of front-end high speed iteration

During the time, the front end complicates increasingly obvious, in order to reduce complexity, one hand in order to use a lot of use in faster development, framework and design mode, and at the same time, the front end begins to use the front-end template and the front end loader for resources. Management, further and server-responsive separation.

The rear end scheme is relatively changed, except for the evolution of the interface, and substitute some plain text interface for the interface for RESTful or false Restful.

The front end is more push, more diverse font selection, reasonable resource modular use, a large amount of CSS animation completely replaced Flash, CSS animation is greater than JS animation …

A large number of bistelishes, stacks that do not manage their plugins, and the styles are also redundant in multiple iterations, and the back-end output template is not adapted to front-end logic.

WordPress and Bootstrap continue to be sought after, directly and indirectly promoted the development of the front end: especially in web font, information push, tripartite platform integration, front-end modular, https, same configuration development, OOCSS, style pre-(post), CSS3 animation effect …

WebFonts / iconFont technology is ripening, and the previous SVG font faded out of the stage.

The front end has a mad output of the MV * mode frame, modular tool, and a series of build tools.

At the same time, due to real-time communication needs, the beautiful wish of the same development, the full stack of Node.js based on Express / framework has also entered everyone’s line of sight, ghost came.

Subsequently, ES6 / ES7’s new grammar support, smarter front-end scaffolding and front-end build tool, even CI support and more advanced distribution systems.

So what kind of solution is suitable for the current personal blog?