Bryan and Adam reminisce about the DTrace journey 20 years after first integrating the code into Solaris back in September 2003.In addition to Bryan Cantrill and Adam Leventhal, we were joined by Josh Clulow.Some of the topics we hit on, in the order that we hit them: Hungry Jack's Bryan's other online dating profile The Sun E10000 (E10k), the world's worst router Leventhal's Conundrum DTrace as Half-Life 3, eternal vaporware More on SPARC, it's TLB, the %npc, and dtrace_fish from OxF May 2021 Solaris 9 was the completion of the Solaris 2.0 vision DTrace Kernel Technical Discussion (2002) Mr. Sparkle Firefox? Mozilla? Firebird! Dynamic Instrumentation of Production Systems, Usenix 2004 Graydon on DTrace in Rust Rust USDT crate DTrace on Windows Adam's blog: DTrace on macOS Adam's blog: DTrace for OEL PSARC cases from 2003 If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

Kelsey Hightower joined Bryan and Adam to revisit a topic Bryan had spoken about a decade ago: corporate open source anti-patterns. Kelsey brought his typical sagacity to a complex and fraught topic.We've been hosting a live show weekly on Mondays at 5p for about an hour, and recording them all; here is the recording from August 28th, 2023.In addition to Bryan Cantrill and Adam Leventhal, we were joined by Kelsey Hightower.Here is the (lightly edited) live chat from the show: xxxxbubbler: https://www.youtube.com/watch?v=Pm8P4oCIY3g here is Bryan's talk from 1 decade ago, for reference rolipo.li: web3 is going great rolipo.li: https://web3isgoinggreat.com/ ahl0003: Last time Kelsey joined us for predictions blainehansen: "Governance orgies" happen when the governance mechanisms aren't well-designed ha. If they are well-designed then governance is good! jbk: opsware maybe? or tivoli? uptill3: hp openview was one as well sevanj: "they've got us working for trinkets" sevanj: this was mentioned on the bugzilla anouncement regarding funded staff being pulled from working on project in the last 3 years. blainehansen: All open source problems are secretly public goods problems haha carpetbomberz.com: Hashicorp DID do a "thing" blacksmithforlife: Just like taxes fund roads, we should have a internet usage tax that then funds these open source projects that everyone finds value in. The person taxed should get to decide which open source project gets the money kaliszad: The problem is, you can help other people, but first you have to sustain yourself. 🙂 aarondgoldman: Too boring to be evil rolipo.li: too busy to be evil? aarondgoldman: Angular never got budget even when Inbox used it and had millions of users blainehansen: Most open source projects are probably not best led/governed by a for-profit company ha aarondgoldman: HP had a huge repair service business when their hardware got much more reliable it almost killed the company geekgonecrazy: Never actually considered using CNCF membership as a qualification for using a tool ahl0003: it's the nintendo seal of quality! geekgonecrazy: It’s an interesting thought now that I’ve heard it 🙈 especially for any sort of core utility like this saone: On the topic of patterns that seem to be working, Docker Desktop's license requiring subscriptions for larger organizations for use of their product and focusing on providing a really good developer experience seems to be a really good spot for them to be goodjanet: The term freeloading comes up only when there's a "problem" (usually fiscal in a company/group), the rest of the time the exact same actions are fine or often encouraged mrdanack: I disagree, there are freeloaders. Multi-billion companies like IBM and Oracle have benefited from the PHP project for multiple decades and really haven't contributed even a modest amount back. geekgonecrazy: Anytime hitting CLA I always use that as clue to take hesitation and think about contributing. 🙈 quasarken: I love that bit about community Adam blacksmithforlife: https://www.linux.com/news/us-government-opens-access-federal-source-code-codegov/ blainehansen: Sometimes a community of passionate contributors is more a burden than a gift. Every project is different, not every project can be supported by many well-paid engineers at vc-funded incentive-aligned companies. I don't think the BUSL is smart or good, but there's a funding/support problem here that legitimately needs to be solved, and the existing open source social contract hasn't solved it. https://www.jeffgeerling.com/blog/2022/burden-open-source-maintainer blacksmithforlife: Disclaimer: I'm a federal employee who tried to get more software open source while I was working at various agencies. For the most part it was soundly ignored and the agencies just claimed it was too hard and they didn't have enough funding to do it, which in my opinion is just false blacksmithforlife: But, if you want it, just do a FOIA, then they have to give it to you saone: There's a great deal of fear at my company that software being open sourced must be carefully vetted to avoid potential embarassment so the hurdles to open source anything are very high girgias: The French government has released code which was pure garbage, and I don't think one can do worse than the APB code geekgonecrazy: That sucks. 😬I can totally see individual developers being afraid. I’ve faced that with my team. Weird to think org would be especially if trusting engineers northrup: Adam to your point though - I don't see how that's any different than other open source projects that aren't corporate backed. No open source projected is obligated to honor your issue to drive a project in a direction, or accept your PR to add a feature or function... ahl0003: Great point! blainehansen: The open source cooperative idea is the best I can come up with to solve the problem blacksmithforlife: What is dev rail? bcantrill: Developer relations ahl0003: developer relations jbk: dev rel(ations)? bcantrill: JYNX blacksmithforlife: Never heard that term before geekgonecrazy: Curious at what scale you think devrel is needed vs the engineers in company directly involved geekgonecrazy: I’ve often wondered if doesn’t create unnecessary barrier between engineers and community. Especially at certain size quasarken: Dev Rel seems a lot like community solutions engineering geekgonecrazy: I’ve personally seen some companies use devrel as sole tie to open source and “community” in place of more of company getting involved rolipo.li: devrel as a service. now it's a consulting firm? northrup: When I worked at GitLab in the early days, some of my most favorite experiences were going to conferences and hanging out in the GitLab booth to answer questions and talk with / help users. SOO much great feedback, clear "oh wow!" edge cases brought forward, and amazing feedback of "yeah, you made this feature, but that wasn't what we needed" ahl0003: I remember liking this book on devrel: https://www.amazon.com/Business-Value-Developer-Relations-Communities/dp/1484237471 rolipo.li: > hello world to hello revenue geekgonecrazy: I forget how blessed I’ve been getting to work for company that started as open source project 🙈 sevanj: that's a benefit ophilli: Do y'all consider the work you do on Oxide & Friends and On The Metal to be investments in dev rel? ahl0003: I think probably closer to brand marketing... on the cheap? ahl0003: or just a way to keep Bryan off the streets and out of trouble northrup: I was going to say "probably more cathartic for Bryan" 😂 rolipo.li: "here's a dead project we found in our version control" punt. thunk. rolipo.li: didn't bryan give a talk about oxide n frens? something about capturing oral history. a172: Bryan's talk on the power of social audio blacksmithforlife: Have you done an episode on subscription software? I really hate how I can't buy something and own it forever (if I really want your upgrades then I'll pay for the next version) rolipo.li: people wanna yoink ur pie? make the pie so big they'll choke. ahl0003: second week in a row that I 'm going to recommend Stephen O'Grady's book: https://www.amazon.com/Software-Paradox-Rise-Commercial-Market/dp/1491900938 sevanj: did you see the wipeout rewrites that have been coming out in recent weeks rolipo.li: the oxide github is great goodjanet: i wish more old games were open sourced blacksmithforlife: And their tool chains. When I worked at the library of Congress, it was near impossible to build some of these games because there was no documentation on what tools they used and how to build the software saone: there have been a few (Freespace, Warzone 2100, Red Alert...) but it definitely isn't widespread, and there are ungodly licensing issues surrounding that from what I understand blacksmithforlife: https://blogs.loc.gov/thesignal/2012/09/yes-the-library-of-congress-has-video-games-an-interview-with-david-gibson/ geekgonecrazy: CLAs definitely make me take pause. Usually for this exact reason. I know giving them the flexibility to relicense with no warning geekgonecrazy: Fleet was pretty sweet blacksmithforlife: You might also like https://blogs.loc.gov/thesignal/2014/08/dukes-legacy-video-game-source-disc-preservation-at-the-library-of-congress/ rolipo.li: BDFL - benevolent dictator for life ahl0003: re: Swift: meet my friend, Perl 6 ahl0003: I love Go; I hate Go bcantrill: Kelsey on HN geekgonecrazy: 💯 it’s as much if not more about the people than the software goodjanet: people make things not corporations! kelseyhightower: Thanks for listening and hanging out with us. If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

