Other softwareAI models and assistantsLibraries and frameworksOperating systems and desktopMedia and creativeAI coding toolsInfrastructure and DevOpsTerminal and shellBrowsers and extensionsEmail and chatSelf-hosted and home serverNetworking and VPNEditors and IDEsSecurity and passwordsProductivityDatabasesFiles, sync and backupGit and code hostingNotes and knowledgeMonitoring and analyticsSearchFinance
Libraries and frameworks
What HN commenters recommend, ranked by distinct recommenders. Under each: what people praise most and the most common caveat, or the strongest quote where there is no summary yet.
- 1.Loved for Reproducible environments, Agents and LLMs · Caveat Learning curve
- 2.Loved for Simpler workflows, Speed · Caveat CLI UX
- 3.Loved for Batteries included, Admin interface · Caveat Performance
- 4.Loved for Minimal JavaScript, Backend pairing · Caveat Complexity growth
- 5.Loved for All-in-one environment, Replaces older tools · Caveat Scope creep
- 6.Loved for Essential on Mac, Linux support · Caveat Old macOS dropped
- 7.Loved for Productivity, CRUD web apps · Caveat Non-standard requirements
- 8.Loved for Interactive UIs, Developer experience · Caveat Complexity and bloat
- 9.Loved for Easy static sites, Simple, unobtrusive · Caveat Acquisition uncertainty
- 10.Loved for Developer experience, Close to web platform · Caveat Tooling support
- 11.Loved for Speed, Node compatibility · Caveat Rewrite trust
- 12.Loved for AI agent testing, End-to-end testing · Caveat Agent UX limits
- 13.Loved for Ergonomics, LLM-friendly · Caveat Class soup
- 14.Loved for Cross-platform reach, Developer experience · Caveat Non-native feel
- 15.Loved for Ecosystem and tooling, Cross-platform · Caveat Microsoft distrust
- 16.Loved for Cleaner API, Performance · Caveat API churn
- 17.Loved for Small footprint, Electron replacement · Caveat Webview inconsistency
- 18.Loved for Built-in tooling, Security model · Caveat Uncertain future
- 19.Loved for Speed, Linting and formatting · Caveat Fragmented CLI
- 20.Loved for Code analysis tooling, Grammar authoring · Caveat Indentation languages
- 21.Loved for Current apps, stable base, Sandboxing · Caveat Sandbox breakage
- 22.Loved for Server-driven SSE, Beyond htmx · Caveat Unclear value
- 23.Loved for Declarative config, Homebrew management · Caveat Learning curve
- 24.Loved for Monorepo workspaces, Supply-chain safeguards · Caveat Not a security fix
- 25.Loved for TypeScript support, Stability · Caveat Ecosystem churn
- 26.Loved for Enjoyable to use, Cross-platform · Caveat Non-native look
- 27.Loved for Next.js alternative, Replaces Webpack · Caveat Feature support
- 28.Loved for Developer experience, General-purpose use · Caveat Not batteries-included
- 29.Loved for Enjoyable to use, Ergonomics · Caveat Others preferred
- 30.Loved for Cross-platform setup, Declarative dotfiles · Caveat Nix learning curve
- 31.Loved for Older Mac support, Stability · Caveat Smaller selection
- 32.Loved for Easy dependencies, Unified ecosystem · Caveat Supply chain security
- 33.Loved for Smooth performance, Cross-platform · Caveat Bare components
- 34.Loved for LLM output validation, Typed data models · Caveat Ty support
- 35.Loved for Lower memory use, Fewer OOM kills · Caveat Needs tuning
- 36.Loved for Developer experience, Tiny footprint · Caveat Learning curve
- 37.Loved for Simple and durable, Versatile uses · Caveat Ergonomics
- 38.Loved for Design quality, Works with agents · Caveat LLM look
- 39.Loved for Runtime validation, Shared schemas · Caveat Compromised release
- 40.Loved for Cross-platform desktop, Mature ecosystem · Caveat Language sprawl
- 41.Loved for Pairs with HTMX, Simple projects · Caveat Complex UIs
- 42.Loved for Developer experience, BEAM/OTP reliability · Caveat Productivity vs Rails
- 43.Loved for Elm architecture, Simplicity · Caveat No software renderer
- 44.Loved for Enjoyable to use, Lua fit · Caveat Stale release
- 45.Loved for Works with LLMs, Real solid models · Caveat AI accuracy
- 46.Loved for Cross-platform builds, Feature breadth · Caveat Feature churn
- 47.Loved for Reliable rendering, Developer experience · Caveat Bloat
- 48.Loved for Default backend stack, Lightweight layer · Caveat Async confusion
- 49.Loved for Mature compiler, Web backends · Caveat Shell command overhead
- 50.Loved for Platform abstraction, Smooth migration · Caveat Fullscreen modes
- 51.Loved for Code over engines, Ease of use · Caveat Build from scratch
- 52.Loved for Works well, Ecosystem
- 53.Loved for API design, Production use · Caveat Responses API
- 54.Loved for Custom terminal apps, Emacs terminal
- 55.Loved for WebAssembly support, Embedded hardware · Caveat Go compatibility gaps
- 56.Loved for Cross-platform binaries, Pairs with redbean · Caveat Expired certificates
- 57.Loved for Prototyping, Dense UI · Caveat Non-native look
- 58.Loved for Practical agents, SDK design · Caveat Uneven docs
- 59.Loved for Cross-platform .NET GUI, WPF alternative · Caveat Wayland drag-and-drop
- 60.Loved for Static linking, Glibc alternative · Caveat Slow malloc
- 61.Loved for Ecosystem, Next.js alternative · Caveat Foot guns
- 62.Loved for Python data ecosystem, Exploratory research · Caveat Unintuitive API
- 63.Loved for LLM-friendly, Web games · Caveat Browser-bound
- 64.Loved for Daily workhorse, Ecosystem default · Caveat Python lock-in
- 65.Loved for Ecosystem foundation, Numeric speed · Caveat Slow import
- 66.Loved for Cross-language schemas, Efficient exchange · Caveat Design flaws
- 67.Loved for React alternative, Async features · Caveat Data fetching
- 68.Loved for Electron alternative, Developer productivity · Caveat Platform confusion
- 69.Loved for Well engineered, Speed at scale · Caveat Endpoint security hangs
- 70.Loved for Performance, Musl malloc replacement
- 71.Loved for Simple installs, Vetted repositories · Caveat No AUR support
- 72.Loved for Speed, Engine integration
- 73.Loved for Go integration, Speed · Caveat Go module setup
- 74.Loved for Better Conda, Fast solver · Caveat Often unnecessary
- 75.Loved for Agent feedback loop, Claude Code pairing · Caveat Speed
- 76.Loved for No real alternative, Compute power · Caveat Nvidia lock-in
- 77.Loved for Quick simple tools, Cross-platform · Caveat Basic widgets
- 78.Loved for OTA updates, Single codebase · Caveat Performance
- 79.Loved for Production-ready, Grid layout · Caveat Windows-only
- 80.I used Expo recently and loved the development experience.
- 81.I have found out that it is very efficient to use phaser.js/three.js for fast, vibe coding
- 82.apt is/was the best thing since recycled electrons
- 83.tantivy's BM25 search is faster, more expressive, and more scalable than SQLite.
- 84.Make has long been my go-to script runner and build tool, simple and ubiquitous
- 85.When it comes to mobile app development I'll stick to Kotlin Multiplatform with Compose Multiplatform.
- 86.I switched to Hotwire/Stimulus and found it to be a significantly better implementation of the same core concepts.
- 87.I can highly recommend TypeScript/JavaScript with AI SDK
- 88.I switched from brew to https://asdf-vm.com/ for this very reason.
- 89.Roger is doing amazing work and I urge anyone wanting to fully utilize SQLite to try apsw.
- 90.We use the golang wrapper at work and love the simplicity and speed
- 91.It’s the best of both worlds. We use it to bridge svelte with Laravel at work and I couldn’t be happier about this stack.
- 92.TCC is fantastic! I use it a lot to do fast native-code generation for language projects
- 93.But it does them well, and it does all of them because only a coherent system can deliver the promise of allowing you to write production-ready TypeScript.
- 94.I was against ORMs until I used EF Core in .NET which I really loved.
- 95.tsgo which has dramatically lowered our type checking latency
- 96.We use NX in our monorepo, and it is great at determining which testing/linting tasks need to be run
- 97.Adding github link for those who want to use it (I do)
- 98.The official aspnet core web framework is (in my opinion) good enough that you don't need anything 3rd party.
- 99.Libraries like [BOSL2](https://github.com/BelfrySCAD/BOSL2) provide a good set of core ideas and preferences
- 100.What about using PyPy? You'll probably see a significant improvement in these benchmarks.
- 101.I can only recommend to check out a popular project, maybe Laravel, and read it’s documentation.
- 102.I tried to tune it to use MLX on Mac GPUs, and it's so much faster.
- 103.AppImage actually works and is simple, so I use that.
- 104.After using a lot of others, including jest and node's built in one, I love vitest.
- 105.lately I've been happy with Drizzle for TS. It's very performant and expressive.
- 106.when I threw cucumber into the mix things suddenly got a lot more stable
- 107.it's much simpler and it's stable: there's no constantly evolving ecosystem.
- 108.GCC and LLVM having won the compiler wars and being extremely high quality
- 109.I spent a couple of nights working out how to configure beets to my liking and have loved it ever since.
- 110.But 1/ it’s much simpler for doing simple things and 2/ we can drop down to AppKit when needed. All in all, it’s good that we have it.
- 111.I use Angular 2+, and I find it quite pleasant to use.
- 112.I'm totally sold on Guix, and have been using it on an old laptop for the last few months.
- 113.a more modern Next.js-powered stack that's faster, lighter weight, and easier for them to manage
- 114.tokio gives me most of the concurrency goodies I like
- 115.I’m used to using Hono and really enjoy working with it
- 116.you can connect to your local library with an app named "libby". I used this frequently on my Android phone to download books and magazines
- 117.Babashka is my go-to tool for starting all new projects now.
- 118.providing a VM like QuickJS for running simple code could be enough (thus also cheaper)
- 119.I’ve had far fewer issues with this app than the likes of Bluesky (react native) and Discord
- 120.I use Slint and tried a bunch of the other frameworks and nothing worked as well in embedded and also as mac/linux apps.
- 121.I would recommend something like SDL if you want a more complete platform abstraction, it even supports software rendering as a context mode.
- 122.I used Slug at a previous job. It is an excellent, artfully crafted library; really the pinnacle of software engineering in my opinion.
- 123.For learning SICP, I use Chicken 5 with 203 and 216 eggs plus the ~/.csirc and call it done.
- 124.the Textual framework is fantastic. I’ve been using it for years in a small project
- 125.I use Wails which is Tauri but for Go and I don't have the kind of issues you're mentioning.
- 126.There are companies like Antithesis that have done incredible work in this space.
- 127.Other languages have similar libraries, e.g., Rust has Diesel.
- 128.I've been using ULIDs [0] in prod for many years now, and I love them.
- 129.Some recent alternatives/successors/forks that are in the same vein as Pico
- 130.I replaced it with rust tls to remove the dynamic linked library.
- 131.This is cool and I love how enthusiastic you are about it
- 132.I've been using it for years and it often really is that easy.
- 133.I use Manim for maths, for me having computational libraries (python) is a requirement.
- 134.numpy/scipy/matplotlib/pandas/plotly/polars/pyarrow/jupyter, which is essential to my work
- 135.I had the best success with popular and versatile packages like matplotlib and ggplot2
- 136.Your LLM can replace your cargo build with bazel in a few sessions.
- 137.Theres already git-in-rust project that is making good progress
- 138.This day you don't need Anki for this, just use one of FSRS libraries for scheduling.
- 139.I use a package manager that checks the hash of the downloaded installer against what's recorded in the package listing for that version. WinGet has been built in to Windows
- 140.In my opinion, Unpoly has a better-organized approach to everything.
- 141.There's a module for it in scipy, so it should be rather straightforward to try your analysis
- 142.the latest version of yay (v13+) supports being able to skip recently added packages through its new Lua extension system
- 143.The main reasons for choosing it were its simplicity, adherence to web standards, and how easy it is for students to grasp.
- 144.I used a native CoreGraphics renderer for Mermaid (BeautifulMermaid) so the diagrams update without any flicker.
- 145.i have been using JUCE for decades and it's been very reliable and stable with a well maintained forum
- 146.Clang already had the full C99 designated init feature set in C++ mode implemented long before C++20 and it worked just fine.
- 147.It let's you target specific glibc versions. It's a pretty amazing C toolchain.
- 148.Python has won for me: fastapi, pytorch, langchain, streamlit, and so on and on.
- 149.If you are using Tailwind, I highly recommend Tailwind Plus.
- 150.GCC and LLVM having won the compiler wars and being extremely high quality
- 151.it's one of the best frameworks I've ever used for gamedev
- 152.I love jQuery syntax. It's still way tigheter than standards-based stuff
- 153.We use the ONNX runtime for small models in the browser
- 154.I love it so much, it has a great balance between: readability, fast write/compile/debug cycle and great performance.
- 155.I am 100% sure what SQL do I want it to produce and what SQL will a particular ORM invocation produce.
- 156.ROCm runs most things just fine without any ceremony or difficulty.