Does anyone else think that FPGA is like one of the biggest dogs to work with in the electronics world?
Massively complicated, closed software (and jesus I thought C compilers were bad), hard to use, expensive, difficult to solder, windows can probably destroy your design, etc.
I think I would rather work with any other component then a FPGA if I could avoid it. I think they need all the help they can get to get rid of all the engineering questions associated with them. If they had advanced open source software I might try it. Having to do all the complications in a closed ecosystem?? NO THANKS
I can see that you really haven't had much real experience doing FPGA designs for products which actually ship to customers.
The products I work on literally are not possible without FPGAs. High-speed converters, multiple data paths, high-speed communications to a remote server, and a whole bunch of other stuff to make the product work. And the bulk of the logic is on PCBs the size of credit cards.
If what you work on is not that complex or doesn't have the speed and the channel-count and size requirements, then you don't need to do FPGAs. And that's fine -- billions of dollars in electronic products ship every year with nothing more complicated than a 50-cent microcontroller doing the work.
I think when business people decide to make something, and they hear 'we need to get a FPGA guy for this' they think 'lets make something else'.
I think that business people decide what market they want to be in, and whether their products are sufficiently interesting to that market, and then they hire engineers who can do the design work. It's not like there are only ten of us FPGA guys in the entire country.
I don't even WANT to learn it because what I am going to get stuck in some kind of closed ecosystem.
While it's true that there are lots of aspects of the chips that are proprietary, it's not hard at all to go between toolsets and devices. But you have to want to learn, and you have to have a reason to do so. There's nothing inherently wrong about doing Xilinx-only projects.
Even assembly is kind of crappy because you can learn like ATMEL or PIC but it can kinda transfer over. C is better.
Except when you have to deal with the details of how SiLab's timers work vs ST's vs Atmel's, and they're all different, and very little of the code you wrote for one can transfer over because the parts are all completely different. And even though there are attempts with, say, ARM Cortex parts, to have some commonality, each vendor has its own special sauce which makes porting annoying.
For all I know learning one of those FPGA systems is like learning freaking FORTRAN!!!
That's it, in bold -- you DON'T know, yet you're happy to come onto a professional forum visited by people who actually DO know and you just start talking without making any sense. Just because it's all too hard for YOU to do doesn't mean that a lot of engineers make a living working with these devices.
You have choices. You can continue to do whatever it is that you do, and if you're making a living at it, great. Or you can spend the time to learn the tools and the parts and if a project or employer needs an FPGA, you can step up and do the work.