GAGarbage·Oct 30, 2020Submission
Idiomatic.js: Principles of Writing Consistent, Idiomatic JavaScript
1 points · Open discussionrwaldron
idiomatic.js
Web Development2011–2020
rwaldron / idiomatic.js
idiomatic.js
Principles of Writing Consistent, Idiomatic JavaScript
13Distinct people
15Mentions
0Explicit recommenders
25.7KGitHub stars
What to know before exploring
What it is
Principles of Writing Consistent, Idiomatic JavaScript
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year15 dated mentions
Observed mentions: 2011-08-03 16:13:40 UTC to 2020-10-30 14:15:17 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2011 | 2011-01-01 00:00:00 UTC | 2012-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 3 | 3 | 0 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 3 | 3 | 0 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
15 sourcesThe history of JS style standards is a lesson in ignoring prior work:
- In the beginning was the jQuery style guidelines, which started for jQuery but were eventually for general JS https://contribute.jquery.org/style-guide/js/
- Then there was idiomatic.js, from a massive bunch of JS community leaders https://github.com/rwaldron/idiomatic.js/, evolving some of the principles of jQuery style guidelines.
- Then AirBnB made their own style guides because they didn't realise the jQuery guidelines or Idiomatic existed
- Feross and some other people made 'Standard' JS, ignoring the previous 3 standards, and said it's standard because, well: https://github.com/standard/standard#but-this-isnt-a-real-we... (see 'tape' and how it's 'the only test framework which supports TAP' because the tape author invented TAP). https://standardjs.com/
- Current
Read the rest
ly most JS devs who have been around a while use Prettier instead of eslint because it formats the code rather than just complaining (recent versions of Standard apparently do this too, but that came later) https://prettier.io/
Feross himself is awesome. The name 'standardJS' was a poor choice.
Principles of Writing Consistent, Idiomatic JavaScript
2 points · Open discussionAlternatively, idiomatic.js https://github.com/rwaldron/idiomatic.js/, an older publication with more people contributing to it.
In Airbnb JavaScript Style GuideAmen! Though I am partial to idiomatic.js' whitespace suggestions:
https://github.com/rwaldron/idiomatic.js#spacing
Much easier to skim/parse quickly, at least for me.
In Airbnb JavaScript Style GuideNot really sure we need another one of these: Idiomatic.JS[1] is far more complete, and if you want an opinion, just seek the style of Google[2].
[1] = https://github.com/rwaldron/idiomatic.js/
[2] = https://google-styleguide.googlecode.com/svn/trunk/javascrip...
In A JavaScript Quality Guide> Always put 'use strict'; at the top of your modules.
'use strict'; should be in the top of the scope you control. A global 'use strict'; would place the global scope into strict mode, so all your imported modules would be under strict mode too, and then third party code would break and you don't know why. IIRC jshint will pick this up.
To be honest, the whole guide seems like a shorter, less comprehensive version of the JS community's own Idiomatic JS https://github.com/rwaldron/idiomatic.js/
In A JavaScript Quality GuidePrinciples of Writing Consistent, Idiomatic JavaScript
1 points · Open discussionPrinciples of Writing Consistent, Idiomatic JavaScript
4 points · Open discussionPrinciples of Writing Consistent, Idiomatic JavaScript
3 points · Open discussionPrinciples of Writing Consistent, Idiomatic JavaScript
3 points · Open discussionPrinciples of writing consistent, idiomatic JavaScript
3 points · Open discussion