Re: [myhdl-list] Advocacy page

[Jan D. <ja...@ja...>]

Andrew Stone wrote:
> How about "because you can take your dev env (MyHDL/gtkwave/emacs for
> me) with you"?  I'm a noob at hardware design so maybe you all do not
> find this so advantageous but for me its a pain to use the WebPack ISE
> GUI for Xilinx chips, Flex for Cypress, and if I ever get an Altera
> device I'm going to have to learn Quartus I think?  With MyHDL I can
> do all the simulation outside of the vendor GUI and so all I have to
> learn to do in each vendor tool is how to click the "compile" button,
> assign the pins, and program the device, instead of trying to actually
> use GUIs that seem to be designed by a bunch of hardware engineers
> ;-).

I don't think we can argue that MyHDL has a clear distincitive advantage
for non-GUI based design. You can set it up for other HDL languages
and environments also. (When I was doing Verilog and VHDL, I have
basically always done it like that.)

Jan

-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
     Using Python as a hardware description language:
     http://jandecaluwe.com/Tools/MyHDL/Overview.html