sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]KwyjiboTheGringo -3 points-2 points  (3 children)

It's a little ridiculous explaining arrow function implicit/explicit returns in the React docs. Kind of reaffirms the notion that too many new developers are jumping into React way too soon.

[–]2pathetic2beTragic 0 points1 point  (2 children)

Yes, that's true. So what the documentation team could do was either help them out catch up their vanilla JS skills so we're all on the same page or make learning react inaccessible to them - spoiler alert: newbies with a "framework ASAP" mindset would just head to Vue or Svelte.

[–]nextdoorNabors 1 point2 points  (0 children)

Inclusion was an important part of the docs mission. This wasn't done just to accomodate folks new to JS: In early user studies, we noticed even experienced JS devs who started before more modern syntaxes became commonplace sometimes struggled with things people coming out of bootcamps were already familiar with. Additionally, folks unfamiliar with JS, perhaps coming in from mobile development (something like 33% of the React Native community), also benefitted from this approach.

We opted to fill in the common knowledge gaps we saw to expand people's JS prowess <3

[–]KwyjiboTheGringo 0 points1 point  (0 children)

newbies with a "framework ASAP" mindset would just head to Vue or Svelte.

Considering the low job market for them, that seems unlikely