On August 10th, HashiCorp made the controversial decision to re-license some of the popular, formerly-open source project under the Business Source License (BUSL). Bryan and Adam spoke with founders of the OpenTF project, an effort to keep Terraform operating in the open.In addition to Bryan Cantrill and Adam Leventhal, speakers on August 21st included Josh Padnick, Malcolm Matalka, and Cory O'Daniel.Our condolences to the friends, family, and loved ones of Kris NóvaOminous figure squeezing a fish that is vomiting gold coinsSome of the topics we hit on, in the order that we hit them: OpenTF HashiCorp BUSL announcement HashiCorp BUSL FAQ Squeezefish "Interview" (image) Cory's blog post CNCF issue for tracking Hashicorp license change If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

Bryan and Steve Klabnik discuss Fred Brooks' essay "No Silver Bullets"--ostensibly apropos of nothing!--discussing the challenges to 10x (or 100x!) improvements in software engineering.In addition to Bryan Cantrill speakers on included Steve Klabnik, Ian Grunert, and Tom Lyon.Some of the topics we hit on, in the order that we hit them: No Silver Bullet by Fred Brooks Sub-podcasting (it's a thing!) this video: Fred Brooks speaking on No Silver Bullet Ruby on Rails demo (2005) Future of coding podcast Amdahl's law FizzBuzzEnterpriseEdition Knuth and McIlroy Approach a Problem If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

