Products · Broad category

FPGA development tooling

Raised as a usability problem by 13 people on Hacker News over 11 years (2015–2025), in 11 threads.

This is a broad category rather than one product, so its issues aren't ranked on the home page.

People raised many different problems with FPGA development tooling, but no single problem has yet been raised by 3 people in 3 different months and threads.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 13 complaints

Vendor GUI is atrocious, so the commenter avoids it and scripts everything in TCL2025-12-23
Learning FPGAs is annoying due to huge toolchain installs, long waits, and IDE bugs2025-12-23
Toolchains and IDEs are hard to use and documentation is hard to get2025-12-23
Vendor development tools are bloated, version-specific, and buggy, forcing engineers into clunky workflows2025-09-29
Vendor IP is a blackbox and examples for peripherals like DDR3 are missing2022-09-29
FPGA compilers are buggy and slow, making simple development very difficult2021-05-16
Tools are GUI-centric with little guidance for batch processing, making server use laggy2020-10-12
FPGA development software is outdated and hard to work with2020-10-11
Moving a component in the schematic detaches its wires2020-07-24
Vendor FPGA toolchains are slow, huge, and annoying to use2020-05-23
FPGA development tools are so bad that smaller companies avoid them2017-10-03
FPGA tooling is annoying to work with, though workable2017-05-17
FPGA development tools are so poor and closed that average programmers can't use them2015-10-13