Stackness

Misc tools

Most used tools

  1. #1

    Package manager for macOS and Linux

    2 users
  2. #2

    Fast, disk-space-efficient package manager for Node.js

    2 users
  3. #3

    Build automation tool using Makefiles

    2 users
  4. #4

    Fast front-end build tool and dev server

    2 users
  5. #5

    Fast Python package and project manager written in Rust

    2 users
  6. #6

    The JavaScript task runner that made front-end builds routine

    2 users
  7. #7

    Password manager with browser extension

    1 user
  8. #8

    Open-source password manager

    1 user
  9. #9

    Dev tools version manager and task runner

    1 user
  10. #10

    Node Version Manager for managing multiple Node.js versions

    1 user
  11. #11

    API development platform for building and testing APIs

    1 user
  12. #12

    User-friendly command-line HTTP client

    1 user
  13. #13

    Task runner and build tool written in Go

    1 user
  14. #14

    Pluggable linting utility for JavaScript and TypeScript

    1 user
  15. #15

    Fast formatter and linter for JavaScript and TypeScript

    1 user
  16. #16

    Module bundler for JavaScript applications

    1 user
  17. #17

    Streaming build system for front-end task automation

    1 user
  18. #18

    Command-line client for transferring data over any protocol

    1 user
  19. #19

    Command-line toolkit for converting and streaming audio and video

    1 user
  20. #20

    Cross-platform build system generator for C and C++

    1 user
  21. #21

    Extremely fast Python linter and formatter written in Rust

    1 user
  22. #22

    Version manager for switching between Python versions

    1 user
  23. #23

    Universal database tool for developers and analysts

    1 user
  24. #24

    Dependency manager for Swift and Objective-C projects

    1 user
  25. #25

    Open source library for computer vision and image processing tasks.

    1 user
  26. #26

    Productivity tool for macOS with extensible commands

    0 users
  27. #27

    Reproducible package manager and build system

    0 users
  28. #28

    Extendable version manager for multiple runtimes

    0 users
  29. #29

    Fast and simple Node.js version manager

    0 users
  30. #30

    Fast, reliable, and secure dependency management

    0 users
  31. #31

    Default package manager for Node.js

    0 users
  32. #32

    API client for REST, GraphQL, and gRPC

    0 users
  33. #33

    Open-source IDE for exploring and testing APIs

    0 users
  34. #34

    Open-source API development ecosystem

    0 users
  35. #35

    Expose local servers to the internet for testing

    0 users
  36. #36

    Zero-config VPN built on WireGuard

    0 users
  37. #37

    Universal secrets manager for developers

    0 users
  38. #38

    Online regex tester and debugger

    0 users
  39. #39

    Lightweight command-line JSON processor

    0 users
  40. #40

    Command-line YAML, JSON, and XML processor

    0 users
  41. #41

    Command runner alternative to make

    0 users
  42. #42

    Opinionated code formatter for multiple languages

    0 users
  43. #43

    Framework for managing multi-language Git pre-commit hooks

    0 users
  44. #44

    Fast and powerful Git hooks manager

    0 users
  45. #45

    Build and dependency management for Java

    0 users
  46. #46

    Build tool for JVM and Android projects

    0 users
  47. #47

    Module bundler for JavaScript libraries

    0 users
  48. #48

    JavaScript testing framework with zero-config defaults

    0 users
  49. #49

    Flexible JavaScript test framework for Node.js and the browser

    0 users
  50. #50

    Package installer for Python

    0 users

Often paired with

Moves in Misc

by StacknessMiscbackdated

The whole team at one screen, one driver at a time, rotating on a timer. It grew out of pair programming and stayed a minority practice with a devoted following.

63

by StacknessMiscbackdated

GitHub turned code review into a conversation attached to a branch, and the pull request became the unit of work for most teams that followed.

63

by StacknessMiscbackdated

Two developers, one keyboard, one problem. Extreme programming made it a named practice, and it survives mostly as a deliberate tool for onboarding and hard problems rather than as an all-day default.

63

by Sergei GordeichukMiscbackdated

I make tasks locally within the repo with simple backlog/in_progress/done structure. That way LLMs know all the context and I don't have to connect Linear or so. The tasks itself are just simple MD files

52

by StacknessMiscbackdated

Write the failing test first, then the code that makes it pass, then clean up. Kent Beck's 2002 book put a name on the loop, and the argument about how literally to take it has never stopped.

32

Adoption history

Homebrew

History
Collected from public datasets outside Stackness, not from stacks on this site. Each series is scaled to its own peak because the units do not compare. Data sources
Mentions, monthly

Hacker News mentions mentions: 1 mentions (2007) to 70 mentions (2026)

20072012201620212026

Imported from Hacker News mentions

Questions asked, monthly

Stack Exchange data explorer questions asked: 3 questions (2008) to 1 questions (2026)

20082013201720222026

Imported from Stack Exchange data explorer

Usage share, yearly

Stack Overflow developer survey usage share: 26.62 % of respondents (2022) to 25.93 % of respondents (2025)

2022202320242025

Imported from Stack Overflow developer survey

Pageviews, monthly

Wikipedia pageviews pageviews: 3 views (2015) to 4,470 views (2026)

20152018202120232026

Imported from Wikipedia pageviews

pnpm

History
Collected from public datasets outside Stackness, not from stacks on this site. Each series is scaled to its own peak because the units do not compare. Data sources
Mentions, monthly

Hacker News mentions mentions: 5 mentions (2017) to 16 mentions (2026)

20172019202120242026

Imported from Hacker News mentions

Downloads, monthly

npm downloads downloads: 1 downloads (2015) to 597,839,745 downloads (2026)

20152017202020232026

Imported from npm downloads

Questions asked, monthly

Stack Exchange data explorer questions asked: 1 questions (2018) to 3 questions (2026)

20182021202220242026

Imported from Stack Exchange data explorer

Usage share, yearly

Stack Overflow developer survey usage share: 6.47 % of respondents (2023) to 13.56 % of respondents (2025)

202320242025

Imported from Stack Overflow developer survey

Pageviews, monthly

Wikipedia pageviews pageviews: 257 views (2024) to 1,236 views (2026)

202420252026

Imported from Wikipedia pageviews

make

History
Collected from public datasets outside Stackness, not from stacks on this site. Each series is scaled to its own peak because the units do not compare. Data sources
Mentions, monthly

Hacker News mentions mentions: 3 mentions (2007) to 21 mentions (2026)

20072012201620212026

Imported from Hacker News mentions

Usage share, yearly

Stack Overflow developer survey usage share: 20.75 % of respondents (2023) to 23.42 % of respondents (2025)

202320242025

Imported from Stack Overflow developer survey