Last time I had to find in-depth documentation on a fairly common and new SONY image sensor, there was nothing available officially, found it in some chinese file sharing site though. Seems like they are shooting themselves in the foot by not opening it.
I don’t understand why chipmakers seem to always restrict access to documentation on chips. Their competitors will get it anyway. This only creates more problems for small developers.
I think there could be way better solutions for those problems without using blockchain. Use of blockcains where it’s not needed will only create more tecnical debt.
But is it really "realtime"? I thought something should have consistent millisecond or even microsecond latencies to be called realtime, but it's probably not possible for JavaScript application.
1. I/O isn't that bad, 40-100 GPIOs out, pretty much on par with most Artix-7 boards out there, SFP and PCIe is a plus cause Artix chips have no/slow transceivers and simply can't use them, and well everything aside from tutorials aren't beginner thing on FPGAs
2. License is pain though, you can get a proper demo license for Kintex probably
3. Compile times for barebones projects are few times more for a larger FPGAs, but as you add IPs and stuff they take a few minutes on a fastest computer anyway
FPGA tools allow a lot of customization if you need it, what difference will it make if they are fully opensource? FPGA chip design isn't opensource anyway