Reid Burke

Fastfetch is a Neofetch-like tool for fetching system information and displaying it prettily. It is written mainly in C, with performance and customizability in mind.

brew install fastfetch

Why Fastfetch?

From the README:

1. Fastfetch is actively maintained.
2. Fastfetch is faster. As the name suggests.
3. Fastfetch has a greater number of features, though by default fastfetch only has a few modules enabled; use fastfetch -c all to find what you want.
4. Fastfetch is more configurable. You can find more information in the Wiki: https://github.com/fastfetch-cli/fastfetch/wiki/Configuration.
5. Fastfetch is more polished. For example, neofetch prints 555 MiB in the Memory module and 23 G in the Disk module, whereas fastfetch prints 555.00 MiB and 22.97 GiB respectively.
6. Fastfetch is more accurate. For example, neofetch never actually supports the Wayland protocol.

Discovered from looking at this Ghostty post on X:

Whenever there’s a new terminal emulator, I’d hesitantly try it out and then switch back to iTerm2

Ghostty is the exception. It’s so snappy, doesn’t get in my way, has sensible default settings, etc. It’s now my go-to choice ?

brew install –cask ghostty pic.twitter.com/ooDPHTUujb

— Jane Manchun Wong (@wongmjane) December 31, 2024

You may have heard of React Scan for automatically detecting performance issues. It uses Bippy internally. From the README:

a react fiber is a “unit of execution.” this means react will do something based on the data in a fiber. each fiber either represents a composite (function/class component) or a host (dom element).

fibers are useful because they contain information about the react app (component props, state, contexts, etc.). a simplified version of a fiber looks roughly like this:

interface Fiber {
  // component type (function/class)
  type: any;

  child: Fiber | null;
  sibling: Fiber | null;

  // stateNode is the host fiber (e.g. DOM element)
  stateNode: Node | null;

  // parent fiber
  return: Fiber | null;

  // the previous or current version of the fiber
  alternate: Fiber | null;

  // saved props input
  memoizedProps: any;

  // state (useState, useReducer, useSES, etc.)
  memoizedState: any;

  // contexts (useContext)
  dependencies: Dependencies | null;

  // effects (useEffect, useLayoutEffect, etc.)
  updateQueue: any;
}

Further reading and watching:

• Why does React have “Rules of Hooks?”
• How does React re-render internally?
• Live visualization of a fiber tree

why does React have "Rules of Hooks?" pic.twitter.com/jOL4TpKeTn

— Aiden Bai (@aidenybai) December 31, 2024