2 ms·
I implied that. Most programmers today use Google. A paywall prevents them from getting these answers. So, most are blocked out. Far as your example, I agree t
by nickpsecurity 11y ago
I implied that. Most programmers today use Google. A paywall prevents them from getting these answers. So, most are blocked out.
Far as your example, I agree that algorithm support can't help without good software going along with it. That's probably true for many use cases with examples you cited being areas where proprietary tools and ecosystem dominate. Leads to some potential counters:
1. It might help in the many things that OSS is doing. That's a huge list that includes desktops, phones, servers, and a few major apps.
2. It might help in commercial sector if their developers see the cutting edge approaches. It might be obvious where rendering advances are but most stuff is scattered: finding it took lots of searching with my keyword, kung-fu. Might be affecting discovery in proprietary side, too. I know many of them keep inventing solutions weaker than even well-cited academic stuff. Aside from patents, gotta wonder why they didn't go with better approach if it seemed like a good fit. Likely explanation: didn't know it existed.
For instance, it's commonly believed that signal processing can only use a commercial DSP or graphics card with nothing delivered aside from that. People wanting an open alternative don't even know where to start that's worth anything. I heard and believed that too till I landed on this bad boy:
https://www.wikiwand.com/en/Asynchronous_array_of_simple_processors#/AsAP_2_chip:_167_processors https://www.wikiwand.com/en/Asynchronous_array_of_simple_pro...
The architecture is described in enough detail to be clonable. It might even be licensable with open-source allowed. It should handle plenty of workloads and supports custom accelerators for common things. After the mask costs, it would have great price vs performance vs energy usage. Yet, with 8 years of research, I just now came across this despite the first deliverable being in 2005. Might be a dead end and might turn into something if pursued. Yet, I'm sure it had potential to benefit commercial and OSS projects whose design approach accomplished far less had they known about this.
So, more full and legacy systems certainly have lots of momentum. You can't just have a piece of a system. I think even they might be affected by the problem I describe, though, given they're as sub-optimal vs cutting edge as OSS often are. So, easier movement of these ideas might benefit both.