4 ms·
Layout is NP-hard. Actually, it is NP-impossible. How does an algorithm know that in this case I want to emphasize how my code interacts with the IP stack (top
by RogerL 13y ago
Layout is NP-hard. Actually, it is NP-impossible. How does an algorithm know that in this case I want to emphasize how my code interacts with the IP stack (top of page higher layers), in this next page I want to emphasize change over time (later operations to the right and down), and so on?
I assert without proof that any programming model that requires me to do layout is one that does not scale and will fail. Any model that does not allow me to suck in and work with 1MM lines of enterprise code will fail. I don't direct this at NoFLo, which I haven't used, it's a more general comment directed to the multiple attempts over the decades for a visual interface. It works great for domain specific, small problems, and falls flat for larger problems and larger code bases. Anyone trying to make a new tool should be aware of the history and difficulties.
- Detrus 13y agoI'd guess that for your example you'd have labels on the flow components that approximate the order of events. So in the visualizer it can display them in almost linear order. When you want to view low level vs high level code, you switch layouts. May have to manually label your components low level vs high level. So you won't see everything at once but noticeably more useful. Hard to tell how far ahead these guys thought this through. Maybe with community interest and a cool looking product they'd attract enough people to work out these details. But judging by comments and relative lack of interest, won't be holding my breath.