# React.js in the small

DevFeed: [React.js in the small](<https://devfeed.tech/articles/react-js-in-the-small-32153.md>)

Original publisher: [Read original article](<https://adambard.com/blog/react-in-the-small/>)

Published: 2016-03-26T00:00:00Z

Content type: opinion

Language: en

Sources: [Adam Bard](<https://devfeed.tech/sources/adam-bard.md>)

Topics: [React](<https://devfeed.tech/topics/react.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Document Object Model (DOM)](<https://devfeed.tech/topics/dom.md>), [Angular](<https://devfeed.tech/topics/angular.md>)

Tags: [html](<https://devfeed.tech/tags/html.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [react](<https://devfeed.tech/tags/react.md>)

## AI overview

A developer describes using React.js for a small web application that randomly combines a language, framework, and datastore into an acronym. The article discusses React components, properties, state, and hand-written JavaScript DOM construction without JSX.

## Source excerpt

I'm a big fan of accessible technologies. I get suspicious whenever I encounter a framework or library that is "not worth it for a small project," because that is a coded statement that means either "It has a broad scope of features that a small project won't take advantage of," or "it trades off simplicity or user experience for performance or other reasons." Accessibility also helps open-source projects move from obscure to ubiquitous; if jQuery had required a command-line tool to compile it when it came out, I can practically guarantee you wouldn't have ever heard about it.