text stringlengths 0 2.68k |
|---|
**Ewelina Kurtys:** Actually, we aim for general computing. But of course, not everything. By looking at the human brain and also thinking about what is done now in digital, we think that every -- maybe not every, but many tasks which are done by artificial neural networks will be much better to be done on biological n... |
**Adam Stacoviak:** Really? Okay. So maybe that's the first place where -- because we've started off talking about our energy crisis that is obvious; that seems to be the obvious reason why biocomputing is the platform... It's potentially a lot less required energy usage. |
**Ewelina Kurtys:** Absolutely. |
**Adam Stacoviak:** And so you're going general. |
**Ewelina Kurtys:** Yes, yes. We go for general computing, which will be much, much cheaper, and very competitive to digital. |
**Jerod Santo:** Are any of your customers well-capitalized evil geniuses who just want to electrocute some neurons because they're just enjoying... |
**Adam Stacoviak:** Gru. Maybe Gru is -- |
**Jerod Santo:** Like a Doofenshmirtz, or maybe like a Moriarty... Any Moriartys? I'm just messing with you, Ewelina. I've just run out of actual questions... Adam, anything else for her? I mean, this is interesting stuff. I think we're definitely -- a lot of work to be done. |
**Adam Stacoviak:** Yeah, I think it's really about the -- I was just thinking like where could it be used, where do you see it being used... I'm surprised at general, because it seems like it's -- that's the long road. Like, the short-term road would be specialized use cases, where you can control the environment, hav... |
**Ewelina Kurtys:** No. Actually, we aim for general computing. We think general computing could be a real revolution. |
**Adam Stacoviak:** Post-silicon, Jerod. Post-silicon. |
**Jerod Santo:** Biocomputing human neurons. |
**Adam Stacoviak:** Wow. I'm looking forward to it. I can't wait to see what happens next. I'm so surprised by what's happening today... |
**Jerod Santo:** Yeah, I had no idea. |
**Adam Stacoviak:** ...let alone what the future may hold from this. So cool. |
**Jerod Santo:** Thanks, Ewelina. Thanks for coming on the show and telling us all about it. |
**Ewelina Kurtys:** Thank you so much for the nice questions and nice discussion. |
• Ellie Huxtable discusses her move to San Francisco and her motorcycle |
• Ellie explains how she uses Atuin, a tool she has been working on, and its features |
• Atuin Desktop is introduced as a runbook editor and an extension of the CLI |
• Ellie discusses the transition from working full-time jobs to focusing on open-source development |
• Atuin Desktop's features and functionality are described in detail, including its Tauri app and Blocknote editor |
• Custom blocks for editing and syncing runbooks |
• Atuin's hub for collaborative editing and automatic syncing |
• Rust-based runtime for executing runbooks |
• Long-term vision of making automation more accessible and flexible |
• Runbooks can perform sequential tasks, database operations, and local development tasks |
• Challenges of environment differences and potential solutions through containerization |
• Discussion of container integration and contextual blocks |
• Brief tangent on the decline of Apple's excitement and the rise of Linux as a development platform |
• Ellie Huxtable's experience with Arch on a MacBook in 2015 and the ease of use of the current project |
• Challenges of working with the CLI, including database migrations and mistakes lingering over time |
• Challenges of working with the desktop app, including inconsistent graphical environments and varying performance across different systems |
• Comparison between the CLI and desktop app, and how they solve similar problems but in different ways |
• Decision to create a separate desktop app, including the ability to do things that can't be easily done in a TUI |
• Using Tauri as a platform, including its development experience, resource usage, and performance issues on Linux |
• Ellie Huxtable's positive experience with Rust on the backend, allowing for faster performance |
• Reception to Atuin CLI, with universally positive feedback |
• Ellie Huxtable's thoughts on monetizing her open-source project, considering the cost of infrastructure and the potential for a low-income stream |
• The distinction between open-source for personal use and commercial use, with Ellie arguing that commercial use should be closed-source or licensed separately |
• The potential for the desktop app to be more successful in a business setting than the CLI, with a stronger use case for organization collaboration |
• The trade-off between supporting self-hosting and open-sourcing the desktop app, with Ellie expressing concerns about the complexity of supporting custom installations |
• Monetization options, including GitHub Sponsors and hosted sync, with Ellie hesitant to introduce a paid model due to the potential for changing the project's dynamics |
• "Pay what you want" pricing model discussed |
• Open-source software monetization strategies, with a focus on companies paying rather than individuals |
• Desktop app release and reception, including opt-in telemetry and community response |
• Atuin desktop release features and functionality, including runbooks and executable blocks |
• Interaction with terminals and scripts, including block and wait functionality and output capture |
• Creation of a shared hub for users to share and access runbooks and blocks |
• Current limitations of the hub, including only allowing sharing of runbooks and requiring an online workspace |
• Plans to allow sharing of blocks and accessing others' blocks through the hub |
• Importance of portability and ease of use, even if the company or GitHub repo disappears |
• Future plans to switch from YAML to Markdown as the file format |
• Development of a new runtime for running runbooks from the CLI and in CI systems |
• The new runtime's goal of making the frontend minimal and allowing for more flexibility in block definitions |
• Plans for users to be able to write their own blocks and integrations |
• Current status of the project as open source, with plans for open contribution |
• Open contribution process, accepting fixes and features from anyone |
• Feature request process, preferring issues before pull requests to avoid wasting effort |
• Roadmap for the project, to be created soon and made public on GitHub issues |
• CLI tool status, mostly mature but with some major feature requests and bug fixes needed |
• Forum and blog usage, with GitHub issues and Discourse forum being primary discussion places |
• Managing feature requests and user feedback, with a need to improve organization and communication |
• Feedback on the tool's user experience and usability |
• Comparison of the CLI and runbooks app usage cases and depth |
• Discussion of the tool's target audience and users' needs |
• Update on the tool's website and availability |
• Invitation to explore and contribute to the open-source codebase |
• Closing comments and appreciation for the conversation |
**Jerod Santo:** Well, I am joined once again by Ellie Huxtable with Atuin, which has been making my shell magical for years now... Ellie, welcome back to The Changelog. |
**Ellie Huxtable:** Hi, great to be here. |
**Jerod Santo:** Great to have you. You sound closer. You were so far away last time... I think we had a schedule around our different time zones... But now you're in the States. What happened? What changed? |
**Ellie Huxtable:** I moved to San Francisco. That's been very recent, just like a month ago, but it's been good so far. |
**Jerod Santo:** Good so far. And where were you before? Somewhere in the UK, right? |
**Ellie Huxtable:** I was in London. |
**Jerod Santo:** In London. Okay. And you were often on a motorcycle, I remember that part... |
**Ellie Huxtable:** All the time, yeah. Still am. I bought one like four days after moving here, so... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.