101–110 of 931 posts
Previously you've mentioned the "Oxbridge approach" to reading, whereby--if my recollection is correct--you take four topics and delve into them as much as possible. Could you elaborate on this approach (I've searched the internet, couldn't find anything)? And do you think this structured approach has more benefits than, say, a non-structured approach of reading whatever of interest?
Thanks for your time and generosity, Alan!
And what could be done to re-spark interest in moving forward?
My gut feeling says that it would require a complete overhaul in almost every layer in the stack we use today and that there's reluctance to do that. Would you agree to some degree with that?
What do you find most frustrating about software development at current times.
Regards, Jyoti
Many mainstream programming tools feel to be moving backwards. For example, Saber-C of the 1980s allowed hot-editing without restarting processes and graphical data structures. Similarly, the ability to experiment with collections of code before assembling them into a function was advance. Do you hold much hope for our development environments helping us think?
Development environments should help programmers think (but what if most programmers don't want to think?)
Hi Alan, 1. what do you think about the hardware we are using as foundation of computing today? I remember you mentioning about how cool was the architecture of the Burroughs B5000 [1] being prepared to run on the metal the higher level programming languages. What do hardware vendors should do to make hardware that is more friendly to higher level programming? Would that help us to be less depending on VM's while sti…
If you start with "desirable process" you can eventually work your way back to the power plug in the wall. If you start with something already plugged in, you might miss a lot of truly desirable processes. Part of working your way back to reality can often require new hardware to be made or -- in the case of the days of microcode -- to shape the hardware. There are lots of things vendors could do. For example: Intel…
We need to find ways to free ourselves from the cage of "vendors getting programmers to make their CPUs useful rather than the exact opposite approach" <- meditate on this we all should
Any conventional paradigms that you'd like to see retired? FS, Unix, signalling/messaging, etc.?
Edit: just noticed HARC and YC-Research. I'll check it out.