In an Oxide and Friends tradition, Bryan and Adam invite the community to share book recommendations.In addition to Bryan Cantrill and Adam Leventhal, speakers on included Steve Klabnik, Tom Lyon, Ian Grunert, Owen Anderson, phillipov, makowski, and saethlin. (Did we miss your name and/or get it wrong? Drop a PR!)Some of the topics we hit on, in the order that we hit them: Elon Jet High Noon: The Inside Story of Scott McNealy and the Rise of Sun Microsystems by Southwick, Karen Making PCR: A Story of Biotechnology by Paul Rabinow Sun Labs vs. SunSoft Water Fight 1992 Cyberville: Clicks, Culture, and the Creation of an Online Town Hardcover by Stacy Horn Built to Fail: The Inside Story of Blockbuster's Inevitable Bust Kindle Edition by Alan Payne A History of Silicon Valley - Vol 1: The 20th Century Paperback by Piero Scaruffi H-E-B Moby Dick by Herman Melville (Arion Press) A Psalm for the Wild-Built by Becky Chambers Endurance: Shackleton's Incredible Voyage by Alfred Lansing Into the Raging Sea: Thirty-Three Mariners, One Megastorm, and the Sinking of El Faro If Then: How the Simulmatics Corporation Invented the Future Hardcover by Jill Lepore UNIVAC and the 1952 Presidential Election NPR: The Night A Computer Predicted The Next President Doom Guy: Life in First Person by John Romero From Secret Ballot to Democracy Sausage: How Australia Got Compulsory Voting by Judith Brett Bryan had a reading list for his wedding?! (his wife confirms) The Fatal Shore by Robert Hughes Harp in the South by Ruth Park Cloudstreet by Tim Winton Death of the Lucky Country by Donald Horne 30 Days in Sydney by Peter Carey Leviathan by John Birmingham The Fatal Shore: The Epic of Australia's Founding by Robert Hughes Barbarians Led by Bill Gates by Jennifer Edstrom and, Marlin Eller Murray Sargent's account of how his Scroll Screen Tracer got Windows to work in protected mode Startup: A Silicon Valley Adventure by Jerry Kaplan DeviceScript Washington: A Life by Chernow California Burning: The Fall of Pacific Gas and Electric--and What It Means for America's Power Grid Command and Control: Nuclear Weapons, the Damascus Accident, and the Illusion of Safety by Eric Schlosser The Color of Law: A Forgotten History of How Our Government Segregated America by Richard Rothstein Acts of the Apostles: Mind over Matter: Volume Blue by John F.X. Sundman Thunder Below!: The USS Barb Revolutionizes Submarine Warfare in World War II by Eugene B. Fluckey Thinking, Fast and Slow by Daniel Kahneman The Man Who Solved the Market: How Jim Simons Launched the Quant Revolution by Gregory Zuckerman The Predictors: How a Band of Maverick Physicists Used Chaos Theory to Trade Their Way to a Fortune on Wall Street by Thomas A. Bass The Eudaemonic Pie: The Bizarre True Story of How a Band of Physicists and Computer Wizards Took On Las Vegas by Thomas A Bass Some of the other books mentioned in the Discord channel: Herr aller Dinge/Lord of All Things by Andreas Eschbach Debt: The First 5,000 Years by David Graeber The Sciences of the Artificial by Herbert A. Simon California Burning: The Fall of Pacific Gas and Electric--and What It Means for America's Power Grid by Katherine Blunt The Man Who Solved the Market: How Jim Simons Launched the Quant Revolution Hardcover by Gregory Zuckerman The Predictors: How a Band of Maverick Physicists Used Chaos Theory to Trade Their Way to a Fortune on Wall Street by Thomas A. Bass The Eudaemonic Pie: The Bizarre True Story of How a Band of Physicists and Computer Wizards Took On Las Vegas by Thomas A Bass Models.Behaving.Badly.: Why Confusing Illusion with Reality Can Lead to Disaster, on Wall Street and in Life by Emanuel Derman It's a Nonlinear World by Richard H. Enns Not technically books, but suggested reading nonetheless by folks in Discord: The Night A Computer Predicted The Next President by Steve Henn, NPR How a brilliant debugger (Scroll Screen Tracer by Murray Sargent) turned Windows OS into the IBM OS/2 crusher and gave Microsoft its killer product. DeviceScript: TypeScript for Tiny IoT Devices Bob and Ray | Slow Talkers of America | Audio Recording (YouTube) Ursula K. Le Guin The Maintenance Race by Stewart Brand If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!