Skip to content

Instantly share code, notes, and snippets.

@crutchcorn

crutchcorn/preface-framework-specifics.md

Created July 8, 2022 06:21
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save crutchcorn/362f3e878ad6d2323f1b95ed483394c2 to your computer and use it in GitHub Desktop.
Save crutchcorn/362f3e878ad6d2323f1b95ed483394c2 to your computer and use it in GitHub Desktop.
Download ZIP
An early draft of one heading in the Preface of "The Framework Field Guide". https://framework.guide
Raw
preface-framework-specifics.md

A note on framework specifics

As a final note, before I send you into the rest of the book/course, I want to touch on a few points about these frameworks:

  • React has two different ways of writing code: Using classes and "Hooks".

While React classes are more similar to Angular or Vue's Option API, I've decided to write this book/course using React's "Hooks" method as references for the components.

This is because, while classes are still a part of the most modern versions of React, they've drastically fallen out of favor in comparison to React Hooks. I want to try to make this book representative of real-world codebases you're likely to run into with modern versions of these frameworks, so I thought it only made sense to go with Hooks.

That all said, the core concepts outlined in this book/course apply to both of these methods, so if you want to learn the React class API after the fact, it should be easier with this foundation of learning.

  • Angular is not AngularJS.

Despite the similarities in their names, these two are entirely distinct entities. More specifically, AngularJS was originally released in 2010 and was followed up by the initial release of Angular in 2016. Despite this shared lineage, the core concepts shifted drastically between these two releases. For all intents and purposes, you will not know AngularJS at the end of this book: You will know Angular.

  • Vue has two different ways of writing code: The "Options" API and the "Composition" API.

While the "Options" API has been around for longer and is more similar to Angular's classes, this book will be using Vue's "Composition API". This is for a few reasons:

  1. The Composition API is newer and seemingly favored over the Options API for new applications.
  2. The Composition API shares a bit of DNA with React's Hooks, which makes explaining some of the cross-framework concepts easier.
  3. The Options API is relatively trivial to learn once you have a strong grasp of the options API.
  4. Their documentation does a good job at providing code samples in both Options API and Composition API - allowing you to learn both even easier.
  5. Evan You, the project's creator and lead maintainer, told me to. 😝

Similarly, this book will not cover Vue's other upcoming compiler-based syntax choice, the upcoming $ref sugar. However, a future book in this series will walk you through all of these different APIs, why they exist, and how they build on-top of one-another.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment