News for hackers. Stuff that matters.
Re:Why Use an FPGA Instead of a CPU or GPU? by LeifCarrotson on Tuesday August 14, 2018 @10:53AM (#17758455)
That is incorrect, or at least inaccurate, on both counts.

FPGAs are often used to test/design not a "circuit" but an ASIC (application-specific-integrated-circuit) that you will then go on to actually build. Or, if your application doesn't have volume to suppprt the ASIC engineering costs but can support the FPGA unit cost, you just leave it as an FPGA. There are millions of devices (industrial machines, research, testing, etc) where this makes sense.

And not all FPGAs loose state when powered down. For those that do, there's typically an easy way to hook up a little Flash chip and bootloader to reload the state automatically on reset. For those that don't have that option (EG, currently working with an ABB robot, Mecco laser, and Rockwell PLC which all contain FPGAs, only the Mecco can boot itself), you store state in battery-backed SRAM and just leave the RAM on at all times.

Re:Why Use an FPGA Instead of a CPU or GPU? by joemi on Tuesday August 14, 2018 @04:06PM (#17761417)
> FPGAs are often used to test/design not a "circuit" but an ASIC (application-specific-integrated-circuit)

To be pedantic, an ASIC (and any IC really) is a circuit, as denoted by the "C" standing for "circuit".

Re:Why Use an FPGA Instead of a CPU or GPU? by corerius on Tuesday August 14, 2018 @11:09AM (#17758613)
Absolutely. In the worlds I work in, FPGA has been standard practice for years and years. As of late, it's becoming more common to place the CPU there for cost reduction.

In addition, you get the opportunity to both update the part and/or to change it's behavior via (for instance) a user setting.