viT-1

The past and the future of hub by Mislav Marohnić 30.01.2020

I have been maintaining hub, the command-line git extension, for 10 years. After 2,100 issues and pull requests closed, 18k+ stars on GitHub, and countless hours invested in it, I thought it might be fitting to reflect on its unlikely past, share a bit about my process working on it, and address the future of GitHub on the command line.

viT-1

Little Known Ways To Utilize GitHub Gists by David Singer 27.02.2020

There are multiple ways to utilize gists. Here are a few examples we have found that are very useful in our daily activities.

• As a task lists.
• Organize notes.
• As a writing platform.
• To Save links.
• To Write anonymous text.
• Track text changes.

viT-1

Searching Github Gists via API isn't supported yet (23.07.2020)

For example: all my shareable gists on JSON, on GitHub Search and simplest (not shareable) form of favorited/starred & for registered github user gists with querying complete word "github" (you can find nothing if you haven't any gist with keyword "github").

viT-1

3 ways to get data from GitHub Gists by Miguel Piedrafita 28.11.2017

4th way: all viT-1 user gists by official API documentation. You can compare with JSON format of viT-1/zvezdoble issues, which have filter ability to use single label/tag, multiple tags & web interface for searching multiple labels. See also GitHub advanced search.

viT-1

GitHub for default branch decided to change the name "Master" 12.06.2020 on twitter. You can join to anti-renaming petition

viT-1

eslint since v7 warns about deprecation of root config Now, if you have eslint config in your project and global config, you should define it as root config (loss or copy/paste all recommended rules - preferred way with saving rules relate to project) or define extends key with file system dotted path! 🤦‍♂️

If you want to have shared rules for different projects and don't want hardcoding path to file with common rules, you should create your custom eslint plugin with your rules (may be based on other recommended rules).

viT-1

Восемь лет в Opera by Vadim Makeev, 2016.11.21

viT-1

GDPR article about on Habr.

Official documents, e.g. WP244

Google 50 Million euros penalty

Пакет Яровой нарушает GDPR Интернет в эпоху границ и ограничений – возможно ли регулировать технологии?

viT-1

Stop using js-classes

Please, stop using classes in JavaScript!!! (not TS) by Michael Krasnov, 2020.01.12

ReactJS: Classes confuse both: people and machines.

Refactoring OOP code is extremely risky! Complex dependency graphs and state scattered all over OOP codebase, make it impossible for the human brain to consider all of the potential issues.

Comparison es6 classes with es5 abilities. Way to VanillaJS OOP: Object literal vs constructor+prototype.

Stop using getters and setters

viT-1

Prefer (or require) named exports from all modules, regardless of how many exports they have! By Thomas Randolph 2019.09.05

Before airbnb-base we can use only one rule: "import/no-default-export": "error" but after airbnb (which want to use default exports) you must to add second rule: "import/prefer-default-export": "off"

Why I've stopped exporting defaults from my JavaScript modules by Nicholas C. Zakas 2019.01.15