Podcasts about transclusion

Xanadu was the first hypertext project founded in 1960 by Ted Nelson. It aims to facilitate a type of media called hypermedia, which is non-sequential writing in which the reader can choose their own path through an electronic document.Links/Resources:http://www.rheingold.com/texts/tft/14.htmlhttps://en.wikipedia.org/wiki/Project_Xanaduhttps://mimix.io/en/blog/xanaduhttps://sentido-labs.com/en/library/201904240732/Xanadu%20Hypertext%20Documents.htmlhttps://www.notion.so/blog/ted-nelsonhttps://www.wired.com/1995/06/xanadu/https://xanadu.com.au/ararathttps://www.youtube.com/watch?v=-_-5cGEU9S0https://www.youtube.com/watch?v=hMKy52Intachttps://www.youtube.com/watch?v=1gPM3GqjMR4https://www.youtube.com/watch?v=hGKbRcvIZT8https://www.youtube.com/watch?v=qyzgoeeloJAhttps://www.youtube.com/watch?v=_xYwgJW7T8ohttps://jasoncrawford.org/the-lessons-of-xanaduhttps://blockprotocol.org/https://github.com/subconsciousnetwork/noosphere/blob/main/design/explainer.mdhttps://maggieappleton.com/xanadu-patternshttps://aaronzlewis.com/blog/2019/05/01/spreading-threading/https://www.zombo.com/https://stratechery.com/concept/aggregation-theory/https://maggieappleton.com/tools-for-thoughthttps://cdixon.org/2015/01/31/come-for-the-tool-stay-for-the-networkChapters:[00:00:00] Intros[00:03:22] What is Xanadu?[00:15:49] Transclusion and Bidirectionality[00:26:32] Versioning[00:29:47] Vision divorced from implementation[00:35:13] Baked in Payments[00:46:15] Hypermedia as Envisioned[00:56:20] Tiktok as Hypermedia[01:01:52] Alternative business model for the web[01:16:19] Failure to Launch[01:26:15] Linearization as a forge[01:31:51] Success of Xanadu's Vision[01:37:04] Passing the torch===== About “The Technium” =====The Technium is a weekly podcast discussing the edge of technology and what we can build with it. Each week, Sri and Wil introduce a big idea in the future of computing and extrapolate the effect it will have on the world.Follow us for new videos every week on web3, cryptocurrency, programming languages, machine learning, artificial intelligence, and more!===== Socials =====WEBSITE: https://technium.transistor.fm/SPOTIFY: https://open.spotify.com/show/1ljTFMgTeRQJ69KRWAkBy7APPLE PODCASTS: https://podcasts.apple.com/us/podcast/the-technium/id1608747545

Link to original articleWelcome to The Nonlinear Library, where we use Text-to-Speech software to convert the best writing from the Rationalist and EA communities into audio. This is: The lessons of Xanadu, published by jasoncrawford on August 7, 2022 on LessWrong. One of my all-time favorite articles is “The Curse of Xanadu,” by Gary Wolf, which ran in WIRED Magazine in 1995. On the surface, it's a piece of tech history, a story of a dramatic failure. But look closer, and you can find deep philosophical insight. Xanadu was a grand vision of a hypertext system, conceived long before the Web, that at the time of this article had been “under development” for three decades without launching. The visionary behind it was Ted Nelson, one of the originators of the concept of hypertext. Here's how the article describes him and the project: Nelson's life is so full of unfinished projects that it might fairly be said to be built from them, much as lace is built from holes or Philip Johnson's glass house from windows. He has written an unfinished autobiography and produced an unfinished film. His houseboat in the San Francisco Bay is full of incomplete notes and unsigned letters. He founded a video-editing business, but has not yet seen it through to profitability. He has been at work on an overarching philosophy of everything called General Schematics, but the text remains in thousands of pieces, scattered on sheets of paper, file cards, and sticky notes. All the children of Nelson's imagination do not have equal stature. Each is derived from the one, great, unfinished project for which he has finally achieved the fame he has pursued since his boyhood. During one of our many conversations, Nelson explained that he never succeeded as a filmmaker or businessman because “the first step to anything I ever wanted to do was Xanadu.” Xanadu, a global hypertext publishing system, is the longest-running vaporware story in the history of the computer industry. It has been in development for more than 30 years. This long gestation period may not put it in the same category as the Great Wall of China, which was under construction for most of the 16th century and still failed to foil invaders, but, given the relative youth of commercial computing, Xanadu has set a record of futility that will be difficult for other companies to surpass. The project had many of the earmarks of other failed or long-overdue efforts. As a product, it was over-designed: Xanadu was meant to be a universal library, a worldwide hypertext publishing tool, a system to resolve copyright disputes, and a meritocratic forum for discussion and debate. By putting all information within reach of all people, Xanadu was meant to eliminate scientific ignorance and cure political misunderstandings. And, on the very hackerish assumption that global catastrophes are caused by ignorance, stupidity, and communication failures, Xanadu was supposed to save the world. In contrast to the later Web, links in Xanadu did not point to entire documents, but to any arbitrary range of characters within any document. Links were to be bi-directional, so they could not be broken. And there was an advanced feature in which “parts of documents could be quoted in other documents without copying”: The idea of quoting without copying was called transclusion, and it was the heart of Xanadu's most innovative commercial feature—a royalty and copyright scheme. Whenever an author wished to quote, he or she would use transclusion to “virtually include” the passage in his or her own document.. The key to the Xanadu copyright and royalty scheme was that literal copying was forbidden in the Xanadu system. When a user wanted to quote a portion of document, that portion was transcluded. With fee for every reading. Transclusion was extremely challenging to the programmers, for it meant that there could be no redundancy in the grand Xanadu library. Every text could exist only as an original. Every user in the world would have to have instant ...

