From today, we will officially use cnblogs to record the learning process and various learning documents, and leave a post to commemorate
I have been using 51cto's blog before, but then 51cto blog has undergone a very large version update. After the update, it seems that some bells and whistles have been added, but after the actual experience, it feels extremely difficult to use, and all the previous articles are all typographically confused, etc. various problems. In fact, I personally think that the primary requirement of technical bloggers should be the convenience and speed of writing records and whether the documents can be kept intact and safe for a long time, rather than the various decorations that look fancy but are not very practical. Adding some bells and whistles makes writing and editing more difficult, which I think is a stupid act of putting the cart before the end. However, although this kind of behavior is stupid and tolerable, [the reason why it can be tolerated is that I can understand that after a new version and a new editor appear, it will definitely require a process of learning and adaptation, although it will take us a lot of time (our Time is also very precious, and time also needs to be included in the cost) for self-study of the new version of the editor (51cto will not teach you, you can only rely on your own research) and adaptation, but maybe the new version may really improve (I The level is limited, so I don’t know if there is any progress, but I really feel it intuitively that the difficulty of use has increased a lot.] But the most unbearable reason for me to give up 51cto and switch to other blogs is that the layout of previous articles is all It's messed up, it's so messy that it's impossible to read. Do you want me to manually re-edit one by one? Such a big version change (it can no longer be regarded as a version update or upgrade, but a new set of systems has been changed, from It can be seen from the blog 2.0 written on the publicity page), it is said that there should be internal beta and public beta and other tests, after obtaining user experience feedback, modifying BUG and other operations, can you finally go online and replace the old system? Have you tested the new version before it goes online? Have you asked for our opinion? These articles are all our hard work day and night!!! They are all messed up, what do you think of the previous articles? A lot of the code in it is copied There are errors, should we check line by line every time we copy the code? You are too disrespectful to bloggers, right?
Alas, I am full of tears. Anyway, players of my level don't care at all, so I can't afford to hide it. The articles I wrote on 51cto in the past will be slow when I have time. Export slowly. Another lesson learned is, don’t think that the products operated by big companies and websites must be 100% reliable, and don’t put eggs in the same basket at any time, because maybe the server is a serious server, the technology is serious technology, and the engineer is a serious engineer, but We don't know if the company's leaders are serious leaders or not, haha.