News for hackers. Stuff that matters.
Re:Why hardware development is hard, part 1: Verilog is weir... by pjc50 on Thursday November 03, 2016 @11:50AM (#12865007)
I don't think they do have much adoption. SystemVerilog is still Verilog, and most of the new functions are aimed at simulation and testbench use. SystemC is rather painful as you have to write an artificially constrained subset and style of C.

> "Vendors pushing high-level synthesis have a decades long track record of overpromising and under-delivering."

Abstraction is important, but in hardware detail matters. In software you can afford to have a less efficient language if it results in faster development. This is absolutely not true of hardware.

High-level synthesis has usually held out misleading promises of portability; that you might be able to get some complex application working written by (cheaper, easier to hire) software developers, then just drop it straight onto a chip. That's simply not true because the constraints are different.

Chisel looks extremely promising, as it addresses a lot of what I'd say were Verilog pain points:

  Algebraic construction and wiring
  Abstract data types and interfaces
  Bulk connections
  Hierarchical + object oriented + functional construction
Re:Why hardware development is hard, part 1: Verilog is weir... by tonmoy on Thursday November 03, 2016 @12:05PM (#12865160)
SystemVerilog does seem to be used more and more. It is just verilog from the designer's perspective, but you have less chance to make mistakes, easier to write and the synthesis tool has more control over how to optimize the design.