Welcome to The Nonlinear Library, where we use Text-to-Speech software to convert the best writing from the Rationalist and EA communities into audio. This is: The lessons of Xanadu, published by jasoncrawford on August 7, 2022 on LessWrong. One of my all-time favorite articles is “The Curse of Xanadu,” by Gary Wolf, which ran in WIRED Magazine in 1995. On the surface, it's a piece of tech history, a story of a dramatic failure. But look closer, and you can find deep philosophical insight. Xanadu was a grand vision of a hypertext system, conceived long before the Web, that at the time of this article had been “under development” for three decades without launching. The visionary behind it was Ted Nelson, one of the originators of the concept of hypertext. Here's how the article describes him and the project: Nelson's life is so full of unfinished projects that it might fairly be said to be built from them, much as lace is built from holes or Philip Johnson's glass house from windows. He has written an unfinished autobiography and produced an unfinished film. His houseboat in the San Francisco Bay is full of incomplete notes and unsigned letters. He founded a video-editing business, but has not yet seen it through to profitability. He has been at work on an overarching philosophy of everything called General Schematics, but the text remains in thousands of pieces, scattered on sheets of paper, file cards, and sticky notes. All the children of Nelson's imagination do not have equal stature. Each is derived from the one, great, unfinished project for which he has finally achieved the fame he has pursued since his boyhood. During one of our many conversations, Nelson explained that he never succeeded as a filmmaker or businessman because “the first step to anything I ever wanted to do was Xanadu.” Xanadu, a global hypertext publishing system, is the longest-running vaporware story in the history of the computer industry. It has been in development for more than 30 years. This long gestation period may not put it in the same category as the Great Wall of China, which was under construction for most of the 16th century and still failed to foil invaders, but, given the relative youth of commercial computing, Xanadu has set a record of futility that will be difficult for other companies to surpass. The project had many of the earmarks of other failed or long-overdue efforts. As a product, it was over-designed: Xanadu was meant to be a universal library, a worldwide hypertext publishing tool, a system to resolve copyright disputes, and a meritocratic forum for discussion and debate. By putting all information within reach of all people, Xanadu was meant to eliminate scientific ignorance and cure political misunderstandings. And, on the very hackerish assumption that global catastrophes are caused by ignorance, stupidity, and communication failures, Xanadu was supposed to save the world. In contrast to the later Web, links in Xanadu did not point to entire documents, but to any arbitrary range of characters within any document. Links were to be bi-directional, so they could not be broken. And there was an advanced feature in which “parts of documents could be quoted in other documents without copying”: The idea of quoting without copying was called transclusion, and it was the heart of Xanadu's most innovative commercial feature—a royalty and copyright scheme. Whenever an author wished to quote, he or she would use transclusion to “virtually include” the passage in his or her own document.. The key to the Xanadu copyright and royalty scheme was that literal copying was forbidden in the Xanadu system. When a user wanted to quote a portion of document, that portion was transcluded. With fee for every reading. Transclusion was extremely challenging to the programmers, for it meant that there could be no redundancy in the grand Xanadu library. Every text could exist only as an original. Every user in the world would have to have instant ...

