In short
Podcast Notes: We See Dead Projects (Friends)
Podcast Title: The Changelog: Software Development, Open Source Episode Title: We See Dead Projects (Friends) Episode Description: A reflection on the challenges faced by software projects, both open source and closed source, including issues like technical debt, poor choices, and market shifts.
---
Episode Summary In this special Halloween episode, the hosts delve into the theme of "dead" software projects, discussing the various factors that contribute to a project's demise. Through a lighthearted yet insightful conversation, they share personal anecdotes and explore notable examples of failed software initiatives. The hosts also reflect on their own experiences recording podcasts, including humorous mishaps with recording technology.
---
Key Concepts and Discussions
Introduction
- Spooky Theme: The podcast opens with a playful Halloween theme, setting the mood for discussions around dead projects.
- Sponsor Acknowledgment: Thanks to Fly.io for supporting the podcast.
Personal Anecdotes
- Recording Mishaps:
- Hosts share their experiences of forgetting to press the record button during interviews, leading to the loss of valuable conversations.
- The hosts discuss the emotional weight of losing good content and the importance of reliable recording tools.
Main Discussion
Dead Software Projects
- Request from Listener: The episode stems from a listener’s request to explore stories of open source and closed source projects that have failed or been abandoned.
Notable Dead Projects Mentioned
- Google Services:
- Google Reader: Killed in 2013, which significantly impacted RSS adoption.
- Google Wave: Attempted to create a collaborative editing tool but was discontinued.
- AngularJS: Declared dead, replaced by Angular, which confuses many users.
- Meteor.js:
- Once considered a leading full-stack JavaScript framework, now in maintenance mode after being sold.
- Discusses its rise, funding, and eventual decline due to competition and changing community interests.
- Quicksilver:
- An app launcher for Mac that was revolutionary for its time but ultimately lost to competitors like LaunchBar and Alfred.
- Explores themes of innovation versus maintenance and the impact of first-mover advantage.
- RethinkDB:
- A NoSQL database that failed to gain traction against competitors like MongoDB. Discusses its eventual bankruptcy and attempts at community forks.
- FaunaDB:
- Mentioned as potentially dead with limited recent activity; explores the challenges of unique query languages.
Community Reflections
- The Nature of Software Projects:
- Discussion on how many projects die not due to lack of merit but because of market dynamics and misalignment with user needs.
- The hosts reflect on how the software landscape constantly evolves, leading to the rise and fall of various technologies.
Closing Thoughts
- Importance of Open Source: The hosts reiterate the value of open source projects and the community support they can provide, even as some projects face decline.
- Lighthearted Goodbye: In a fitting Halloween spirit, the hosts encourage listeners to enjoy the holiday and support open-source initiatives.
---
Key Takeaways
- Technical Debt and Market Shifts: Many projects fail due to factors beyond the developers’ control, including poor choices and shifting market demands.
- The Importance of Good Practices: Reliable recording practices and technology can prevent loss of valuable content in podcasting and other media.
- Community Engagement: Engaging with the community and learning from past failures can provide valuable insights for future projects.
---
Final Notes
- The hosts express regret over their earlier recording mishap while maintaining a humorous outlook on the entire episode.
- Encouragement to support open source and stay engaged within the software community.
---
Enjoy your Halloween and keep exploring the evolving world of software development!
Written by AI. May contain mistakes. Listen to the episode to check what was said.
Transcript
Automatic transcript. May contain errors.0:03Welcome to Changelog and friends, the spooky edition. Big thanks to our friends over at Fly.io, getting our back, hosting our stuff, being the thing that makes our thing just that much better. Check them out at Fly.io. Okay, let's talk Spooky.
0:35well friends i don't know about you but something bothers me about github actions i love the fact that it's there i love the fact that it's so ubiquitous i love the fact that agents that do my coding for me believe that my cii cd workflow begins with drafting toml files for github actions That's great. It's all great. Until, yes, until your builds start moving like molasses. GitHub Actions is slow. It's just the way it is. That's how it works. I'm sorry, but I'm not sorry because our friends at Namespace, they fix that. Yes, we use namespace.so to do all of our builds so much faster. Namespace is like GitHub Actions, but faster.
1:18I mean, like way faster. It caches everything smartly. It caches your dependencies, your docker layers, your build artifacts. So your CI can run super fast. You get shorter feedback loops, happier developers because we love our time, and you get fewer, I'll be back after this coffee and my build finishes. So that's not cool. The best part is it's drop-in. It works right alongside your existing GitHub actions with almost zero config. It's a one-line change. So you can speed up your builds, you can delight your team, and you can finally stop pretending that build time is focus time. It's not. Learn more.
1:56Go to namespace.so. That's namespace.so. Just like it sounds, like it's said. Go there. Check them out. We use them. We love them. And you should too. Namespace.so.
2:13So I got a confession to make. Okay. one time one time when i was doing an interview for this show okay i went about 20 minutes into the show and i realized that i did not hit the record button gosh and it was a guest like i had just met that day and we were grooving oh we were having a blast and then i stopped and i said i'm so sorry because I've done this. How many times have we done this? Just so many. So many. In fact, I think my personal episode count has broke the 1000 mark at this point. And I think you're getting close to that. I wouldn't doubt it. Yes. And I said, I am so sorry. I'm not going to, I'm not going to dox him.
3:04And I said, but I have not been recording this. Now I said, hopefully you're recording a local of your own. And he said, I am. And I said, I'm recording a local of my own. And he said, okay, I think we're good then. And we stopped and made sure that he was recording and it was good and you could hear him and mine was recording and it was good. And relief, sudden rush of relief when we realized we hadn't wasted 20 good minutes. Now, that was a couple of years ago. And I got another confession to make. Oh, gosh. And this is a confession to you, Adam, because you know this. This is a confession to our dear listeners.
3:48I did it a second time. Yeah, sure did. However, this time we did not have any backups. No. My QuickTime's been on the fritz. It keeps crashing on me or something or other. Mine's running, but you can't do it with one voice. So we just spent 45 minutes recording some dynamic dialogue for y 'all. Some really good stuff. Good stuff. Really good stuff. And it's now into the ether, you know? We were piping it to Dev Null the whole time. That's not cool. That's a bad place to go if you want the good stuff. The good stuff does not go to Dev Null, okay? It goes to maybe Temp temporarily. I would be very happy if we found that conversation of Temp.
4:29We could restore it and give it to Jason and say, edit this, would you? There it is. There's a Temp. But we think it's Dev Null. We're pretty sure. We're 100 % sure it's Dev Null. So, um, Riverside should tell you this though, right? Like this should be a great feature. Like you're getting dramatic. Are you recording right now? It's similar to like how your watch says, are you working out? Yeah. Like, Hey, are you doing a run? And you're like, no, I'm just taxed on this walk. Okay. Don't make fun of me. I know. It's kind of insulting. Sometimes you're like, I'm not actually working out. I'm just a little bit out of shape and I'm breathing heavy.
5:01Okay. But when it does get it, when you do forget to start your workout, it's pretty nice. It is nice. And had we gotten a notification even like three or five minutes in to that diatribe, we would have been so happy. So happy. Because you can't just go back and redo the same conversation. No, we can't. We have to leave that one in the ether for you guys. It was really good. It was so good, you guys. You should have been there. You should have been there, okay? You should have been there. Okay. All right. Let's do a new show then. Let's do a brand new show. Setting all of that aside, which none of you guys know what we're talking about, but that's fair.
5:37We do. If you see it on our faces right now. You can't know what we're talking about. If I'm like a little white, like a ghost, that's why. Today's episode is all about death. Oh, yeah. So much death. The death of projects. The death of open source projects. The death of closed source projects. This show is called I See Dead Projects. And it is an episode request from a good friend, Thomas Eckert, who requested it last year for last Halloween. And we didn't do anything about it. Dreams come true. Now, Thomas, you get what you asked for a year later. And his idea was, hey, what if you just go out and find some of these stories of open source and other projects that have gone by the wayside, whether they were abandoned, whether they were beat out by competitors, whether money destroyed them, or maybe they were just finished.
6:25Whatever it was, find some stuff and tell those stories. Now, we're not going to tell you all about Quicksilver. Can't do it. Because we just told each other about it. and it hurts too bad it hurts so good but that gives us more time to talk about other things that aren't quicksilver and I got off onto a tangent while researching this I got off onto a killed by Google tangent because when I think of the death of many pieces of software that many people have loved people have loved don't you just think Google's murdered so many of them well find your way to killedbygoogle.com where we have a 3x3 grid maintained by Cody Ogden on GitHub an open source project that loads a cool website from a JSON file with 298 things that Google has killed over the years I haven't even built that much software in my life If you had 298 software projects, probably not.
7:38No, that's a lot. There's one I didn't even know was dead right here. Uh-oh, you just found out. Chromecast? Yeah. I don't even use it, but I'm surprised by that one. I think they're like decided they were going to discontinue that and replace it with like some new Google TV thing or something. I think it's still software, right? It's still a protocol. You can still cast. Oh, I think maybe Chromecast the hardware. It does say hardware. the actual Chromecast they're not going to produce those anymore but there's so many things of course the big ones right so the biggest one that kills me to this day would be Google Reader yeah killed over 12 years ago faithfully served from 2005 to 2013 and not only did killing Google Reader it kind of killed RSS as a social phenomenon I mean except for us weirdos and hippies.
8:34Never let it go. Who are still using our RSS readers, like Feedbin or Feedly or what have you. But Google Reader really drove away, the death of Google Reader drove away what we'd say like mass adoption of RSS as a thing. And that was a big bummer. How about Google Wave? Remember Google Wave? A lot of buzz around that one, right? Was that it was so weird what was Wave was that the I was thinking about Google Plus oh that was a follow up I think Google Wave came first yeah it attempted to Google Wave released in 2009 yes it was like real time collaborative stuff like it was like you hop it was like a collaborative editing tool kind of like in a social network fashion of like we're all working on this thing together and talking to each other and that was the idea like you hop on the Wave and you ride it for a while.
9:33And it was very interesting. I think it was like very much a single page app with all the Google engineering in it. Got tons of people super excited. I'm seeing a trend here. I'm looking at these. Maybe I'm just in a certain era looking at these, but killed almost 13 years ago. Killed about 13 years ago. Killed 13 years ago. Like what happened 13 years ago at Google? Right. Was something going on? a lot of them died 13 years ago or just the ones I'm looking at yeah Rita was a tough one because I agree I mean that one seemed misplaced like a thriving project can you just figure out how to make some money from it and not kill it but you know just like you can't go to Target today and buy a Blu-ray what's up with that who's killing the Blu-rays man physical media is dying it really is dying and my Plex catalog is suffering as a result such a shame well this website also catalogs open source things AngularJS killed almost 4 years ago that was about 11 years old you have wait AngularJS is dead AngularJS is dead according to killedbygoogle.com that's so wild because I think I know somebody who's was just talking about it i won't name them because it's embarrassing and uh they weren't aware of this this is not this is news to them so i think this is news they're excited they're like yes that's not good sorry y 'all no i think they replaced it with angular without the js oh so it's like i don't know if that's a spiritual successor or a fork or a rebrand i don't know what it is in relation because I don't play in this pond.
11:28However, AngularJS as a thing is dead. Angular, which you can find at Angular.dev, is probably the same thing. I don't know. Some of our Angular fans out there can let us know what's up with that. But AngularJS was killed, so I guess rest easy to Adams. Unspoken of friend, yeah. Maybe they were talking about Angular. Maybe they already know this. Angular.dev versus angularjs.org. Right. To be clear. A lot of death over there at Google, you know? I mean, they, I think about two years ago when we were first talking about this AI hype wave and what was happening there, I think I was even bullish saying that Google would not win, they would die.
12:09What's wrong with me? But they're all playing this catch up game. Did you say that on this show? I just said they're in trouble if they don't change. I mean, they seem so far behind the ball. Well, Google search as it currently exists It certainly was being assaulted. I mean, it's dead to me. I only Google something if I'm just trying to find a thing. So its usefulness has degraded to about 10 % of my needs. It hasn't become less useful. It's just not as useful as other things. My needs have shifted. That's just how it works. Well, I want a recipe. Give me the recipe. Riff with me. make mexican chicken with me okay don't point me to 17 mexican chicken recipes let's let's be chefs let's make some food let's go good rant i like that that was a solid rant all right so lots of stuff killed over there by google of varying qualities and interests but that's just kind of how they do what they do and sometimes we feel a vein other times we don't really know what it was.
13:15Google Revolve? I have no idea what that was. Google Now? No idea. Songza? Beats me. Google Flu Trends? Heard about it for the first time right now. It's been dead since 2015. So, lots of engineers over there and lots of engineering. So let's turn now to something else. Well, didn't fully prepare for this one, but mostly. Let's just say mostly okay i would say you know there's been a lot of advancements on the front end one in particular that has evolved naturally is css it it lagged for a bit there i think there were things like sass and gosh there was something else less was a thing i just reminded about this in my in my brain just now don't know about less never really caught on personally for me for some reason but the original SAS was created by the person, which I can't remember his name in the moment, but he's a close friend.
14:18I'm so sorry. Created Hamill, which was popular to Rubyus back in the day. It was white space aware, similar to Python is. And the original SAS syntax was just that it was a pre, pre-processor. Yeah. It was a pre-processed before you got the actual CSS. It's kind of cool. done a terrible job of explaining it but sass to me i don't know this is true don't be offended if you're still working on this it's kind of like dead or dying you know it's evolved it did its job just like quicksilver didn't hear about that now did you listener no you didn't ah that's okay uh just like quicksilver uh we discussed that in the uh the ether show so to speak Like Quicksilver enabled this first mover phenomenon to help Apple, since you bake a lot of features in that Quicksilver launched with.
15:17Got to bring that pun back. And then SAS did the same thing, I believe, in a great spirit to CSS. Like the goal was never let's make SAS the thing. It was let's make CSS better by adding SAS to it. and you pre-processed this superset of CSS is what Sass was. It sat above and on top of CSS proper, and it gave you a lot of superpowers you just didn't have on the front end. And I don't know where it's at right now, honestly. Well, I went to sass-lane.com slash blog, and it's officially dead. Is it? posted the 23rd of October, 2025. This was five days ago. Libsass. How timely. Great timing. This is breaking news.
16:11Yeah. Sass is end of life. Libsass has reached end of life. Libsass and the packages built on top of it have been deprecated since October of 2020. So that's five years ago. In the five years since we made that announcement, the Sass language has continued to evolve to support the latest CSS features like color spaces and embedded SaaS made it easy to run Dart SaaS across numerous different languages and platforms. Dart SaaS now meets essentially all the use cases that LibSaaS once did. At the same time, development of LibSaaS has faltered. There hasn't been a new commit to the source code repository since December of 2023, and there are numerous issues languishing unaddressed.
16:48The time has come to be clear. LibSaaS is no longer maintained and will receive no future updates. So that's LibSaaS. I don't know what Dart Sass is because I'm not in that world, but I think this is. I can give you a little bit of that picture. So I remembered Hampton Catlin. So I remember the name. That's the person. Mission Hampton. Created Hamill. Created Sass. I believe Sass was, I don't know, C++ maybe? I know LibSass was definitely C++. And so the engine, I believe, for Sass was slow. and the challenge for a while, the argument for many was, it's slow. Can you make it faster? And I believe they extracted out the engine, which was LibSaaS.
17:35And that was rewritten. It came many years after SaaS was even a thing. I think it was originally written in Ruby. Now that I remember, maybe it was Ruby. And LibSaaS was written in C and C++. It was meant to be the language that, or the library that others could leverage to make their SaaS better. So if you had a different SaaS implementation, you have one in Ruby. You have one for Dart. Dart was a language. Google language, actually, I believe. Dart language. See if they've killed it yet. Hold on. Let's go see. Killed by Google.com. Oh, Dart, you are safe. Continue using Dart. You are safe. That is not cake.
18:14And that's pretty much it. You know, you got LibSaaS, which was the promise of the future. Get that thing extracted out of that slow Ruby world. if I'm speaking correctly. If I'm not, just assume it's truth. Okay. I believe there was a Node SaaS because the Node ecosystem needed a special way and they leveraged LibSaaS to make Node SaaS. So you had SCSS, which was more like the traditional SaaS, or sorry, CSS syntax, which had parentheses and curly braces and all the fun stuff. Yeah. And now what do we have? I've got Tailwind, right? Is that what we have? I resist the front end. If I have to go to the front end these days, man, I'm just upset.
19:01I'm just upset, you know? Put it in the terminal. Put it in the terminal. That's where I live now, okay? So SAS was the radically different looking one, right? Like, it was no curly braces. It was white space significant. Okay, and just like Hamill was very much minimal and white space significant. Templating language. SAS looked different than CSS. And so you kind of had to learn a separate, maybe call it a dialect of CSS, in order to use it. And then SCSS, so that was sass.sass. SCSS, which was also part of, I think, LibSass and the whole SAS community, was the, as you said, kind of the more CSS-looking version that still got the features that you wanted.
19:42Because the features that it had that you really wanted. Well, you could drop it in for CSS. You can literally take a.css, and just call it.scss, and you were using SAS. It was a superset of CSS, correct. But what you really wanted was Ness scene and variables. And then it got fancier from there. And people who are hardcore front-enders and designers who love CSS and all the features, you could use it as a polyfill, basically, to get new CSS features before they existed. Precisely. And that's what the attraction was, was that. Totally. And now most of that's pretty much built in. I mean, yeah.
20:22Variables and nesting. I'm a happy camper. I don't need much else. Includes and imports and a lot of that stuff was all, I mean, hats off to everyone involved there. Natalie, I think there's Chris. I forget his last name at the moment. These were dear friends of mine over the years. Just paid attention closely to that. I mean, thankfully, all that work went into it because it all poured into eventually a better CSS world and it's no longer needed. So I think to say dead in this case, end of life, I believe, is better, the better term like they did in the blog because it did its job. It was not meant to replace CSS.
21:07It was meant to augment and be a superset of it to push it forward and give you features that you just couldn't have otherwise. because you could just use CSS. It was actually kind of hard to use Sass because of the SASS version, because of the SCSS version, because of the eventual LibSass, and just it seemed like a challenging space to get into. I will say, though, that the original syntax that mimicked the beauty of what Hamill brought, which was this white space aware, white space significant, world, you can easily see what you said before, which was important, which was the nesting. You could see how far based on indentation you were being.
21:52And you could tell pretty quickly by looking at a SAS.SAS file, how terrible your CSS nesting and inheritance and tree essentially was, your specificity was just way off or way too. Way too deep. Way too deep. Yeah. Too specific. Yeah, too many selectors. Yeah, and that, I think to this day, is the pro argument for white space significant languages is that you can, at a glance, see if you're getting crazy with your indentations. That being said, while I understand that stance, I think you can also see it even with curly braces. I guess you're not required to indent, but anybody who's not indenting their code, like, talk about death, you're dead to me.
22:39you know just just don't care don't care to collaborate with you so that code that's right or you may have a another thing coming so the indentation as advantage of white space significance is like the the scannability i get it i just think it's not such an advantage that being said i'm not of whitespace. Hater, I've enjoyed, I liked Haml quite a bit. I like how clean it looked and I appreciate Python at times as well. Although even with whitespace significant, I've seen some pretty gnarly Python code. So you can make a mess no matter where you are in the world. Just start being messy.
23:36Well, friends, Agentic Postgres is here. And it's from our friends over at Tiger Data. This is the very first database built for agents, and it's built to let you build faster. You know, a fun side note is 80 % of Claude was built with AI. Over a year ago, 25 % of Google's code was AI generated. It's safe to say that now it's probably close to 100%. Most people I talk to, most developers I talk to right now, almost all their code is being generated. That's a different world. Here's the deal. Agents are the new developers. They don't click. They don't scroll. They call. They retrieve. They parallelize.
24:12They plug in your infrastructure to places you need to perform, but your database is probably still thinking about humans only because that's kind of where Postgres is at. Tiger Data's philosophy is that when your agents need to spin up sandboxes, run migrations, query huge volumes of vector and text data, well, normal Postgres, it might choke. And so they fix that. Here's we're at right now agentic postgres delivers these three big leaps native search and retrieval instant zero copy forks and mcp server plus your cli plus a cool free tier now if this is intriguing at all head over to tiger data.com install the cli just three commands spin up an agentic postgres service and let your agents work at the speed they expect not the speed of the old way The new way, Agente Postgres, it's built for agents, is designed to elevate your developer experience and build the next big thing.
25:06Again, go to TigerData.com to learn more.
25:13You know, there's nothing like a good project that was brand new, though, that can use the original, the O-G-S-A-S-S syntax. because you didn't have to compete with old CSS to move around and support. You could just start this new world with this indented world. And until you had to copy CSS from Stack Overflow or something like that, you were pretty happy. And then you had to paste it and then do a bunch of deletion. We didn't have AI back then to automate this stuff. Gosh, that's wild to even say that. We didn't have AI back then. Yeah, the bad old days. Yeah, like, why would I write that code?
25:54It would do it for you, okay? It would do it for you. Listen, today, I took a little break. I just want to think about a feature. I just want to think about a feature. Here I am in Amp, and I'm like, hey, Amp, can we talk? Can we talk? I got an idea for the future, and I just want to think about it with you. Man, I dropped that idea in there. I'm not kidding you, dude. I got an email, went and read it, responded back, was happy. Okay, let me get back to my anthem. Let me see what they did. Feature was done. I said, let's think about it, okay? Let's talk about this. Let's not do the work. Made a bunch of changes all correct and stuff.
26:35Shipped the production and everything. Gosh, in a blink of an eye, I meant to think about it. The feature was done. What a world. What a world. That's not even a joke, man. That's not hyperbole. That's true. that was not that was not fabricated for podcast material that was straight up truth i just got a little bit concerned when you started talking to amp kind of like a marvin gay style voice you know let's talk about listening about well i was being i really was like can we just i know you're a doer okay i know you're a doer amp you just go and do stuff can we just talk about it no i'm a doer amp says i'm gonna go do this i can't plan i only do it plans well it's got the oracle comes back with good stuff but i went and got that email taken care of came back and it was done and i was like all right cool i was kind of upset because i really wanted to think about it but it wasn't necessary it's like gosh man i just want to think about that feature for a second no i can't it's done yeah no input but yeah, but was it good?
27:44It was a pretty simple feature. It didn't require a lot of thinking. I'm just trying to incrementally inch into this one because I had a whole field version of it. I will reveal to you right now what it is. I, I've been itching this scratch for a while to replace pie hole with DNS hole. I like it a lot. It's got a good ring to it. And I can't let it go. I failed the first project version of it. Just total failure. I was vibing all over the place. Slinging code, slop everywhere. Rust, rust memories, unsafe things. Just dead code everywhere. Like if you're a rustation, you're just pissed at my code.
28:28Okay. You're just slapping my code all around. Well, I learned my lesson. Okay. I just went ahead and said, that's V1. It is now a reference only project and just started off simple. and now simple so much better in fact dns simple is sitting at it is it's resolving all my dns queries as we speak on this podcast dns simple is uh sorry dns simple dns simple uh dns hole dns hole is is resolving all of my dns queries right now it is yeah that's pretty cool excited about that i have a new phenomenon when i try to start a new project now where i don't know what language it should be in anymore. Like I used to have opinions.
29:12But I do eventually resolve. So for instance, I started up this, it's like static site generator thing that does some crawling, blah, blah, blah. And I just tell it what I want. I'm just like, you know, this is a cloud code. And I'm like, you just do your thing and come back to me. And it came back to me with a Python script, you know? And I was like, well, I guess I didn't, I didn't specify. I didn't want to specify, but now I'm looking at this and I'm thinking, yeah, no, not really. and I'm like let's rewrite this in JavaScript no TypeScript please just pure JavaScript keep it clean you know keep it loose give me options no types no types do not constrain me I'm vibe coding okay that's right and so it ports it to JavaScript in a blink of an eye and I'm like that was cool and then I build out some features and I get going I realize I want this actually to run on a remote server which is a shared server so I don't have access to npm I have node there it's an older version I can run it but I can't run npm and of course this thing vibe coded up a couple of packages I think mostly around requests and stuff like that maybe like html parsing and query stuff so I'm like well that sucks and so I'm like you know what port yourself to go and then bam go and I said compile yourself to always bid on go I like Go for that reason.
30:35You just compile yourself to Go. I've got everything in one binary. I just SCP that sucker to the remote server. It's compiled against the Linux that they expect over there on my shared hosting. It even embeds the HTML templates and the CSS and everything. You embed it all in one binary, dude. So cool. One binary to see if it's all. That's how it goes right there. You either rsync or SCP that sucker anywhere you want. and just run it. No dependencies, no package managers. Now, the code is kind of, you know, verbose and ugly. Who cares? Do the tests pass? Does it work? I'm glad that you said the second part.
31:20Because I did not request any tests. Well, the thing about Cloud Code is, you know, if you give Cloud Code a task, it's going to write the task. And if you don't specify, please also write specs or whatever. If you're just like, do this thing. it's going to actually test that it does it via its own little you know shell scripts and stuff it's going to like you know output to a test directory and it's going to grep the thing and it's going to set and it's going to awk and it's going to you know count lines and whatever it's got to do to make sure that it's right and then it's going to say hey I'm done and you're like that's testing I don't have an automated test suite at the end of the day but that's right those tests are like one and done by SIA but yeah they work it's all low it's all low stakes stuff anyways you know that's what I use it for is like low stakes you know I'm not like resolving my own DNS with it or something in that case it is higher stakes yeah it is I'm yubling right now well we're up we're upstream here let's go to another project that is dead for various definitions of the word dead we aren't calling we aren't declaring death in fact I know this one still lives in a sense but it doesn't live in the way that it originally was pitched to live which was as the future of web development yes I'm talking about Meteor.js oh yeah wow remember Meteor.js often something called Meteor it was open source it was a full stack JavaScript framework came out around 2011 back in the early days of jQuery Backbone Node stuff like that initially developed by some folks at Y Combinator.
Read the full transcript
33:03Yes, this was one of the reasons why it's now being declared dead, because it was VC-backed from the start. But built by some cool devs, Jeff Schmidt, David Greenspan, he co-created Etherpad. Remember Etherpad? Ring the bell, yeah. Etherpad was one of the very first things that was collaborative editing, like Google Docs. And it was open source and self-hostable, and so people would stand it up and they would use it for their own little real-time collaborative editors inside their web apps. I think it was very cool. I'm not sure what's going on with either pad. That could probably be another story there.
33:42Matt Dibergales. I'm not sure how to say your last name, Matt. And Nick Martin. That was the team dropped huge fanfare. April 2012, largest hacker news debut of all time, according to this, probably since then. There's been larger ones, but at least at the time. It was huge. Got lots of fanfare. Lots of people trying it. Exploded in popularity. Kind of a typical hockey stick growth kind of thing. Raise more money. Raise more money. This is an MIT-licensed project that just keeps raising more money. In July 2012, they secure$11.2 million in seed funding from A16Z. They hire people. They buy infrastructure.
34:31By 2013, they release a package manager by Tom Coleman that was actually integrated into the core. There's Discover Meteor, which was either a newsletter or some sort of website co-authored by a friend of the show, Sasha Grief and Tom Coleman. Of course, you know, Sasha was big into Meteor for a long time. Really big, yeah. And, you know, things continued up and to the right. 2014 they raised$20 million Series B round and they've totaled over $31 million raised FathomDB comes out so they have a database, a cloud database Galaxy, they launched Galaxy which is like a hosting platform for media apps so that was kind of the play was like you know it's all open source and free but if you want it to be hosted by us on our Galaxy that's how you pay money and performance monitoring so they started to productize around 2013 continued to grow.
35:31I mean, the package registry had thousands of community packages, started to integrate NPM in 2015. They got worldwide production apps out there. So, I mean, not unsuccessful by any means. I call this success. For many definitions of that word, things continued to go, okay, 2016, they were making like exceeding their revenue goals according to them. But community debates arose. There was purists who loved the all-in-one simplicity. Others demanded deeper modern tooling integration. So the community started to disagree on the tech itself and the direction that it should go. They started moving towards GraphQL and that laid the groundwork for Apollo.
36:21Remember Apollo GraphQL? That's still out there, which was a spinoff. and then you know what happened basically was just like new javascript frameworks came out that were more interesting to more people and because they were like so fueled by vc money they needed to grow faster than they could grow eventually discover meteor grew outdated you know people started moving on the state of javascript survey of course is a satan grief thing he's been doing for a long time now. The state of JS actually cataloged Meteor's interest and then you can start to see the decline. And sometimes that is a what do you call it?
37:04A self-fulfilling prophecy. People start to see it declining in interest and so they are less likely to be interested in it. And just that momentum downwards can actually be a problem. And so the transparency around that actually perpetuates it. But still got worked on. And then in 2019, all of a sudden, they changed. MDG, which is the company behind it all, pivoted from Meteor to Apollo GraphQL. They saw more money in that, I think. This deprioritized Meteor's core development, frustrating people. And then in October 2019, Tiny Capital, who are owners of Dribbble and other things, acquired Meteor.js and Galaxy, that's their hosting service, assets for an undisclosed sum.
37:56So it got sold off and renamed Meteor Software. Got put into maintenance mode. I mean, more emphasizing maintenance than growth. And Tiny, which is the company that bought it, pledged they'd support it for long-term, like five years. Still out there. Still going. Yep. That's wild to think about that. They call it a renaissance. Meteor 3.0 and beyond. People still working on it. It has a small community. And so by no means dead. Legacy perhaps. The influence endures. It helped birth UJS. Apollo obviously. Other things. Storybook. But by no means did it take the world over as it was supposed to.
38:47And so in that sense, you know, the original mission of Meteor, as the future of web development. It's gone with the wind. You know, I never got on the train. I never understood it personally. It was always confusing to me. They did an interesting thing like munging server and client code early on, which of course, you know, React team has been struggling to make that a thing in the public's eyes, at least. Like they made it technically a thing, But in terms of adoption and people understanding it, it's been an uphill battle for them as well. Meteor had that from the very start. I did use it one time for a hackathon.
39:29Had a lot of fun with it. Built a game for a hackathon. And it was very strange, like, knowing am I writing server code or am I writing client code? And they were syncing stuff for you. It was very kind of advanced at the time that it was out there. had a lot of cool innovations in it maybe because of the time that I tried it but also what I tried it for to me it felt more like a toy than a tool that I would build a business around not that it necessarily was but that's just the way that it felt to me so I never took it super seriously but obviously lots of people did and they've had lots of they got 44 ,000 GitHub stars 508 ,000 installs 29 ,000 stack overflow questions So, I mean, they definitely got out there and people use it, but.
40:18Yeah. No longer as culturally relevant, surely, as it was back in the good old days. I mean, to be honest about the dead bodies in the JavaScript world is just plentiful. Yeah, that's true. Right? I mean, good luck winning that war. You know, just be happy. Even when you're winning, like two years later, all of a sudden they're like, we're just not interested anymore. Yeah, we need the new. We don't even actually, you still solve our problems. Okay, you're still good. We still don't like it anymore. Okay, we're just used to getting new things. Okay, where's the new thing? Right. That's my feeling as a front ender in the JavaScript world is just like, expect change, expect churn.
41:05And honestly, it's what tired me out of really wanting to play in that world at all. It's just like trying to keep up is basically impossible. That being said, if you look at it today, it's basically the same thing as it was five years ago. I mean, what's popular in JS land front end world today? It's React, basically. It's Next.js. You have people raging against Next.js. You have other, I mean, there's always experimentation. There's always people saying React is dead, React is this or that, but it's still just the 800 pound gorilla right now. and yeah there's been innovations along the way and alternatives along the way but it's not like there's been an upheaval you know there's this HTMX movement a return to form of multi-page apps as they call them now used to just be how you rebuilt things versus single page apps multi-page apps server side rendering full stack frameworks I think are more interesting to the JavaScript community than they ever have been.
42:10But besides from that, I mean, it's kind of been more steady in the last probably five years than it was before. I wonder if that's because of entrenchment, though. Oh, for sure. It's just too hard. There's too much sunk cost in the world of React and Next to move away from it easily. There's too much investment into the infrastructure, the usage of it. I was thinking about this recently with Git. and you make any piece of software, almost everything thinks you're using GitHub to host it. It's going to be there, and then you're going to have actions. And so CI begins with actions files, essentially.
42:52That's where your CI begins if you're starting fresh. And then everything's assumed to be around Git and GitHub. And I love Git. I think Git's great. But I just saw our friends over at Fault We're talking about the newest thing, and I'm not even sure what it's called, but there's a new thing in town to check out. Jiu-jitsu. What's it called? Jiu-jitsu. Jiu-jitsu. There you go. Which I'm not even versed in, but I'm just thinking, like, how in the world do you even – how does the world move away from at this point get? It's too entrenched. All you can do is really improve it. maybe you have some people try and use the 5 to 10 to 20 percenters they're going to try and use something different but you're just going against the current and it's just more challenging until it's not I guess slowly and then all at once that's what they say that's true slowly and then quickly slow than fast that's right that's how you get rich that's how you get poor that's how you get entrenched that's how you get disrupted so fast it is things happen in one fell swoop as they say you know that's what i heard so many swoops so meteor this is on your list meteor well angular well angular i just saw on the website okay and but meteor was on my list yeah i listened to your yeah you know is that how you spell the word meteor i don't even know m-e-t-e-o-r meteor that's how you spell meteor unless you're talking about something that has more meat in it than something else it's meteor meteor that's why i kept calling it meteor because i didn't want to accidentally say meteor like let's talk about something with more depth to it right let's get something let's get some meat on these bones in the air right let's get these meteor out here well you got another one you want to we can loop and i think it's been long enough we can loop back to quicksilver it's going to feel fresh i think it might feel fresh yeah the the pain is a little less fresh of our loss is yeah time heals all wounds i'll give it another try let's talk quicksilver people want to hear it uh take two here we go okay all right uh quicksilver if you're not familiar with this is a software from your 2003 long time ago okay that's the beginning of the internet essentially It's not actually the beginning of the internet, but it's pretty close to it.
45:21No, it's not at all. It's not at all. It's about 15 years after the beginning, maybe more. Depends on who you ask. But Quicksilver was an app launcher for Mac. At that time, OS X, not Mac OS. This is how far back it goes. A lot of people call it OS X. OS X, yes. Unless you're a Mac geek that likes Gab. That was a good one. got lost in that one you just sidelined yourself with a reference little little mac geek it's 2003 you're running mac os 10 probably like probably like lion or leopard or some sort of cat it was a big cat yes and who the heck knows which one it was but it was a kitty cat now that's right and uh quicksilver was launching your stuff man you wanted to launch things and you would go and you would go to your app directory or you would go to your doc bar and you're you're you would click the button for your your your uh your app you see it bounce you'd wait for it and that was cool no that was not cool it bounced forever no that's not cool yeah you had to do command space to conjure this new thing called a hud a heads-up display and it would give you the ability to conjure these things to happen.
46:44Apps to launch, math to be done, terminals to be opened, finder windows to be discovered is what Quicksilver gave the world. So many things. So many things. It was made in 2003 by a fellow named Nicholas Ditkoff. Made in 2003, released several versions of it, always seemed to be in beta, basically in beta for 10 years. But it was the darling. It was what launched literally the ability to have these launch bars, these launch apps to do this. It didn't win, though. It only led to innovation being done by Apple absorbing it or our friends over at LaunchBar. Yeah, absorbing it, copying it. Yeah, absorbing it.
47:33Yes, it's probably not the truth. copying the features, breaking them into the operating system. First mover advantage did not work out for them. Launch bar, Alfred, Raycast, that's what I use. Now, I did use Alfred. I'm still a semi-happy. How would I be? I'm not sure if I'm happy or not. I guess less than happy because I spent my money. I'm not using the value anymore. Owner of a lifetime license of Alfred. I'll never use it again just saying just saying if you want it I'll give it to you I mean I just don't think so I don't never say never though my buddy Justin told me that but you know I don't see it happening I don't see it happening what about Quicksilver are you ever going to go back to Quicksilver I don't even know how I don't even know where to go where would I find Quicksilver these days I think it's still a thing but I don't even know I have no idea I will say this, Quicksilver was the coolest I mean, I'm not going to say I bought a Mac because of it but it was certainly in the calculus I was like, I want a Mac because I want to use Quicksilver it was minimally attractive it was aesthetically pleasing, but it was also minimal almost invisible at times, I mean it's obviously invisible when you don't invoke it but it had a cool kind of purplish, translucent vibe to it and then the combination of things you could do like the actions you could take beyond just if it was just an app launcher then I don't think it would have been quite as popular but it had this like extensibility extensibility and like combinability that made it really powerful and you could like take a file find a file, pass it to a thing have it output something transmogrify it, I don't know capital case it and then spin it back out the other side And so the power users and the nerds, they would show you how many cool stuff you could do with Quicksilver.
49:39And that's why I wanted to run it. Now that being said, I only ever used it basically for math and for app launching, which you know to this day is what I use all my app launchers for, which is why I'm a Spotlight user. It does both those things just fine. But I wanted the power. I wanted the Quicksilver power. and so your story is basically competition why didn't it get why didn't it get better why didn't it get competed why didn't they win i think it just died in the vine i think it just uh it got there i'm not in beta it seemed to not move and so when something seems to not move and it says beta you kind of think well maybe it's not moving maybe there's no true maintenance behind this thing and so your appreciation and belief in something kind of wanes launch bar comes around seems to be newer seems to be fresher more mac native feeling same thing i think with alfred alfred is still amazing software no offense to alfred whatsoever i'm not going to use it anymore because well i moved on but i suppose i suppose if raycast died i'd probably fall back on my free lifetime license anyways we'll see you could use it again Raycast don't die well Quitsilver was open source though and these other ones aren't yeah I mean does that mean anything to you?
51:08does that not sell you on it more? or make you want to support it or use it? I think in the altruistic terms of open source of course but I'm not going to personally maintain it so the fact that it is or is not doesn't personally matter to me because I'm not doing the maintenance of it. And I'm not going to care enough to step in. It's not a problem I want to solve. That's why I'm thankful for Raycast. They've done a great job. I think Raycast is by far, they got a great free version of it. You can pay to use it as well. And it's, I think it's the best version of an app launcher. They've got a lot of cool stuff in there.
51:45And obviously they even have, I think it's like, what is it called? I don't even use it too often, but here and there, They got Raycast AI, a whole chat window. And I believe it ships free with all the free models. Now, if you actually have Raycast AI, I believe you can pay to use other models. You can swap models. You can save things. I think they could have done and should still potentially do a better job of that chat app. Like, it lives in Raycast, the launcher. So arguably, potentially the best thing they've built, a unified chat app for Mac that's Mac native is buried in somewhere you wouldn't expect.
52:31Yeah. It's like you turn over that rock, boom, gold. What's up with that? Why is the gold under the rock? It doesn't belong. There belongs in my pocket or my. On the shelf where you can see it. Yeah. I want to see the gold. Not the gold under the rock. So I don't know. Gold's pretty valuable. And Raycast is venture-backed. They could fail as a company for those reasons. I don't think they will. In fact, I haven't talked to them in a while. Yeah, but a lot of those Meteor users didn't think they were going to fail either. That's true, man. That's true. Not that you all failed, but you know what I mean.
53:03Yes. I did find Quicksilver, though, on GitHub. So it is naturally github.com slash Quicksilver slash Quicksilver. Recent commits? Recent activity? Anything going on over there? This is a bot. so I don't know for sure 5 ,909 commits total one yesterday from Trans TransFX integration bot so I'm not sure about that one in particular although on the 23rd of October there was a merge pull request pull request 3080 which was from the branch Quicksilver copy configuration build step. If you got to use Quicksilver, there it is. It's there for you waiting. And it's open source. What is it like? If you're listening to this and you do use Quicksilver to this day, let us know in the comments.
54:03We want to hear from you. Yes. Did you move it all? Did you come back? Apache 2. AV2. Are you still running macOS Lion? sorry OS 10 lion OS 10 yeah 76 issues two pull requests open not that bad it seems to be tended there's not like a thousand issues for example are you wishing you took it off your dead list no it's still dead no it's still dead it's still dead oh you guys are working on this I can't say that it's just rude I'm sorry for being rude it's just good podcast nature to say that okay don't don't If I was standing next to you in the hallway track of a great conference, I wouldn't be that rude.
54:49It's dead to me. I'm not going to use it. Can I come back? Man, absolutely. Give it a try. Raise some money. That's the way you get to prosper is raise some cash. Sounds like that's the way that you die. Maybe.
55:26Well, the last time I checked, there's only one of me, only one of you. I'd like to have more than one of me because the world expects so much from me. I can't possibly do it all. But let's be honest, that's probably a good thing. There's just one of you and one of me. But what if there was another version of you? One that already knows your projects, your notes, your team's quirks, and can actually finish the work for you. Well, that sounds like more of me, more of me time. That's what Notion's new AI agent feels like. I've been using Notion AI for a while, but the new agent is revolutionary.
56:03It's built right into Notion. Your docs, your notes, your projects, all in one connected space that just works. It's seamless, it's flexible, and you can actually have fun using it. But here's the crazy part. Your Notion agent doesn't just help you with work. It finishes it. It can do anything you can do in Notion. Write pages, organize databases, summarize projects, connect with Slack or Google Drive. It could even clean up post-meeting notes and assign tasks. It plans, it executes, and if something breaks, it just tries again. Basically, it's like delegating to another version of you that already knows how you think.
56:40Teams at OpenAI, Ramp, and Vercel, they're all using Notion Agent to send less email, cancel more meetings, and get more done. And now you can too. Try Notion today, now with Notion Agent at Notion.com slash changelog. That's all lowercase. Again, Notion.com slash changelog to try your new AI teammate today and support our show while you're at it. Love Notion. Check them out. Notion.com slash changelog.
57:14speaking of how about rethink db oh gosh man from the past slava akmachek that's right akmachet that's right whichever way you say it i'm gonna say it's right they're both right rethink was a very interesting database a scalable no sequel back in the craze of NoSQL. Database with a declarative query language for real-time apps launched in 2009 was active for probably until 2016. The company actually declared bankruptcy in 2016. The core team was disbanded. The repo was archived. I mean, this one's dead, dead. So dead. They did inspire some community forks such as ElephantDB.
58:12RethinkDB. You can go back and find that one in our archives, of course. We've had Slava Akhmachet on the show, I think, probably at the beginning of RethinkDB, and I think at the end of RethinkDB. At least two. I'm thinking two times during its heyday and one potentially on its wayday. Basia. Oh, I like that. It's a wayday. The heyday and the wayday? That's right. You're going to go on your way. Basia. be on your way now now why did everything db fail i would only speculate at this point i really don't know my speculation and this is just speculation i just think they couldn't capture market share i think mongo db was just too dominant in the no-sequel database department of the world and rethink uh just couldn't get there but didn't they write i mean now we're going deep into my brain archives because i'm starting to remember didn't they actually even write up a thing why rethink db failed and didn't we actually do an episode maybe even call why everything to be failed i'm starting to like remember something like this check out our last episode with rethink db what was called yeah i'm uh scouring the internet right now okay for information i think the long and the short of it is like no product market fit i mean that's what that's what a startup guy would say.
59:32They had some design choices that were odd. I think they, cause they had their own language. This is why when the FaunaDB people came on the show. And in fact, I think FaunaDB also at this point, can we consider that one dead? I'm not sure, but I haven't heard about it in a long time. They also created their own query language. And I remember saying like, are you sure you guys want to do that? Because it's very difficult to get people to just use your query You're like, can you have it be SQL-alike? That means that Mongo did it. So, I mean, they're all kind of following the Mongo playbook. But Mongo really did succeed where so many others failed.
1:00:11Hmm. If this is true, founder Slava Apichet said that there were two main problems. They picked a terrible market, and then they optimized the product for the wrong metrics of goodness. So they optimized for correctness, simplicity, and consistency, which are all great engineering goals, but those were not what the market valued. This is also in a day when a lot of things were happening on ABOS. A lot of databases were popping up. So we're now past a lot of this. You had CockroachDB. You had a lot of databases come out of seemingly nowhere to solve problems. Some of them open source, some of them not.
1:00:55Obviously, the ones who are not just didn't have a chance. And then ultimately, it came down to just competition AWS and adoption elsewhere. And there's a lot of motion around databases. And so you had a lot of choice. Yeah, there was a thriving market of offerings. Now we just want Postgres, right? Postgres. Postgres for life, man. Why not? you know why would you choose anything else than postgres i just don't know they were eventually acquired by the linux foundation the cncf a few months after the shutdown in 2016 and it continues to be an open source project to this day but i don't know who's using it i don't i don't know what doesn't everything continue to be an open source project to this day though i mean it's not like the source goes away otherwise it's like you could say that about anything that's dead is this i want to know if this is claude trying to get get into my good graces considering what i just said a little bit ago about amp at the very end it says why is that fun fact i see one of the discussions mentioned an episode from the changelog about rethink db you folks have quite the archive come on claude it told you that that's what it said do you have that in your ClaudeMD like, by the way, I host the ChangeLog podcast.
1:02:20We have quite the archive. I think it knows. It knows who I am. Yeah, it's definitely pandering to me because it's like, yo, great job. That is pandering. Yes. But it worked. Did it work? You do prefer Claude now to AMP. So fauna.com actually doesn't go anywhere, which was the location of FaunaDB. F-A-U-N-A dot com. it's either my block list, DNS hole, or it's dead. Mine redirected to Fauna Robotics, which is a different company. Yeah, I'm using Safari, so mine don't redirect, man. Safari does its own thing, okay? It really does. Let me go into Chrome. What does Chrome do? Yeah, faunadb.org is what you're looking for.
1:03:08Ah, okay. It's a strongly consistent OLTV database with a hybrid, blah, blah, blah. open source project is still very early stage. Yeah, you're probably looking at... It used to be.com. Well, you're probably talking about the company, and I'm talking about the open source. And the company might be gone, but the project's still open source because they all are, right? Fonadb, last commit to the Fonadb repo was six months ago. Oh, and the only commit was all six months ago. So I think they open sourced it and moved on. yeah they're like listen crunch the history put it out there cash the no don't cash the check that that'll bounce and get out of here just get out of here it's over we we didn't do it that's right i mean they had some really good ambition though i mean i remember that conversation really smart guy the cto was i recall no offense to him but i recall him just being a little just monotone.
1:04:10Monotone, he was. Right? Very monotone. Yeah. And I think he left months after our conversation. I don't know. Some things are meant to live and some things are meant to die.
1:04:26That's very final. If we keep going, I'll just keep making stuff up, okay? I'll just keep making it up. Well, should we keep going or should we call it? We do have a couple of things. uh just quick mentions icq oh gosh remember icq oh yeah let's do a little leave it list leave it list yeah like icq is cool man for sure and you were cool if you had a low icq number yeah you used to be able to buy the numbers off of ebay and stuff too did you know that probably still can probably can i was not that cool i came way late to icq in fact i got you i used it because someone made me use it you know sometimes people are talking like yeah we use this i'm like dang it i have to install a new app but i did have um there was a open source project that actually combined a bunch of chat messengers of which icq was one aim yeah um others i think it was called pigeon yeah i recall pigeon yeah our game g-a-i-m game it was a bird there was a bird one Is it the pigeon one you think?
1:05:35Yeah, pigeon was a bird. It also means like it's like a. It's spelled not like the bird, but like the language feature. I think a pigeon language is like a language that like multiple people use like as a crossover. Let me Google that instead of just talking out my butt. While you're doing that, there's a Reddit post one year ago. So this is actually 28 years, not 27 as I read it. So it says after 27 years, ICQ is officially shutting down today. Yeah. End of an era for one of the first messaging apps. So 20 years ago. Okay, so Pidgin at P-I-D-G-I-N dot I am also dead. Last modified in 2020. Is a chat program that which lets you log into accounts on multiple chat networks simultaneously.
1:06:29XMPP, IRC, Bonjour. Simple, Silk, Sephir. I mean, tons of these I've never heard of. Same time. I thought there was an ICQ. Oh, and then that's a Windows, Linux, and other units like Client. On macOS, try Adium. Do you remember Adium? That's what I was talking about. Yeah, the pigeon. I was thinking Adium. That's the bird, Adium. Yeah, I used that one. Yep, Jabber. Oh, yeah. Google Talk. Remember Gtalk? Yeah. Google probably also killed Gtalk. There's still some chat up in there. ADM is also open source. Gchat. Let's see. Latest release of ADM runs on Mac OS X. Mac OS X. 10.7.5 or newer. So this is also dead.
1:07:20Man. All this dead stuff. But I mean, these guys, it's because, you know, this audience they serve is gone. I mean, who needs to connect to these different chat apps nowadays? Nobody. Last commit here was like four years ago. So we're finding all kinds of dead projects as we just talk. To go back to the word pigeon, P-I-D-G-I-N is a grammatically simplified form of a contact language that develops between two or more groups of people that do not have a language in common. that's a great name then for a program that does what it did yeah and so if you speak you know Swahili and I speak English and we don't have a crossover language we would develop between our people groups this third simpler language so we could actually communicate we call that a pigeon language interesting very interesting so ICQ was rad ICQ was gone Skype was cool for a minute dude skype was crucial it really was a lot of good days on skype and now it's gone i assume microsoft still ship new versions of skype it's dead man who cares long with teams it's irrelevant oh yeah i would never use i'll never use teams personally what are non-microsoft people using i guess discord for voice it's probably discord at this point even real time like i guess zoom won that.
1:08:53For a while, it was Skype. You would Skype somebody. You would never Zoom somebody. Right. Then we would WebEx. Ugh, gosh. I almost punched my screen just now, dude. It was a bad situation. I almost needed a new back book. It was almost a situation here. You say WebEx, and that's worse than Rochambeau. You know, like, it's like, yeah. WebEx is just nasty nasty man you know I do miss the fact that is gosh I'm just like brain farting not ICQ IRC is IRC still a thing yeah I mean it's as niche as ever I think it had a moment when people were interested in it but then like Freenode freaked out I can't remember what happened with Freenode but like people that were running Freenode ended up being weirdos or something somebody can fill us back in on that and IRC just never had a chance in that way.
1:09:53It's a shame because there's a lot of people who found their love for the thing they do on a mail list or some sort of what were the original chat rooms called? They were like PDP hubs or something like that. I don't know what they were called. I'm not even from that era, but I kind of missed the days I didn't take a part in it. Just when it was simpler. Now everything's commercialized. If I can't make money doing this, it doesn't belong, you know? And that's just kind of sad, man. You know, it really is. I think you should scratch your own itches. That's just, you know, I'm just scratching itches.
1:10:34I got it. That's all. You know, it's a pretty wild world up there these days. You know, one thing I was taking note of when I was looking at Wikipedia for Quicksilver was how cool that logo was, man. that's what made quicksilver cool it had a lot of cool things initially yeah the cool hud the cool logo the colors the new thing it just doesn't work out sometimes and if you go to meteors as i said to meteor meteor software on youtube they're thriving like one month ago 135 views seriously I mean four months ago 3x faster builds 409 views they're thriving on there they're just busting it up putting their content out there so should I take it back no they're dead they're dead man that was me being politely facetious you know what I think is dead I think this episode is dead you know folks I'm just really sad for you because the version one was better.
1:11:48Perfect software. It was, man. It was good stuff. You know, and I think we, like, we did a good job with this episode, but I feel like we kind of botched it. Well, we botched it when we didn't hit the record button, you know. The rest of the time we've been kind of just... Regretulately here just podcasting. It's like, we gotta be here now. You know, we've just kind of been coping. Yeah, it's been hard. So I guess, you know, sorry. But also, you're welcome. yeah you know it is what it is as they say in closing i do want to say one thing okay off the you know off the the thread we're in there but i did mention amp and i do want to say that amp is free you see this jared ampcode.com i did see this this is interesting amp is free but free as in how free as in you're the product again okay they're gonna advertise to you he just went Straight backwards on this thing.
1:12:44You're the product again. Yeah. They're going to sell your eyeballs. That being said, though, I don't know what they're tracking. So I can't say that for sure. But it's the first that I'm aware of where you can use a, I've said it before, my favorite AI agent, coding agent, for free. And I've hit limits with it. So I think it's a couple hours. I don't know what the actual limit is, but after a bit, they're like, listen, we've only got six advertisers. You've seen them all. And the way it works is they show you ads in the terminal, right? Right above. So you have your prompt area. Then you have the chat area.
1:13:23That's been what's been going by. And right between those two, perfectly sandwiched. I think they've done a great job with UI on this, too. Is this subtle text-based ad? It's not even a bother, honestly. and I've actually enjoyed them. I'm like, oh, sweet. They're doing that? Cool. Nice. I find myself actually wanting to see the ads. It doesn't bother me. I mean, you're getting what you, you're opting into this free thing with like, it's all straightforward the way it works, right? So if you need to use it for free and you're okay with that supported, like, I think it's a great option. So I would say there's no shame in that game whatsoever.
1:14:04You know? If you wanted to deep think for you well ask nicely okay because it's probably gonna do it it's like there ain't no thing in here we just do around here if the whole time it's deep thinking it could it show you like a video ad like like that'd be kind of cool like turn it into askinima style like in your terminal watch those here's star wars asky star wars no not star wars that's not an ad has to be like like dawn soap or something you know like even worse all they need to do is take typical advertisements like tv commercials and they need to turn them into ask cinema with some sort of software program and feed those into your terminal that'd be sweet there's there's a dog that hunts there i think maybe but i don't know talk to our friends at sourcecraft and at very least get a changelog ad up in there you know like hey while you're sitting here waiting for this thing to go Why don't you listen to the changelog, dudes?
1:15:05So my prescription, though, for people is this. It's like, don't sleep on this free. It doesn't have to be your daily driver. But what about free docs? Who wants some free docs? Because this thing will just wind up and do whatever you want for a couple hours, unfettered, every day. So you basically have two to three hours per day of AMP code that you can just use. It still has the Oracle. It still has everything else that it has. there's nothing different about it than I can tell. It seems just as smart, just as able. And get yourself some free documentation, maybe some free thinking, some deep thinking, have it write some tests for you, stuff you don't really want to do and maybe you're not going to do.
1:15:47Maybe do a code review for you every day for free. Boom. You're wasting it. It's like free labor just sitting there. Scoop it up. Take it. All right. Well, thank you for hanging out with us. Yes. Friends. Thank you so much. Remind me. Is this our spooky episode? Spooky, man. This was spooky. Was it a little spooky? Well, you were acting a little spooky there. You're like, dead is dead. Oh, I did get it. I was just trying to lean into it. Okay. Trying to play a role here. You know, do my job. You get the Sixth Sense, you know, I see dead projects up in there. That's right. That got probably cut before we started hitting record.
1:16:34Yeah, you might have it, though. Let's say goodbye, friends. I think you did say it twice, though, so that's cool, though. Oh, good. Enjoy your Halloween. Eat lots of candy. Brush your teeth. And support open source. Stay spooky. Bye, friends. Stay spooky.
1:16:52Oh, my gosh. We recorded about 48 minutes of absolute gold. Jared and I were having a ball. We were just really in a good groove, riffing, having fun. And then Jared realized that we did not push record. Yeah, we've been doing this for a long time, but still yet, somehow, someway, we didn't push the button. And that's not cool. Now, I do believe that Riverside could have saved us. Hear me out. If you're in a Riverside session where you normally record for a long period of time and you're talking and the record button has not been pressed, You probably should change the interface or do something to let people know.
1:17:32More clarity. The whole point of Riverside is to record. And we laid down gold. And you missed it. And we did too because, hey, that's how it works. Anyways, it's Halloween. I gotta go. We got costumes. We got crazy. It's literally Halloween right now. I'm leaving. I'm going to be spooky. Go out with my kids. Have some fun. And you should too. Stay spooky, y 'all. We love you. Enjoy Halloween. Thank you.
1:18:28Thank you.
From the publisher
It's a FRIGHT...when your record a podcast with dead projects all around. Tech debt, poor choices, timing, market shift, and optimizing for the wrong things are all lurking around waiting to pop out at you! Just don't forget to push record.

