News for hackers. Stuff that matters.
Re:Front-End Developer Handbook by FLUX-YOU on Saturday April 14, 2018 @09:12AM (#16837185)
Looking back and forth between code and docs just to remember the shape of returned objects is annoying and probably the worst for productivity.

I imagine most people using vanilla JS have significant amounts of objects memorized.

Re:Front-End Developer Handbook by zdragnar on Saturday April 14, 2018 @10:00AM (#16837334)
IDEs like webstorm can ostensibly be quite helpful if you use jsdoc style annotations.

However, in my experience, once a code base is big enough, you can open almost any file and find documentation that's out of date, incorrectly copy-pasted, or some other major issue. TS, on the other hand, at least forces you to stay correct, which is ultimately what convinced me to switch.

Re:Front-End Developer Handbook by nothrabannosir on Saturday April 14, 2018 @10:14AM (#16837382)
> jsdoc style annotations

Which are a form of type annotations. Case in point: the typescript compiler can actually parse those, in .js files, and yield appropriate warnings on errors. See the //@ts-check annotation.

Re:Front-End Developer Handbook by zdragnar on Saturday April 14, 2018 @11:00AM (#16837581)
It'd be a lot less effort to just use TS imho.
Re:Front-End Developer Handbook by zdragnar on Saturday April 14, 2018 @12:32PM (#16838042)
Edit: I meant jsdoc-style, not "style annotations".
Re:Front-End Developer Handbook by speg on Saturday April 14, 2018 @09:36AM (#16837269)
IF there any docs!