Most forthcoming software will necessarily have to be written in high-level language, making it independent of the actual processor used. The reason is due to increasing software costs and the desire to implement more complex programs. No one will be able to afford to develop important new applications in machine language, especially since it will be unnecessary. Because of the increased capabilities of future-generation microprocessors, coding efficiency won't really matter. Stretch it to the limit and you'll see what I mean - perhaps by the year 1999 all the software ever written will run in less than a minute.
:^)
How we laughed when we saw Intel making the same mistakes :)
It absolutely makes sense to integrate things, but this is also a step, not an end game. Step back and look at projects from a lifecycle vantage point, high up, and code is still only one piece. It's probably considered a human rights violation to expose non-devs to git in any way. :^) Manual threading is also crude, but better than nothing to be sure.
Key, for me, is the data (which includes the people involved). If you have that, you can view things and present it in different ways. Picture a project as a tree. You see the end result from the outside, but if you look at slices of the tree you can see how it got there. Years of vigorous growth and drought, where branches broke off. Now look at the forest, where the whole ecosystem comes into play, and timelapse that. What could we learn, and how can we use that information to plan for a better future?
input function. All works perfectly unless i compile my code and then launch executable. It yields *** Script Error: input has no value and i've no idea how to solve it. linux x86_64, latest red-06 and red-04nov20-277584b4c - both do not allow me to use input in compiled code...
routine which is not handled.
load.