Editor & IDE tools
Most used tools
- #1
- #2
- #3
- #4
- #5
- #6
- #7
- #8
- #9
- #10
- #11
- #12
- #13
- #14
- #15
- #16
- #17
- #18
- #19
- #20
- #21
- #22
- #23
- #24
- #25
- #26
- #27
- #28
- #29
- #30
- #31
- #32
- #33
- #34
- #35
- #36
- #37
- #38
- #39
A fast Python code formatter that enforces a consistent style and reduces formatting debates.
0 users - #40
- #41
A rich text editor framework with built-in real-time collaborative editing capabilities.
0 users - #42
A framework for building rich text editors on the web with extensible plugin architecture.
0 users - #43
Visual management tool for OpenAI Codex with API switching, session sync, and skills management.
0 users - #44
Framework for building portable developer tool integrations that work across multiple viewers and environments.
0 users - #45
Browser-based developer tools UI for inspecting and debugging web applications.
0 users - #46
A Python library for building rich terminal user interfaces with a focus on developer experience.
0 users - #47
- #48
Set of tools for building advanced developer tools and debugging interfaces for React applications.
0 users
Rising this month
- Cursor 3 added in the last 30 days, 100% of its 3 users
- JetBrains PyCharm 4 added in the last 30 days, 80% of its 5 users
- Visual Studio Code 1 added in the last 30 days, 25% of its 4 users
Often paired with
Moves in Editor & IDE
by Mika JohanssonEditor & IDE
I used to write end to end tests for nearly everything. If a user could do it, I automated it in Playwright. The test suite grew to about two hundred scenarios, each one spinning up a browser, navigating through the UI, waiting for async operations to settle, taking screenshots on failure. A single change to a form label could break fifteen tests that had nothing to do with the logic I modified. The feedback loop stretched past ten minutes for each run. I started moving most of those tests down a layer into Vitest integration tests that call my backend handlers directly or render components with realistic fixtures. My end to end tests now cover the paths that would actually shut down the business: user signup, checkout, the core workflow that customers pay for. Everything else lives in tests that run in milliseconds and point directly at the broken function. A concrete example from last month: instead of an end to end test that logs in, navigates to settings, uploads an avatar, waits for the UI to confirm the upload, and takes a screenshot, I now have an integration test that calls my upload handler with a test file, asserts the return value, and another test that verifies the component renders the new avatar URL. Those run in about sixty milliseconds total. The end to end test exists only to confirm the whole flow hangs together maybe once per release. The honest limitation is that integration tests do not catch issues in the actual browser's rendering engine or in third party authentication systems. If your business depends on the visual layout being pixel perfect or on OAuth tokens working exactly as the provider implements them, you still need end to end coverage for those specific paths.
Adoption history
JetBrains PyCharm
Hacker News mentions mentions: 9 mentions (2010) to 13 mentions (2026)
Imported from Hacker News mentions
Stack Exchange data explorer questions asked: 1 questions (2010) to 3 questions (2026)
Imported from Stack Exchange data explorer
Stack Overflow developer survey usage share: 9.12 % of respondents (2017) to 15.14 % of respondents (2025)
Imported from Stack Overflow developer survey
Wikipedia pageviews pageviews: 6,847 views (2015) to 4,794 views (2026)
Imported from Wikipedia pageviews
Visual Studio Code
Hacker News mentions mentions: 1 mentions (2015) to 154 mentions (2026)
Imported from Hacker News mentions
Stack Exchange data explorer questions asked: 1 questions (2010) to 23 questions (2026)
Imported from Stack Exchange data explorer
Stack Overflow developer survey usage share: 19.05 % of respondents (2017) to 76.37 % of respondents (2025)
Imported from Stack Overflow developer survey
Wikipedia pageviews pageviews: 6,424 views (2015) to 33,366 views (2026)
Imported from Wikipedia pageviews
Cursor
Hacker News mentions mentions: 23 mentions (2023) to 25 mentions (2026)
Imported from Hacker News mentions
Stack Exchange data explorer questions asked: 3 questions (2009) to 1 questions (2024)
Imported from Stack Exchange data explorer