4 ms·

Congrats Intel, failure to play nice with community granted you a more up to date community fork. Now let's play the internal discussion at Intel: Developer:

Congrats Intel, failure to play nice with community granted you a more up to date community fork. Now let's play the internal discussion at Intel: Developer: see !! I told you so, we had to integrate the patch. Community leadership is more important than these corporate plays. Manager: err... Uhhh.... Now what do we do? How to regain community drive? Developer: i don't know now.... Invest tons of time/money into hyperscan, have new chips that tap hyperscan natively, or re merge the fork? ...

FridgeSeal 5y ago
“Wait, so you’re telling me we could sell a chip that only we could use to tap into for specialised performance?” Is how I imagine that conversation going, but maybe I’m just cynical.
- philprx 5y ago
  Cost of new die > market size, probably NPU was exactly that... And given scarcity, it's probable that foundries prioritize higher paying processors.
  - fmajid 5y ago
    Just look at what happened to AVX512.
mmaunder 5y ago
> Why the fork? Originally, the ARM porting was supposed to be merged into Intel's own Hyperscan, and 2 Pull Requests had been made to the project for this reason (1, 2). Unfortunately, the PRs were rejected for now and the forseeable future, thus we have created Vectorscan for our own multi-architectural and opensource collaborative needs. Karma's a bitch.