That’s what KDE and GNOME said about desktop environments 20 years ago. Difference is new generations of FPGAs still are proprietary chunks of silicon. While “open” tools are great, no one is making an economic decision based on philosophy.
-
-
Maybe in the US… many EU backed projects have to choose tools based on their openness if they want to get the money at all. So yes indeed they are making economic decisions based on philosophy of the tools they use.
1 reply 0 retweets 0 likes -
Replying to @esden @baldengineer and
Also speaking for myself here: I do vote all the time with my wallet. Buying based on philosophy. Not everything is just focused on the VC funders ideals of margins and profit maximization. I am aware that I am likely a minority, but still.
1 reply 0 retweets 1 like -
That’s a fundamental difference for me. I don’t vote based on philosophy. I vote on what gets my job done.
1 reply 0 retweets 1 like -
Why not both? :)
2 replies 0 retweets 0 likes -
Explaining to a client I missed a deadline because I was waiting for a patch to be applied to a fork on GitHub rarely goes well.
1 reply 0 retweets 0 likes -
But your client is ok with you explaining that you missed a deadline because of a bug in a commercial software and you being too small of a fish for them to bother fixing it for you. :) You can always apply the patch in an open source software package yourself you know? :)
1 reply 0 retweets 0 likes -
Replying to @esden
Blah. That argument is worse than “fix it yourself!” Unless you’ve spent years studying the code, the power to get a fix is no different. Except commercial software you have the power of payment. Maybe small and limited, but better than community standing.
3 replies 0 retweets 3 likes -
Replying to @baldengineer @esden
Ah, the good old "FPGA tools are so complicated, you need years of PhD work to do anything" argument. It's nonsense! I know a lot of people working on this kind of software. On free and on commercial projects. I have never heard one of the programmers say something like that. 1/3
1 reply 0 retweets 1 like -
But sales people like to peddle this myth. SUN used similar "arguments" in the 80s regarding compilers. "It's all magic and you need to be a wizzard to do any kind of compiler development." That's not true of course. Today it's the same thing with FPGA tools. 2/3
1 reply 0 retweets 1 like
I have reported many bugs in Xilinx and Intel/Altera tools. Many of them bugs where the tool silently generates an incorrect circuit (which is a "critical bug" imo). Many of them super easy to fix. But the vendors take years to fix them, if they fix them at all. 3/3
-
-
Here are some of the bugs I've reported: http://www.clifford.at/yosys/vloghammer.html … And here are some more: http://svn.clifford.at/handicraft/2017/vivadobugs/xilinxbugs.ods … Since I switched companies I don't have access to the Xilinx support network anymore. So bugs I find now I can not even report: http://svn.clifford.at/handicraft/2017/vivadobugs/vivadobug06.txt …
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.