Read the entire article, despite not having heard about Vivado previously. I wouldn’t be surprised if a certain company ending in soft slop is somehow involved.
The thing that makes sense to me (purely speculative, no real info to back this) is that Microslop isn’t happy about losing money and the user base, so they are pushing their hardware partners to force users back to the platform.
Redis did exactly this back in March 2024, dropping its long-standing BSD license for the more restrictive dual licensing model, and the blowback was severe enough that the community forked it into Valkey almost immediately.
Sounds like this is probably the best approach and outcome for the Vivado community and software. The end of the article recommends either joining in the discussion on AMD’s forums (which only seems to be getting stonewalled) or joining the growing number of people on hacker news.
Read the entire article, despite not having heard about Vivado previously. I wouldn’t be surprised if a certain company ending in
softslop is somehow involved.The thing that makes sense to me (purely speculative, no real info to back this) is that Microslop isn’t happy about losing money and the user base, so they are pushing their hardware partners to force users back to the platform.
Sounds like this is probably the best approach and outcome for the Vivado community and software. The end of the article recommends either joining in the discussion on AMD’s forums (which only seems to be getting stonewalled) or joining the growing number of people on hacker news.
That’s the second-best approach. The best approach is for it to be copyleft instead of permissively-licensed to begin with.
I don’t disagree, I meant given the current situation. Obviously copyleft would be preferred and should be encouraged.