[michaelwu]

Interesting that there is no mention of eslint. I've always found that the best way to learn a new language is to immediately install the linter and its associated plugin for whatever IDE you're using for instant feedback about potential anti-patterns / dangerous code while you work. Also curious that there's no mention of typescript: a lot of companies have already made the transition because it makes huge projects much easier to manage and read.

[nallerooth]

+1 for eslint.

When it comes to typescript, however, I believe that it's better to learn pure javascript first. Understanding -why- typescript is useful has a lot of value, and saying that you know typescript without having spent time using javascript would raise all kind of warning flags during an interview (focus on what's cool/trendy over deeper knowledge and a lack of desire to fully understand the environment in which you work, to mention some).

Also, a beginner frontend developer who reads a list of HTML tutorials will probably not spend a lot of time in "huge projects" in the beginning of their career.

[daviddiasfront]

@michaelwu, tried to keep it simple for a beginner, and I tried to follow the "web developer roadmap 2017".

ESLint and typescript are more for an intermediate IMO, another list will follow this one and will surely mention ESLint and TypeScript.

[nallerooth]

That's understandable, and to some degree a good decision. But then eslint sometimes help you understand why something is broken, which is especially beneficial to beginners.

Whether to include eslint or not may be worthy of discussion, but since both options have valid points I'll be happy to leave this discussion as is.