Yes, and it is also a bug riddled mess that is prone to synthesis errors. I am hoping maybe the AMD acquisition will encourage them to open more things up to get more eyes on the synthesis flow and allow more recourse/debugging when issues are encountered.

What synthesis errors have you run into?

Random ones requiring keep attributes for no reason on larger designs to keep stuff from being inferred away erroneously. Certain issues with limitations on SV interfaces only supporting constructs used in the "IP integration" scripting as opposed to the full language spec. I am sorry if I came off as overly negative, but I really think the FOSS EDA tools are going to lap them unless they open up somewhat.

I agree that just about all of the EDA tools are a pretty terrible experience.

I’ve gotten tired of dealing with quirks using SV interfaces in RTL. I’m using structs as a substitute at the moment.

(I am also biased because the designs I work on are small enough that ECP and presumably upcoming Lattice FPGAs are plenty. I am excited by the Xilinx reverse engineering efforts, too. But there seems to be less official interest than we see with Lattice in supporting the OSS efforts.)

How does that prevent you from making use of the product described in the article ?

That comment was made in the context of a thread about open source FPGA development tools.

And I'm questioning whether lack of open source FPGA development tools means that the device is "locked down". You can do everything that the device is designed to be able to do.

That's true for any locked down device. An iPhone can do everything it is designed to do yet it could also do so much more if it weren't locked down.