preface
Some of you have seen (or at least heard of) GitHub, which has a section called Issues:
When you find a bug or have a problem using a common library or framework, you can ask questions in the Issues module and wait for the repository author or other developers using the repository to answer them.
The most famous case is the Deno incident. Ryan, the father of Node, addresses the mistakes in the design of Node and expresses his dissatisfaction with the current direction of Node.
So he decided to make another one, and called it Deno:
This has alarmed a large number of Chinese people who are eating melons. They inherited the good tradition of emperor Ba’s war and nothing grows, and ran to Deno’s issues.
- To learn without moving
- Please don’t update
- The front end is too difficult
The issue that led to other normal reports of bugs was flooded, causing Ryan to directly close the issue, and the image of Chinese programmers in the world plummeted further.
In fact, very few Chinese programmers have actually studied Deno systematically. Most of them just read one or two articles and have a general idea of what Deno does and how it is different from Node. But that doesn’t stop programmers who never really got to know Deno from making crazy jokes.
- ECMAScript has a little sugar in it
- Vue out 3.0 ==== learn not to move
- Webpack 5.0 ===
- There’s a Vite in Yuyu Creek
In the end, whatever youyuxi posts on weibo, no matter whether it is related to technology or not, can be seen in the comments section:
Although many people in the study can not move is just a joke, life or to continue, isn’t it? In order to limit this behavior, GitHub has previously introduced a feature that automatically closes the issue if it does not fit the format of the question. However, the problem is that GitHub is missing a very important feature: The comments section!
The comments section
Although GitHub is a professional community, many people don’t want to go there to find open source projects, create their own remote repositories, or mention issues or PR. Since it is a community, then there should be other communities have some features, like many people brush brush weibo trill, after you have read some key points to open the comments section, even if you don’t speak also want to look at what everybody says, sometimes comments section is interesting than the body, even in the comments section is talent, listen and speak…
So first of all, we go to our home page, and you can see this prompt:
The little box under Settings says:
Try the GitHub comments section! (Beta)
The comments section allows community members to have conversations or ask questions without having to open Issues. Click Get Started to try out this new feature.
So next, if we click the Get Started button, it will take us to the Settings page, where we can find:
Just check the box in the upper left corner and your project will have this extra TAB:
If we click on the Set Up Discussions button:
It jumps to:
You can see that the comment area also supports dragging and dropping video files, as long as it is in MP4 or MOV format. With the comment area, it will be much better. Let’s also look for some well-known open source projects that have opened discussion areas.
Node
After a long search, there are no comment sections for Vue, React, Angular, JQuery, etc. However, Node and Deno do. Let’s take a look at what Node’s comment sections are saying:
- Options for default package management
- Node.js Binary Management Summit
- HTTPS Imports
- Better signal processing
- Consistent environment variables
- Deprecate legacy urls
- Official plugin for Node.js
- What is the best way to inherit from the Native end to EventTarget?
- Modify the LTS schedule
Let’s click on the first one, options for Default package management, and check it out:
I think we should seriously consider replacing NPM with YARN as the default package manager. Yarn is compatible with NPM and provides higher performance. It also supports a variety of functions and is being actively and rapidly developed. It has a huge impact on the community, with nearly 200,000 warehouses on GitHub that use it in some way. Making it the default package management tool could benefit both the community and the entire Node ecosystem.
Then a little like 👍, smiling face 😄, love ❤️, and even the rocket 🚀, but also attention
The comment below said:
That’s a lot like #9161.
conclusion
Feel this thing is a bit like stick, so that we can finally rest assured bold building! However, after watching a circle has been in that said not to learn much, basically are based on discussion issues, with this function feel more interactive, if you have their own GitHub open source project, go to open it! Find out how much people laugh or praise your project.
This article was published on the official account “Front-end Learning does not Move”.
Previous excellent article
- Vue 3.0.3: New CSS variable passing and the latest Ref Proposal
- You Yuxi: Ref Grammar Sugar Proposal
- “Double 11 small black box is cool? Let’s use CSS variables to improve!”
- “Don’t underestimate the nine grid, one question can let a candidate reveal his true colors!”
- “Mobile Layout Interview Questions to test your CSS Skills (Center)”
- A series of confusing behaviors after setting prototype Objects as Proxies
- Vue’s Super Fun New Feature: DOM Portal
- Create your own Visual Data Map without any libraries
- “Use of React’s Super-popular CSS-in-JS Library in the Vue Project: Styled – Components”
- Is It Finally Vue’s Turn to Inspire React?
- A Small Pit in Vue3 on IOS
- Upgrade your React project to Immer instead of Immutable by 2020
- “Soul Interrogation from the Author of React Hooks and Immutable”
- Good news, Vue3 official document is available in Chinese!
- Hooks use of the New VUe-Router
- Vue 3:20 Years of Status Updates
- React 17 is officially a transition version!
- Yu Yuxi: The Design Process of Vue3
- The Father of Node’s refactoring Deno is finally released. Will it Replace Node after all?
- The Vue3 beta was released early this morning and openly supports scaffolding!