Verilog is weakly typed and VHDL is strong. That is already a pretty big deal when dealing with vector signals, where Verilog happily assigns a 32-bit signal to a 16-bit signal.
VHDL also supports defining record types, such that a collection of signals can be assigned together.
VHDLs type system is pretty rock solid it’s based off Ada after all. Which if you have looked at in any detail its a great type system!
I dont like the begin end style syntax and some the verbosity that entails with VHDL. However, I would rather create designs in VHDL than verilog when given the choice.
I come from a VHDL background (the industry I work in is purely VHDL), but recently I've been enjoying Systemverilog
in my personal projects and it fixes a lot of these issues!
It's true that SystemVerilog fixed a lot of Verilog's deficiencies and took it more in the direction of VHDL. But a lot of free tools don't support SystemVerilog.
Hm, every vendor with free tools (Xilinx/Altera/Lattice/Microsemi etc), seem to be fine with it, along with the usual vendor-specific Modelsim. In fact, most "verilog" synthesis tools actually synthesize SystemVerilog. Out of curiosity what tool are you referring to?
There's few open source tools for any HDL full stop.
Indeed I'd say SystemVerilog is doing better on that front, as Verilator (https://www.veripool.org/verilator/) supports SystemVerilog and is probably the best open source tool for 'real' HDL work (note the number of industrial users).
I didn't mean open source, no, and it looks like the free version of yosys has limited support of systemverilog.
What I meant were the free toolchains provided by all of the FPGA vendors. They typically support SystemVerilog in synthesis and modelsim as far as I have seen.
VHDL also supports defining record types, such that a collection of signals can be assigned together.