#workgraph
Renderlet & others getting to enjoy moving compute more fully to the GPU with work-graphs sounds so excellent. Deliver the work & let that GPU go. #webgpu #renderlet #workgraph
youtu.be/PpYbizur5xA?...
WebGPU and wasi-gfx with renderlet - WasmAssembly
YouTube video by Chrome for Developers
youtu.be
February 24, 2025 at 6:49 PM
Still shocked about the performance of vkd3d workgraph implementation vs NVidia and AMD drivers

I hope this is because we need more adoption so drivers can iterate more on this. For now, workgraphs have a quite low occupancy :(

github.com/HansKristian...
github.com
October 22, 2024 at 3:33 PM
noteにハブ、及び簡単な記事内容を投稿しました
ADRENALINE25.11.1 VS 25.10.2 だいぶ安定寄りにロールバック?-裏話|ヘルハウンド【ホビー系Vtuber】 @hellhoundoujin note.com/agile_coot19...
ADRENALINE25.11.1 VS 25.10.2 だいぶ安定寄りにロールバック?-裏話|ヘルハウンド【ホビー系Vtuber】
新型のADRENALINEである25.11.1が出てから数日が経過し、ベンチマークもまとまってきたので内容として発表していきます。 先出し結論とブログへの案内 まず今回のバージョンの先出しの結論としてはこんな感じです。 マジでこれ。 なんかWorkGraphの痕跡が一度消えている、そんな感じの結果になっています。 ホントに前回CPU使用率が一気に下がったゲームがまた上がってることが多...
note.com
November 29, 2025 at 5:10 AM
動画公開しました! ADRENALINE25.11.1のベンチ結果をピックアップしてお届けです
【ベンチマーク】ADRENALINE25.11.1 VS 25.10.2 だいぶ安定寄りにロールバックしたっぽい結果、WorkGraphの痕跡が... youtu.be/_Lb8LTGoGf4?... @YouTubeより
【ベンチマーク】ADRENALINE25.11.1 VS 25.10.2 だいぶ安定寄りにロールバックしたっぽい結果、WorkGraphの痕跡が割と消える
YouTube video by ヘルハウンドVLOG
youtu.be
November 29, 2025 at 4:48 AM
動画投稿しました! 前回のADRENALINEバージョンを振り返る動画です
【ベンチマーク】ADRENALINE25.10.2を今更語る備忘録 WorkGraphという名の地殻変動級変化による大幅な構成変化の必要性 youtu.be/5YEG_IRyeH8?... @YouTubeより
【ベンチマーク】ADRENALINE25.10.2を今更語る備忘録 WorkGraphという名の地殻変動級変化による大幅な構成変化の必要性
YouTube video by ヘルハウンドVLOG
youtu.be
November 20, 2025 at 5:58 AM
ちくしょー! ADRENALINE25.10.2の動画作るより前に新型のドライバ来るとか聞いてねぇよ!
今ブログに大急ぎで結果をまとめてるが、今回天変地異すぎて内容が大変なんだよ! WorkGraphとかまでぶちこみやがってぇ!!
November 14, 2025 at 2:49 AM
First steps of a workgraph path tracer, already beating a naive pipeline-based path tracer in terms of performance. Still long ways to go before getting in the ballpark of a wavefront PT.
A major painpoint is definitely having to generate nodes due to recursion being a bit limiting.
October 22, 2024 at 3:25 PM
Evolve 1.0.5 is out 🎯
🦖 New:
• Retry failed high score submissions
• WorkGraph scores now live in Hall of Fame
🐞 Fixes:
• No more 30MB submission failures
• Timestamp overflow bug squashed

👉 Press/influencer? Grab free Pro access here: www.evolvebenchmark.com/press-influe...
Press & Influencers | Evolve
Get free access to our benchmark suite—exclusively for press and influencers with over 1000 followers. See if you’re eligible and explore how our suite drives innovation in ray-tracing hardware by opt...
www.evolvebenchmark.com
June 18, 2025 at 5:39 AM
Workgraph scores are now in the Hall of Fame!

This milestone is not only a recognition of Workgraph technology, but also an important step in bringing comprehensive GPU performance evaluation to the industry.

www.evolvebenchmark.com/hall-of-fame...
May 23, 2025 at 1:26 PM
aiida-workgraph-web-ui 0.1.4 (Planning)

Design flexible node-based workflow for AiiDA calculation.

Author: Xing Wang
📖Documentation

🧑‍💻Source
August 1, 2025 at 8:00 AM
aiida-workgraph 0.6.0 (Planning)

Design flexible node-based workflow for AiiDA calculation.

Author: Xing Wang
📖Documentation

🧑‍💻Source
August 1, 2025 at 7:00 AM
aiida-gui-workgraph 0.1.3 (Planning)

Design flexible node-based workflow for AiiDA calculation.

Author: Xing Wang
📖Documentation

🧑‍💻Source
July 29, 2025 at 3:00 AM
aiida-bader 0.1.8 (Planning)

Collections of node-based workflow created using aiida-workgraph.

Author: Xing Wang
📖Documentation

🧑‍💻Source
July 27, 2025 at 9:00 AM
Great Siggraph 2025. Tons of good talks. #AssassinsCreedShadows of course :), Gran Turismo 7, Activision, Neural Shading and Workgraph courses. Great stuff. And a lot of content is already online. It’s great to see so much sharing. #SIGGRAPH2025
Great Siggraph 2025 presentation of Gran Turismo's tonemapping pipeline, which also includes a fantastic introduction to light perception and tonemapping, its origins and how it evolved over the years with display technology, recommended read: blog.selfshadow.com/publications...
blog.selfshadow.com
August 14, 2025 at 11:11 PM
Ask ChatGPT if #workgraph #meshnode #AMD integrated into #blender #b3d . Sounds so interesting.

最近気になるAMDが発表してたworkgraphとmeshnode。もしBlenderが技術を実装したらどうなるかChatGPTに聞いてみた。
興味深い。
July 5, 2025 at 6:31 AM
Folks interested in p2p apps might want to read the history of OSAF/Chandler.
http://webseitz.fluxent.com/wiki/OSAF
OSAF
<p><a class="wikilog" href="http://webseitz.fluxent.com/wiki/MitchKapor">Mitch Kapor</a>'s <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OpenSource">Open Source</a> Applications Foundation, creator of <a class="wikilog_missing" href="http://webseitz.fluxent.com/wiki/Chandler">Chandler</a>, the <a class="wikilog" href="http://webseitz.fluxent.com/wiki/WorkGraph">WorkGraph</a> <a class="wikilog" href="http://webseitz.fluxent.com/wiki/PIM">PIM</a> for <a class="wikilog" href="http://webseitz.fluxent.com/wiki/FreeAgent">Free Agent</a>s. <a href="http://www.osafoundation.org/">http://www.osafoundation.org/</a></p> <p>As of Dec'2011</p> <ul> <li>last blog entry Jul30'2009</li> <li>no commits since Nov'2009!</li> <li>download binary app at <a href="http://chandlerproject.org/Projects/DownloadChandlerDesktop">http://chandlerproject.org/Projects/DownloadChandlerDesktop</a></li> <li>download source at <a href="http://downloads.osafoundation.org/chandler/releases/1.0.3/">http://downloads.osafoundation.org/chandler/releases/1.0.3/</a> <ul> <li>instructions <a href="http://chandlerproject.org/Developers/ChandlerDesktopSource">http://chandlerproject.org/Developers/ChandlerDesktopSource</a></li> </ul> </li> </ul> <p>See <em><a class="wikilog" href="http://webseitz.fluxent.com/wiki/DreamingInCode">Dreaming in Code</a></em> book.</p> <p><a class="wikilog_missing" href="http://webseitz.fluxent.com/wiki/RemoteWikiURLhttpwikiosafoundationorgbinviewMain">RemoteWikiURL:http://wiki.osafoundation.org/bin/view/Main/</a></p> <p>Created in 2002 by <a class="wikilog" href="http://webseitz.fluxent.com/wiki/MitchKapor">Mitch Kapor</a></p> <p>The mission includes: <em>carry forward the vision of <a class="wikilog" href="http://webseitz.fluxent.com/wiki/VannevarBush">Vannevar Bush</a>, <a class="wikilog" href="http://webseitz.fluxent.com/wiki/DouglasEngelbart">Douglas Engelbart</a>, and <a class="wikilog" href="http://webseitz.fluxent.com/wiki/TedNelson">Ted Nelson</a> of the computer as a medium for communication, <a class="wikilog" href="http://webseitz.fluxent.com/wiki/Collaboration">Collaboration</a>, and coordination</em></p> <p>Initially building the "Chandler" (code-name) <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OpenSource">Open Source</a> <a class="wikilog" href="http://webseitz.fluxent.com/wiki/PIM">PIM</a>. <a class="wikilog" href="http://webseitz.fluxent.com/wiki/P2P">P2P</a> data sharing, smarts like <a class="wikilog" href="http://webseitz.fluxent.com/wiki/LotusAgenda">Lotus Agenda</a>. Death to <a class="wikilog" href="http://webseitz.fluxent.com/wiki/MsOutlook">MsOutlook</a>!</p> <ul> <li><a href="http://wiki.osafoundation.org/bin/view/Journal/ChandlerInFifteenMinutes">http://wiki.osafoundation.org/bin/view/Journal/ChandlerInFifteenMinutes</a></li> </ul> <p>Technologies (at least initially): <a class="wikilog" href="http://webseitz.fluxent.com/wiki/RDF">RDF</a>, <a class="wikilog" href="http://webseitz.fluxent.com/wiki/ZODB">ZODB</a>, <a class="wikilog" href="http://webseitz.fluxent.com/wiki/Python">Python</a>, <a class="wikilog" href="http://webseitz.fluxent.com/wiki/WxPython">WxPython</a>.</p> <p>Road <a href="http://www.osafoundation.org/Chandler-Product_Roadmap.htm">map</a> uses <a class="wikilog" href="http://webseitz.fluxent.com/wiki/CrossingTheChasm">Crossing The Chasm</a> model for prioritizing feature development.</p> <p><a href="http://webseitz.fluxent.com/wiki/">OSAF:OSAFStatusReports</a></p> <p>nice <a href="http://archive.neotonic.com/archive/osaf-design">alternative</a> design-list archives</p> <p><a class="wikilog_missing" href="http://webseitz.fluxent.com/wiki/RepositoryAccessProtocol">Repository Access Protocol</a> (RAP) <a href="http://lists.osafoundation.org/pipermail/design/2003-February/002024.html">will</a> <em>resemble an extended version of <a class="wikilog" href="http://webseitz.fluxent.com/wiki/IMAP">IMAP</a>, and so would be especially suited to use as a <a class="wikilog" href="http://webseitz.fluxent.com/wiki/IMAP">IMAP</a> server, and the similarity is partly driven by <a class="wikilog_missing" href="http://webseitz.fluxent.com/wiki/LouMontulli">Lou Montulli</a>'s appreciation of <a class="wikilog" href="http://webseitz.fluxent.com/wiki/IMAP">IMAP</a>. It is also driven by our appreciation of <a class="wikilog" href="http://webseitz.fluxent.com/wiki/IMAP">IMAP</a> as a message based protocol that is trivially easy to use in modeling items as messages, because they are simply objects composed of attributes. We have talked about using a RAP server as the implementation of other kinds of servers, including ones you mention as well as CAP.</em></p> <hr/> <p>My current (Oct'02) recommendations, mostly <strong>meta-process</strong> stuff:</p> <ul> <li>think like a "PlatForm" vs an "application"</li> <li><strong>start by documenting some <a class="wikilog" href="http://webseitz.fluxent.com/wiki/UserScenarios">User Scenarios</a></strong> (see <a class="wikilog" href="http://webseitz.fluxent.com/wiki/CollaborationWare">Collaboration Ware</a> for some rough notes I did months ago). That way discussions about how/why to do things like scheduling meetings or browsing remote data will be grounded.</li> <li>get the platform code out there before the application is ready (e.g. <a class="wikilog" href="http://webseitz.fluxent.com/wiki/RDF">RDF</a>/<a class="wikilog" href="http://webseitz.fluxent.com/wiki/ZODB">ZODB</a>). Let other people start working on complementary apps. Keep code modular, and define APIs, so that other <a class="wikilog" href="http://webseitz.fluxent.com/wiki/EMail">EMail</a> clients can be used.</li> <li>push out lots of info, don't worry about cleaning it up. Publish notes from every meeting/decision immediately, via <a class="wikilog" href="http://webseitz.fluxent.com/wiki/Wiki">Wiki</a>. Have each developer use that as a <a class="wikilog" href="http://webseitz.fluxent.com/wiki/WikiWeb">WikiWeb</a>log. Make all this read-only for the public.</li> <li>have <a href="http://lists.osafoundation.org/pipermail/design/2002-October/thread.html#387">some mechanism</a> for making public input manageable. <ul> <li>The goal is to improve the delivered code, not have a kibbitz klatsch.</li> <li>I'm not sure a <a class="wikilog_missing" href="http://webseitz.fluxent.com/wiki/MailingList">Mailing List</a> is manageable. But it's probably the optimal high-volume channel.</li> <li>I don't think a Wiki works for discussion (see WikiFor<a class="wikilog" href="http://webseitz.fluxent.com/wiki/CollaborationWare">Collaboration Ware</a>). It's too hard to follow/find new comments. Having to re-read a page to find the refactored bits is annoying.</li> <li>Maybe a public wiki that parallels the controlled wiki? (e.g. the team has its site which the public can only read, there's a parallel wide-open wiki) see <a class="wikilog" href="http://webseitz.fluxent.com/wiki/WikiWeb">WikiWeb</a> ideas (esp <a class="wikilog" href="http://webseitz.fluxent.com/wiki/SisterSites">Sister Sites</a>)...</li> <li>Maybe use <a class="wikilog" href="http://webseitz.fluxent.com/wiki/SlashCode">SlashCode</a> to filter user comments? (You could auto-generate a <a class="wikilog" href="http://webseitz.fluxent.com/wiki/SlashCode">SlashCode</a> item for each wiki page! Of course that could get weird as the content of a wiki page changed, or even moreso if pages get renamed...) <ul> <li><a class="wikilog" href="http://webseitz.fluxent.com/wiki/PaulSnively">Paul Snively</a> <a href="http://lists.osafoundation.org/pipermail/design/2002-October/000399.html">recommended</a> the <a class="wikilog" href="http://webseitz.fluxent.com/wiki/Advogato">Advogato</a> engine. Whether that engine/model is responsible for the signal/noise quality on that site is maybe open to debate. It also seems to focus on limiting spam potential of people more than providing feedback on the quality of individual postings (though I could be wrong, I've haven't paid much attention to the workings of the site).</li> </ul> </li> </ul> </li> </ul> <p><strong>Specific feature requests</strong></p> <ul> <li><a href="http://webseitz.fluxent.com/wiki/">OSAF:Optional</a><a class="wikilog" href="http://webseitz.fluxent.com/wiki/WikiName">Wiki Name</a>ForEveryItem (also see <a class="wikilog" href="http://webseitz.fluxent.com/wiki/WikiMail">WikiMail</a>, <a class="wikilog" href="http://webseitz.fluxent.com/wiki/WikiProxy">WikiProxy</a>)</li> <li>hierarchical tasks - see <a class="wikilog" href="http://webseitz.fluxent.com/wiki/ProjectFlux">Project Flux</a></li> <li><a class="wikilog" href="http://webseitz.fluxent.com/wiki/UniversalInbox">Universal Inbox</a></li> <li>either publish subset of thoughts out to multiple wiki spaces, or have very granular controls of outsider access to local items.</li> <li>Visual input/output: <a class="wikilog" href="http://webseitz.fluxent.com/wiki/MindMapping">Mind Mapping</a>, <a class="wikilog" href="http://webseitz.fluxent.com/wiki/GraphDrawing">Graph Drawing</a>, <a class="wikilog" href="http://webseitz.fluxent.com/wiki/TouchGraph">Touch Graph</a></li> </ul> <hr/> <p><strong><a class="wikilog" href="http://webseitz.fluxent.com/wiki/UserScenarios">User Scenarios</a>, personas, etc.</strong></p> <p>I've been (Nov'02) kvetching about a lack of requirements-context documentation, and Mitch replied that he thinks the current site docs do a pretty good job, asking if there are specific questions I think are relevant. So I'll have to think about that a bit.</p> <p>They key source documents are the <a href="http://www.osafoundation.org/mission_statement.htm">mission</a> , <a href="http://www.osafoundation.org/our_product_desc.htm">product description</a> , and <a href="http://www.osafoundation.org/feature_summary.htm">feature summary</a> .</p> <p>Some user attributes:</p> <ul> <li>individual <a class="wikilog" href="http://webseitz.fluxent.com/wiki/FreeAgent">Free Agent</a>, member of small team (<a class="wikilog" href="http://webseitz.fluxent.com/wiki/SmallCo">SmallCo</a>), or multiple small teams</li> <li>have a primary "real computer" (desktop or laptop), but may also use additional machine (home desktop, etc.) <ul> <li>any philosophical/logistical issues with having lots of data, personal and "group", sloshed together in a single repository running on a company-owned machine? Maybe philosophical issues are less of an issue on smaller teams, which presumably value their members more as autonomous humans, vs <a class="wikilog" href="http://webseitz.fluxent.com/wiki/BigCo">BigCo</a> cogs. But lawyers can make this an issue (esp where outside investment is involved, I suppose).</li> </ul> </li> <li>may also have a <a class="wikilog" href="http://webseitz.fluxent.com/wiki/PDA">PDA</a>. Willing to switch from a narrow/closed model like the <a class="wikilog" href="http://webseitz.fluxent.com/wiki/PalmOS">PalmOS</a> to something that could more realistically run an <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OSAF">OSAF</a> (lite) client, like a <a class="wikilog" href="http://webseitz.fluxent.com/wiki/SharpZaurus">Sharp Zaurus</a>? Or do we have to plan on having a model that can <a class="wikilog" href="http://webseitz.fluxent.com/wiki/DataSynch">Data Synch</a> to <a class="wikilog" href="http://webseitz.fluxent.com/wiki/PalmOS">PalmOS</a> core <a class="wikilog" href="http://webseitz.fluxent.com/wiki/PIM">PIM</a> applications? Will lack of <em>any</em> <a class="wikilog" href="http://webseitz.fluxent.com/wiki/PDA">PDA</a> support be a signficant barrier to adoption for many people (besides me)? <ul> <li>some searches to see if people are having success with the Zaurus (which uses <a class="wikilog" href="http://webseitz.fluxent.com/wiki/PyQt">PyQt</a> instead of PyWindows) <ul> <li><a href="http://www.google.com/search?q=zaurus%20chandler">http://www.google.com/search?q=zaurus%20chandler</a></li> <li><a href="http://www.google.com/search?q=zaurus%20zodb">http://www.google.com/search?q=zaurus%20zodb</a></li> <li><a href="http://www.google.com/search?q=zaurus%20wxwindows">http://www.google.com/search?q=zaurus%20wxwindows</a></li> <li><a href="http://www.google.com/search?q=zaurus%20wxembedded">http://www.google.com/search?q=zaurus%20wxembedded</a></li> </ul> </li> </ul> </li> </ul> <p>Product definition, Positioning, etc.</p> <ul> <li><a class="wikilog" href="http://webseitz.fluxent.com/wiki/PIM">PIM</a> similar to <a class="wikilog" href="http://webseitz.fluxent.com/wiki/MsOutlook">MsOutlook</a>, <a class="wikilog" href="http://webseitz.fluxent.com/wiki/Evolution">Evolution</a>, but...</li> <li>free, <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OpenSource">Open Source</a> <ul> <li>won't disappear (unlike <a class="wikilog" href="http://webseitz.fluxent.com/wiki/LotusAgenda">Lotus Agenda</a>, <a class="wikilog" href="http://webseitz.fluxent.com/wiki/EccoPro">Ecco Pro</a>, <a class="wikilog" href="http://webseitz.fluxent.com/wiki/InfoDepot">InfoDepot</a>, etc.)</li> <li>can keep evolving</li> </ul> </li> <li>won't require a server (other than <a class="wikilog" href="http://webseitz.fluxent.com/wiki/EMail">EMail</a>) for sharing info (e.g. <a class="wikilog" href="http://webseitz.fluxent.com/wiki/GroupCalendaring">Group Calendaring</a>)</li> <li>some superior <a class="wikilog_missing" href="http://webseitz.fluxent.com/wiki/RocketScience">Rocket Science</a> features <ul> <li><a class="wikilog" href="http://webseitz.fluxent.com/wiki/LotusAgenda">Lotus Agenda</a> organizating capabilities</li> <li>....</li> </ul> </li> </ul> <p>Hmm, I think Mitch may be right that the basic mission/vision is reasonably well defined. Looking at some specific email threads I've found frustrating, maybe what I'm looking for is a mid-level context for those threads, like which specific <a class="wikilog" href="http://webseitz.fluxent.com/wiki/UserStories">User Stories</a> are being targeted. For instance, in this <a href="http://lists.osafoundation.org/pipermail/dev/2002-November/thread.html#241">thread</a> about existing <a class="wikilog" href="http://webseitz.fluxent.com/wiki/P2P">P2P</a> systems and synchronization, is the goal to get updated contact information for another <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OSAF">OSAF</a> user, or to get updated versions of a bunch of note items on another <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OSAF">OSAF</a> user's machine, or something else? Expecting one approach to solve both problems efficiently may not be realistic.</p> <hr/> <p>My <strong>short-term desires</strong> (Nov'02): deliver as soon as possible a tool which provides:</p> <ul> <li>basic single-user <a class="wikilog" href="http://webseitz.fluxent.com/wiki/PIM">PIM</a> features comparable to <a class="wikilog" href="http://webseitz.fluxent.com/wiki/MsOutlook">MsOutlook</a></li> <li>a mechanism for <a class="wikilog" href="http://webseitz.fluxent.com/wiki/GroupCalendaring">Group Calendaring</a> (personally, I don't even need <em>that</em> yet, but I suspect it's important for others) (a first pass could be extremely simple)</li> <li>a <a class="wikilog" href="http://webseitz.fluxent.com/wiki/PDA">PDA</a> solution</li> </ul> <p>This means I'd rather see <em>not</em> dealt with until v2:</p> <ul> <li><a class="wikilog" href="http://webseitz.fluxent.com/wiki/EMail">EMail</a> client (I'll use <a class="wikilog" href="http://webseitz.fluxent.com/wiki/Mozilla">Mozilla</a> for that)</li> <li>fancy view and auto-categorizing features (I actually think that being able to optionally assign a <a class="wikilog" href="http://webseitz.fluxent.com/wiki/WikiName">Wiki Name</a> to every item, and have any <a class="wikilog" href="http://webseitz.fluxent.com/wiki/WikiName">Wiki Name</a> in any field be automatically a link to that named item, would provide plenty of <a class="wikilog" href="http://webseitz.fluxent.com/wiki/Intertwingularity">Intertwingularity</a> for now)</li> <li>other <a class="wikilog" href="http://webseitz.fluxent.com/wiki/P2P">P2P</a>/sharing features beyond basic <a class="wikilog" href="http://webseitz.fluxent.com/wiki/GroupCalendaring">Group Calendaring</a></li> </ul> <p>Here's Mitch's <a href="http://blogs.osafoundation.org/mitch/2002_11.html">posting</a> about the schedule, made later the same day as the notes above...</p> <hr/> <p>thoughts on <strong>licensing</strong></p> <p>As of Apr'03, the <a href="http://webseitz.fluxent.com/wiki/">OSAF:LicensingPlan</a> is to emulate <a class="wikilog" href="http://webseitz.fluxent.com/wiki/MySQL">MySQL</a>: a developer can use/build on <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OSAF">OSAF</a> with an <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OpenSource">Open Source</a> arrangement (meaning that all code developed on top of it be returned (with ownership rights) to <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OSAF">OSAF</a>, or the developer can purchase a commercial license and build his own proprietary stuff on top of it.</p> <p>Weird thought: what if the code were completely <a class="wikilog" href="http://webseitz.fluxent.com/wiki/PublicDomain">Public Domain</a> (or some other structure) and thus any developer could build his own commercial/proprietary apps on top of it without paying a license?</p> <p>This would probably increase the use of <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OSAF">OSAF</a>. (By coincidence, here's <a href="http://scriptingnews.userland.com/backissues/2001/04/15#letAThousandFlowersBloom">something</a> <a class="wikilog" href="http://webseitz.fluxent.com/wiki/DaveWiner">Dave Winer</a> wrote 2 years ago.)</p> <p>What would be the downside?</p> <ul> <li>that licensing revenue stream lost, reduces viability of <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OSAF">OSAF</a> long-term existence (given that Mitch probably doesn't want to play <a class="wikilog" href="http://webseitz.fluxent.com/wiki/GoldOwner">Gold Owner</a> forever). <ul> <li>another potential revenue stream: <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OSAF">OSAF</a> team would be considered the world experts on the platform, so they'd probably be getting requests for custom development all the time, so they could spend part of their time on revenue-generating contract work. The <a class="wikilog" href="http://webseitz.fluxent.com/wiki/Zope">Zope</a> team does this - that custom code doesn't go back into the platform, though a lot of it tends to result eventually in development of generalized platform-level code (e.g. <a class="wikilog" href="http://webseitz.fluxent.com/wiki/ZopeCMF">ZopeCMF</a>) which they <em>then</em> put into the base product. It's also not clear to me whether <a class="wikilog" href="http://webseitz.fluxent.com/wiki/Zope">Zope</a>'s <a href="http://www.zope.org/Resources/License">license</a> requires changes to be delivered back to them.</li> </ul> </li> <li>many improvements to underlying platform would be hidden in proprietary implementations, so platform would not improve as much - which might also keep underlying platform from reaching community <a class="wikilog" href="http://webseitz.fluxent.com/wiki/CriticalMass">Critical Mass</a>. <ul> <li>maybe there's some sort of <a class="wikilog_missing" href="http://webseitz.fluxent.com/wiki/CompatibilityTest">Compatibility Test</a> that could be defined, which a proprietary app would have to pass in order to be "<a class="wikilog" href="http://webseitz.fluxent.com/wiki/OSAF">OSAF</a>-Compliant", which might add marketing value to such products. Thus any low-level changes which would break compatibility would negate this compliance - so such a developer would have an incentive to donate back platform-level stuff, while keeping app-level stuff to himself.</li> </ul> </li> </ul> <hr/> <p>thoughts on <strong>merging/integrating <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OSAF">OSAF</a> and <a class="wikilog" href="http://webseitz.fluxent.com/wiki/Mozilla">Mozilla</a></strong> (Jul'03)</p> <p>We (the users) need a decent app that includes <a class="wikilog" href="http://webseitz.fluxent.com/wiki/EMail">EMail</a> and <a class="wikilog" href="http://webseitz.fluxent.com/wiki/GroupWare">GroupWare</a>/<a class="wikilog" href="http://webseitz.fluxent.com/wiki/PIM">PIM</a> features. It also really needs to be a <a class="wikilog" href="http://webseitz.fluxent.com/wiki/MicroContent">MicroContent</a> reader and writer. <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OSAF">OSAF</a> intends to deliver that.</p> <p><a class="wikilog" href="http://webseitz.fluxent.com/wiki/EMail">EMail</a> probably needs to be the centerpiece because that's what people use the most. Any other mode which needs to grab the user's attention probably needs to get to them via the <a class="wikilog" href="http://webseitz.fluxent.com/wiki/EMail">EMail</a> client.</p> <p>But <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OSAF">OSAF</a> has been seeking an <a class="wikilog" href="http://webseitz.fluxent.com/wiki/EMail">EMail</a> guru for months with no apparent progress.</p> <p>It keeps smelling to me like <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OSAF">OSAF</a> and <a class="wikilog" href="http://webseitz.fluxent.com/wiki/Mozilla">Mozilla</a> should merge. What do I want?</p> <p>More precisely, why not just use <a class="wikilog" href="http://webseitz.fluxent.com/wiki/Mozilla">Mozilla</a> and <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OSAF">OSAF</a> side by side?</p> <ul> <li>Well, to some extent it's not about <em>my</em> options, it's about wanting <a class="wikilog" href="http://webseitz.fluxent.com/wiki/OSAF">OSAF</a> to get used by <em>lots</em> of people. And not having <a class="wikilog" href="http://webseitz.fluxent.com/wiki/EMail">EMail</a> keeps that from happening.</li> <li>want address book integration</li> <li>want to build a <a class="wikilog" href="http://webseitz.fluxent.com/wiki/UniversalInbox">Universal Inbox</a> - 2 of the key incoming message types are <a class="wikilog" href="http://webseitz.fluxent.com/wiki/RSS">RSS</a> and <a class="wikilog" href="http://webseitz.fluxent.com/wiki/EMail">EMail</a>. <a class="wikilog" href="http://webseitz.fluxent.com/wiki/Mozilla">Mozilla</a>'s too big a pain for me to consider building a good <a class="wikilog" href="http://webseitz.fluxent.com/wiki/RSS">RSS</a> handler in (now if someone built high-level <a class="wikilog" href="http://webseitz.fluxent.com/wiki/Python">Python</a> wrappers for everything - not just <a class="wikilog" href="http://webseitz.fluxent.com/wiki/PyXpCom">PyXp Com</a> - I might feel differently)</li> <li>don't want to end up with 2 Gecko engines running in memory at the same time</li> <li></li> </ul> <p>See these events:</p> <ul> <li><a class="wikilog" href="http://webseitz.fluxent.com/wiki/2003-06-26-MitchKaporInterview">2003-06-26-Mitch Kapor Interview</a></li> <li><a class="wikilog" href="http://webseitz.fluxent.com/wiki/2003-07-18-MozillaCutFromAol">2003-07-18-MozillaCutFromAol</a> - probably what led to my notes above <ul> <li><em><a class="wikilog" href="http://webseitz.fluxent.com/wiki/DreamingInCode">Dreaming In Code</a></em> says that they had internal discussions about this issue at this time, and lays out some of the arguments, but then just says it was "settled" within a month, without giving any meaty sense of the key reason.</li> </ul> </li> <li>I finally asked about integration <a class="wikilog" href="http://webseitz.fluxent.com/wiki/2004-02-27-OsafMozMail">2004-02-27-OsafMozMail</a></li> </ul> <hr/>
webseitz.fluxent.com
January 8, 2025 at 3:14 PM
I've reached the first milestone of creating an extensible terrain system for #r3f and #threejs

next step: heightmaps via #webgpu compute

hello-terrain.kenny.wtf/examples
Hello World
Quadtree upload to GPU via WorkGraph
hello-terrain.kenny.wtf
February 6, 2026 at 2:02 PM