Here is my take on Verilog-vs-VHDL
In the early 1990s many people thought that Verilog was a temporary language and was going away with VHDL standard adoption.
For example, Verilog was plagued by race conditions in the form:
always @ (posedge clock) a = b;
always @ (posedge clock) c = a;
You had to use non-blocking assignments or delays in simulation to counteract the fact that the order of always block evaluation is indeterminate. This led to a pre-synthesis-post-synthesis simulation mismatch. At the same time, many people complained that VHDL has different incompatible arithmetic packages (numeric_std and std_logic_arith) and writing something like
wire [3:0] a, b;
wire [4:0] c = a + b;
becomes something like
signal a, b : std_logic_vector (3 downto 0);
signal c : std_logic_vector (4 downto 0);
c <= std_logic_vector (resize (unsigned (a), 5) + resize (unsigned (b), 5))
Finally John Cooley, the first blogger of EDA industry (he started his blog http://deepchip.com even before the word "blogger" appeared in the press) decided to make a hackathon in 1997 (at that moment the word "hackathon" was also unknown) to find out who is more productive - Verilog or VHDL engineers.
John Cooley published the results in an article
"The Unexpected Results From A Hardware Design Contest: Verilog Won & VHDL Lost? -- You Be The Judge!"
https://www.angelfire.com/in/rajesh52/contest.html
He found that the Verilog engineers were more productive in his challenge.
After that more and more companies started to switch to Verilog, especially when Verilog-2001 and SystemVerilog integrated all the features of VHDL (packages, generate, records/structs etc).