Stackness

Trending Misc

Data as of

These rankings count what people do on Stackness: a trending tool is one that was added to the most stacks in the window, a rising tool is one whose recent additions are the largest share of its total users, and a trending move is the one that collected the most reactions. When a window is too quiet to rank, it widens to the next one and the page says which window it used. This is platform usage, not the imported history series that tool pages and trend waves chart - see where our data comes from.

Browse every tool in Misc

Not enough activity this week - showing this month

#1uv+2

Fast Python package and project manager written in Rust

2 users
#2make+2

Build automation tool using Makefiles

2 users
#3Grunt+2

The JavaScript task runner that made front-end builds routine

2 users
#4Vite+2

Fast front-end build tool and dev server

2 users

Module bundler for JavaScript applications

1 user
#6Gulp+1

Streaming build system for front-end task automation

1 user
#7Biome+1

Fast formatter and linter for JavaScript and TypeScript

1 user
#8pnpm+1

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

2 users
#9Task+1

Task runner and build tool written in Go

1 user
#10ESLint+1

Pluggable linting utility for JavaScript and TypeScript

1 user
#1uv+2

Fast Python package and project manager written in Rust

2 users
#2make+2

Build automation tool using Makefiles

2 users
#3Grunt+2

The JavaScript task runner that made front-end builds routine

2 users
#4Vite+2

Fast front-end build tool and dev server

2 users

Module bundler for JavaScript applications

1 user
#6Gulp+1

Streaming build system for front-end task automation

1 user
#7Biome+1

Fast formatter and linter for JavaScript and TypeScript

1 user
#8pnpm+1

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

2 users
#9Task+1

Task runner and build tool written in Go

1 user
#10ESLint+1

Pluggable linting utility for JavaScript and TypeScript

1 user

Not enough activity this week - showing this month

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

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

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

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

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

No tool is growing fast enough to rank yet.

Supporters get the weekly Stackness trends newsletter and trend waves, the interactive charts of how tools rise and fall over time.