Pearls that we left behind
-
Every now and then I get the urge to publish a book on the pearls we left behind. Solutions to problems that we are fighting with today - but ten, twenty or fifty years ago, we did have solutions. At the time, they may have been rejected because computing resources where not available. Today, they are, yet we haven't picked up the old solutions. We may have settled on architectures where the old solutions do not fit in. So we can see what would be the solution, but we cannot make use of it. Some solutions may not have been viable in its day - that's why it was left behind - and maybe not even today. Yet it might represent interesting concepts or approaches, that could be mind stimulating today, even though not necessarily realizable as code. Often, I see that my own thoughts have spun further: This is a great basic concept, but it could have been expanded so-and-so. That certainly is no discredit to the concept - quite to the contrary, if your ideas to extend it could have made it even stronger. Some concepts "sort of" exist, mostly in papers and articles, but are not commonly practiced in coding. I've got a fair number of candidates of my own, but I'd like to hear which other concepts, techniques and models you think that today does not receives the merit that it deserves. What is your favorite forgotten concept, that we really should be aware of today? If I really sit down to write this book, I probably will not see offhand what makes it valuable anno 2020, so I might need your explanations and references. We could start it here, and move it elsewhere if it grows too large. Would you think it interesting to start this a "book" as a CP article, that we could develop stepwise together?
-
Every now and then I get the urge to publish a book on the pearls we left behind. Solutions to problems that we are fighting with today - but ten, twenty or fifty years ago, we did have solutions. At the time, they may have been rejected because computing resources where not available. Today, they are, yet we haven't picked up the old solutions. We may have settled on architectures where the old solutions do not fit in. So we can see what would be the solution, but we cannot make use of it. Some solutions may not have been viable in its day - that's why it was left behind - and maybe not even today. Yet it might represent interesting concepts or approaches, that could be mind stimulating today, even though not necessarily realizable as code. Often, I see that my own thoughts have spun further: This is a great basic concept, but it could have been expanded so-and-so. That certainly is no discredit to the concept - quite to the contrary, if your ideas to extend it could have made it even stronger. Some concepts "sort of" exist, mostly in papers and articles, but are not commonly practiced in coding. I've got a fair number of candidates of my own, but I'd like to hear which other concepts, techniques and models you think that today does not receives the merit that it deserves. What is your favorite forgotten concept, that we really should be aware of today? If I really sit down to write this book, I probably will not see offhand what makes it valuable anno 2020, so I might need your explanations and references. We could start it here, and move it elsewhere if it grows too large. Would you think it interesting to start this a "book" as a CP article, that we could develop stepwise together?
The concept that all data would include semantic meaning and the things you could do with it would be determined by plugins. This was the original vision of the GUI created by the folks at Xerox PARC, and is something I consider forgotten but that we should really be aware of today. Instead, we have monolithic OS's where the semantic nature of information is totally lost in bit streams and meaningless JSON packets. :sigh: And I've already written a variety of articles here on CP to explore the concepts of true semantically aware data. :rolleyes:
Latest Articles:
Abusing Extension Methods, Null Continuation, and Null Coalescence Operators -
Every now and then I get the urge to publish a book on the pearls we left behind. Solutions to problems that we are fighting with today - but ten, twenty or fifty years ago, we did have solutions. At the time, they may have been rejected because computing resources where not available. Today, they are, yet we haven't picked up the old solutions. We may have settled on architectures where the old solutions do not fit in. So we can see what would be the solution, but we cannot make use of it. Some solutions may not have been viable in its day - that's why it was left behind - and maybe not even today. Yet it might represent interesting concepts or approaches, that could be mind stimulating today, even though not necessarily realizable as code. Often, I see that my own thoughts have spun further: This is a great basic concept, but it could have been expanded so-and-so. That certainly is no discredit to the concept - quite to the contrary, if your ideas to extend it could have made it even stronger. Some concepts "sort of" exist, mostly in papers and articles, but are not commonly practiced in coding. I've got a fair number of candidates of my own, but I'd like to hear which other concepts, techniques and models you think that today does not receives the merit that it deserves. What is your favorite forgotten concept, that we really should be aware of today? If I really sit down to write this book, I probably will not see offhand what makes it valuable anno 2020, so I might need your explanations and references. We could start it here, and move it elsewhere if it grows too large. Would you think it interesting to start this a "book" as a CP article, that we could develop stepwise together?
Many of the concepts in my book and articles on this site are more or less in that category. Maybe they haven't been left behind so much as they aren't widely known. If you drew up a list of topics, I'd pitch in if I thought I could contribute something useful.
Robust Services Core | Software Techniques for Lemmings | Articles
-
Every now and then I get the urge to publish a book on the pearls we left behind. Solutions to problems that we are fighting with today - but ten, twenty or fifty years ago, we did have solutions. At the time, they may have been rejected because computing resources where not available. Today, they are, yet we haven't picked up the old solutions. We may have settled on architectures where the old solutions do not fit in. So we can see what would be the solution, but we cannot make use of it. Some solutions may not have been viable in its day - that's why it was left behind - and maybe not even today. Yet it might represent interesting concepts or approaches, that could be mind stimulating today, even though not necessarily realizable as code. Often, I see that my own thoughts have spun further: This is a great basic concept, but it could have been expanded so-and-so. That certainly is no discredit to the concept - quite to the contrary, if your ideas to extend it could have made it even stronger. Some concepts "sort of" exist, mostly in papers and articles, but are not commonly practiced in coding. I've got a fair number of candidates of my own, but I'd like to hear which other concepts, techniques and models you think that today does not receives the merit that it deserves. What is your favorite forgotten concept, that we really should be aware of today? If I really sit down to write this book, I probably will not see offhand what makes it valuable anno 2020, so I might need your explanations and references. We could start it here, and move it elsewhere if it grows too large. Would you think it interesting to start this a "book" as a CP article, that we could develop stepwise together?
Digital concrete? Sounds like something I'd add to my kilometre-high "to read" pile.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Many of the concepts in my book and articles on this site are more or less in that category. Maybe they haven't been left behind so much as they aren't widely known. If you drew up a list of topics, I'd pitch in if I thought I could contribute something useful.
Robust Services Core | Software Techniques for Lemmings | Articles
Greg Utas wrote:
Many of the concepts in my book and articles on this site are more or less in that category.
Grandiosity points awarded.
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
-
Every now and then I get the urge to publish a book on the pearls we left behind. Solutions to problems that we are fighting with today - but ten, twenty or fifty years ago, we did have solutions. At the time, they may have been rejected because computing resources where not available. Today, they are, yet we haven't picked up the old solutions. We may have settled on architectures where the old solutions do not fit in. So we can see what would be the solution, but we cannot make use of it. Some solutions may not have been viable in its day - that's why it was left behind - and maybe not even today. Yet it might represent interesting concepts or approaches, that could be mind stimulating today, even though not necessarily realizable as code. Often, I see that my own thoughts have spun further: This is a great basic concept, but it could have been expanded so-and-so. That certainly is no discredit to the concept - quite to the contrary, if your ideas to extend it could have made it even stronger. Some concepts "sort of" exist, mostly in papers and articles, but are not commonly practiced in coding. I've got a fair number of candidates of my own, but I'd like to hear which other concepts, techniques and models you think that today does not receives the merit that it deserves. What is your favorite forgotten concept, that we really should be aware of today? If I really sit down to write this book, I probably will not see offhand what makes it valuable anno 2020, so I might need your explanations and references. We could start it here, and move it elsewhere if it grows too large. Would you think it interesting to start this a "book" as a CP article, that we could develop stepwise together?
Member 7989122 wrote:
Would you think it interesting to start this a "book" as a CP article, that we could develop stepwise together?
Would I find interesting any further discussion of this rambling, content-free,
Member 7989122 wrote:
on the pearls we left behind.
fantasia ? No.
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
-
Member 7989122 wrote:
Would you think it interesting to start this a "book" as a CP article, that we could develop stepwise together?
Would I find interesting any further discussion of this rambling, content-free,
Member 7989122 wrote:
on the pearls we left behind.
fantasia ? No.
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
OK, so I understand that you think there is nothing to learn from the past. Anything that has ever been rejected, for whatever reason, under whatever assumptions and circumstances, should forever be forgotten and ignored, and noone should ever suggest that it might have some merit under the new and changed circumstances. A rejection of an idea should always be final and absolute. Fine. I'd like you think so - that is your right. So I am certainly NOT going to bother you with any stuff about ideas that you have been decleared, for yourself, as rejected and carrying no value. Obviously, I cannot prevent you from looking up, or by accident come across, any such idea that you consider rejected and without value, but I certainly feel no need to force it onto you. You go ahead hunting the freely roaming game, whether it be the web framework of the week, the next programming language to hit the Tiobe index as the fastest growing one, or whatever. Anything else is just soooo 2019, and not worth a dime!
-
Greg Utas wrote:
Many of the concepts in my book and articles on this site are more or less in that category.
Grandiosity points awarded.
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
-
OK, so I understand that you think there is nothing to learn from the past. Anything that has ever been rejected, for whatever reason, under whatever assumptions and circumstances, should forever be forgotten and ignored, and noone should ever suggest that it might have some merit under the new and changed circumstances. A rejection of an idea should always be final and absolute. Fine. I'd like you think so - that is your right. So I am certainly NOT going to bother you with any stuff about ideas that you have been decleared, for yourself, as rejected and carrying no value. Obviously, I cannot prevent you from looking up, or by accident come across, any such idea that you consider rejected and without value, but I certainly feel no need to force it onto you. You go ahead hunting the freely roaming game, whether it be the web framework of the week, the next programming language to hit the Tiobe index as the fastest growing one, or whatever. Anything else is just soooo 2019, and not worth a dime!
"Never wrestle with a pig. You both get dirty and the pig enjoys it." --apocryphally attributed to George Bernard Shaw
Robust Services Core | Software Techniques for Lemmings | Articles
-
OK, so I understand that you think there is nothing to learn from the past. Anything that has ever been rejected, for whatever reason, under whatever assumptions and circumstances, should forever be forgotten and ignored, and noone should ever suggest that it might have some merit under the new and changed circumstances. A rejection of an idea should always be final and absolute. Fine. I'd like you think so - that is your right. So I am certainly NOT going to bother you with any stuff about ideas that you have been decleared, for yourself, as rejected and carrying no value. Obviously, I cannot prevent you from looking up, or by accident come across, any such idea that you consider rejected and without value, but I certainly feel no need to force it onto you. You go ahead hunting the freely roaming game, whether it be the web framework of the week, the next programming language to hit the Tiobe index as the fastest growing one, or whatever. Anything else is just soooo 2019, and not worth a dime!
Member 7989122 wrote:
OK, so I understand that you think there is nothing to learn from the past. Anything that has ever been rejected, for whatever reason, under whatever assumptions and circumstances, should forever be forgotten and ignored, and noone should ever suggest that it might have some merit under the new and changed circumstances. A rejection of an idea should always be final and absolute.
wonderfully entertaining hyperbole, but, you left out the part where I strangle kittens :)
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