Robby speaks with Ana Nelson, a software developer, writer, improv performer, and creator of Dexy — an open-source tool for writing any kind of technical document that incorporates code.Helpful LinksAna's websiteDexyFollow Ana on TwitterAna on GithubConnect with Ana on LinkedInWhat is Transclusion?The Modern Scholar by Professor Michael D. C. Drout[Book] On the Origin of Stories: Evolution, Cognition, and Fiction[Book] The Anatomy of Story: 22 Steps to Becoming a Master StorytellerSubscribe to Maintainable on:Apple PodcastsOvercastOr search "Maintainable" wherever you stream your podcasts.

This week Federico and Myke discuss the Google Daydream VR headset, how Instagram is becoming even more like Snapchat, Apple's Holiday ad, the advancement of the iPad Pro, and iA Writer.

This week Federico and Myke discuss the Google Daydream VR headset, how Instagram is becoming even more like Snapchat, Apple's Holiday ad, the advancement of the iPad Pro, and iA Writer.

01:33 - Tero Parviainen Introduction Twitter GitHub Blog Build Your Own AngularJS with Tero Parviainen 02:28 - Getting Started Digging the Angular Source Code Angular Documentation 05:05 - The Angular Compiler 06:13 - Advantages of Understanding the Compiler 07:42 - Directives 10:21 - Combining Controllers and Directives 12:43 - Routing 13:42 - What do we need to know about the Directive API? 15:12 - Transclusion 17:46 - Getting Started with the Compiler Tero Parviainen: Inside The AngularJS Directive Compiler 19:08 - How much do you need to know? 20:55 - Why use the compile phase? 22:02 - Angular 2 25:02 - The Clojure and JavaScript Worlds Picks Build Your Own AngularJS with Tero Parviainen (Lukas) The U.S. National Women’s Soccer Team (Joe) Better Off Ted (Joe) Inside Out (Ward) Aftershokz AS500 Bluez 2 Open Ear Wireless Stereo Headphones (Chuck) Paul Graham: Programming Bottom-Up (Tero) Flash Boys: A Wall Street Revolt by Michael Lewis (Tero)

01:33 - Tero Parviainen Introduction Twitter GitHub Blog Build Your Own AngularJS with Tero Parviainen 02:28 - Getting Started Digging the Angular Source Code Angular Documentation 05:05 - The Angular Compiler 06:13 - Advantages of Understanding the Compiler 07:42 - Directives 10:21 - Combining Controllers and Directives 12:43 - Routing 13:42 - What do we need to know about the Directive API? 15:12 - Transclusion 17:46 - Getting Started with the Compiler Tero Parviainen: Inside The AngularJS Directive Compiler 19:08 - How much do you need to know? 20:55 - Why use the compile phase? 22:02 - Angular 2 25:02 - The Clojure and JavaScript Worlds Picks Build Your Own AngularJS with Tero Parviainen (Lukas) The U.S. National Women’s Soccer Team (Joe) Better Off Ted (Joe) Inside Out (Ward) Aftershokz AS500 Bluez 2 Open Ear Wireless Stereo Headphones (Chuck) Paul Graham: Programming Bottom-Up (Tero) Flash Boys: A Wall Street Revolt by Michael Lewis (Tero)

01:33 - Tero Parviainen Introduction Twitter GitHub Blog Build Your Own AngularJS with Tero Parviainen 02:28 - Getting Started Digging the Angular Source Code Angular Documentation 05:05 - The Angular Compiler 06:13 - Advantages of Understanding the Compiler 07:42 - Directives 10:21 - Combining Controllers and Directives 12:43 - Routing 13:42 - What do we need to know about the Directive API? 15:12 - Transclusion 17:46 - Getting Started with the Compiler Tero Parviainen: Inside The AngularJS Directive Compiler 19:08 - How much do you need to know? 20:55 - Why use the compile phase? 22:02 - Angular 2 25:02 - The Clojure and JavaScript Worlds Picks Build Your Own AngularJS with Tero Parviainen (Lukas) The U.S. National Women’s Soccer Team (Joe) Better Off Ted (Joe) Inside Out (Ward) Aftershokz AS500 Bluez 2 Open Ear Wireless Stereo Headphones (Chuck) Paul Graham: Programming Bottom-Up (Tero) Flash Boys: A Wall Street Revolt by Michael Lewis (Tero)

People have been having conversations on the web since the moment the web was born. Comments, forums, linking, and more have provide ways for people to hold a back-and-forth discussion. But is that enough? There's a movement to create an annotation system for the web, one that might end up as a new web standard & feature in every browser. Learn what annotations on the web would mean with guest Doug Schepers.