3 ms·
That's a valid point, but you can do things to mitigate this, like splitting up your program into processes that have different dependencies. For instance, if y
by witten 15y ago
That's a valid point, but you can do things to mitigate this, like splitting up your program into processes that have different dependencies. For instance, if you have a UI process and a core logic process, you won't need to import your giant UI library twice.
- adambyrtek 15y agoIf you split the code horizontally instead of vertically you have to deal with IPC, which could be problematic (and slow). I would do that only if there was already a clearly defined interface between the modules, not just for the sake of concurrency. Moreover, taking into account growing number of cores in modern machines such strategy doesn't seem very future-proof.
- rayiner 15y agoOr you could just use a language whose implementation doesn't blow.
- FooBarWidget 15y agoAnd suffer from 5x slower development time. Yeah your deadline now has to be extended from 2012 to 2015 but at least the language is FAST and is technically excellent, right?
- Peaker 15y agoFalse dichotomy...