Chuyển đến nội dung chính

Front-end technical trend observation 2019

Top GitHub projects

This is trend of front-end technology that may helpful for you.

Experience Technology


JS implementation of the class Excel form, it is very convenient to embed your own project


Automatic formatting<input />Input, easy to deal with credit card input, mobile phone number input, date input and other scenarios


Didi's cross-end development framework, class VUE syntax, multi-terminal rendering


Functional Web file Upload components, modular plug-in, for modern front-end system


When the mouse hovers over the link, the preload page starts and opens directly in seconds after clicking.


Simple and easy-to-use lightweight interactive command prompt, which is a must


Open source AI dialogue robot, you can write your own modules to help improve your daily work efficiency


Pure JS full-text search engine, zero dependency, support for browser and Node.js, compact size


Image recognition ability based on Tensorflow JS, no server support required


It is said that Electron can run Windows 95?


Efficiency tools 

By replacing the URL, you can easily view the commit history of any file in any GitHub repository.


Electron-based cross-platform downloader, full protocol support (HTTP/FTP/BT/Baidu network disk)


Automatically generate visual tree code structure diagram to help you understand complex codebase


Summary 

In addition to doing Hello World and To-do app for beginners, is it better to be complicated? This is a collection of blogging demo apps built using various technology stacks.


Collected a large number of Node.js best practices


Thanks for reading

Nhận xét

Bài đăng phổ biến từ blog này

How to ensure double write consistency between the cache and the database?

Interview question How to ensure double write consistency between the cache and the database? Interviewer psychoanalysis You only need to use the cache, it may involve double storage and double storage of the database. As long as you double write, there will be data consistency problems. How do you solve the consistency problem? Analysis of interview questions In general, if you allow the cache to be slightly inconsistent with the database, that is, if your system  is not strictly required to  "cache + database" must be consistent, it is best not to do this, namely:  read request Serialize the write request  and string it into a  memory queue  . Serialization guarantees that there will be no inconsistencies, but it will also result in a significant reduction in system throughput, supporting a request on the line with machines that are several times larger than normal. Cache Aside Pattern The most classic cache + database read and write mode...

Storing Enum like String

In this post, i want to share about storing Enum into Database (Reddis, NoSQL,...) as String then load it again as Enum type. In Ecomerce Application, we use NoSQL repository to do CRUD with DB. Behind the sense, it use some json library(ex: Jackson) to parse your object to JSON and store to DB. With java objects, it work well but for enum type, we may lose old data after we change eum property. Example we have enum: and it is used in Person class: If we persist person object to ivy repo, the JSON after serialization will look like this: This JSON just type String so when we load this from persistence, it will be deserialized and we can get back the correct type enum for property status. Just assume that after several months, customer want to change this enum, he want to rename the property MARRIED to GET_MARRIED, So for all data was persisted after that time it’s fine, but not the old one. we lost all data about status because system does not know that MARRIED now become GET...