Codetown ::: a software developer's community
Mycroft developer Ryan Sipes, speaking from the show floor of this year's OSCON in Austin, Texas...
(see our video interview here), says that what started out as a weekend project to use voice input and some light AI to locate misplaced tools in a makerspace morphed into a much more ambitious, and successfully crowd-funded, project -- hosted at the Lawrence Center for Entrepreneurship in Lawrence, Kansas -- when he and his fellow developers realized that the state of speech recognition and interfaces to exploit it were in a much more rudimentary state than they initially assumed.
How ambitious? Mycroft bills itself as "an open hardware artificial intelligence platform"; the goal is to allow you to "interact with everything in your house, and interact with all your data, through your voice." That's a familiar aim of late, but mostly from a shortlist of the biggest names in technology. Apple's Siri is exclusive to (and helps sell) Apple hardware; Google's voice interface likewise sells Android phones and tablets, and helps round out Google's apps-and-interfaces-for-everything approach. Amazon and Microsoft have poured resources into voice recognition systems, too -- Amazon's Echo, running the company's Alexa voice service, is probably the most direct parallel to the Mycroft system that was on display at OSCON, in that it provides a dedicated box loaded with mics and a speaker system for 2-way voice interaction.
The Mycroft system, though, is based on two of the first names in open hardware -- Raspberry Pi and Arduino -- and it's meant to be and stay open; all of its software is released under GPL v3. The initial hardware for Mycroft includes RCA ports, as well as an ethernet jack, 4 USB ports, HDMI, and dozens of addressable LEDs that form Mycroft's "face." That HDMI output might not be immediately useful, but Sipes points out that the the hardware is powerful enough to play Netflix films, or multimedia software like Kodi, and to control them by voice. Unusually for a consumer device, even one aimed at hardware hackers, Mycroft also includes an accessible ribbon-cable port, for users who'd like to hook up a camera or some other peripheral. Two other "ports" (of a sort) might appeal to just those kind of users, too: if you pop out the plugs emblazoned with the OSI Open Hardware logo, two holes on each side of Mycroft's case facilitate adding it to a robot body or other mounting system.
The open-source difference in Mycroft isn't just in the hacker-friendly hardware. The real star of the show is the software (Despite the hardware on offer, "We're a software company," says Sipes), and that's proudly open as well. The Python-based project is drawing on, and creating, open source back-end tools, but not tied to any particular back-end for interpreting or acting on the voice input it receives. The team has open sourced several tools so far: the Adapt intent parser, text-to-speech engine Mimic (based on a fork of CMU's Flite), and open speech-to-text engine OpenSTT.
The commercial projects named above (Siri, et al) may offer various degrees of privacy or extensibility, but ultimately they all come from "large companies that work really hard to mine your data" and to keep each user in a silo, says Sipes. By contrast, "We're like Switzerland." With Mycroft the speech recognition and speech synthesis tools are swappable, and there's an active dev community adding new voice-activated capabilities ("skills") to the system.
And if you can program Python, your idea could be next.
Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.
Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.
Check out the Codetown Jobs group.

Pinterest Engineering cut Apache Spark out-of-memory failures by 96% using improved observability, configuration tuning, and automatic memory retries. Staged rollout, dashboards, and proactive memory adjustments stabilized data pipelines, reduced manual intervention, and lowered operational overhead across tens of thousands of daily jobs.
By Leela Kumili
Franka Passing discusses the architectural shift of Duolingo’s 500+ backend services to Kubernetes. She explains the move toward GitOps with Argo CD, the transition to IPv6-only pods, and the "cellular architecture" used to isolate environments. She shares "reports from the trenches" on managing developer trust, navigating AWS rate limits, and productionizing early adopter services.
By Franka Passing
How can you focus in a sea of results from a large regression test suite? This article describes a stochastic approach that relies on some degree of redundancy in your CI regression test set. This approach does not guarantee you will catch every bug every time, but it gives you your best bet of not missing the subtle signatures of all the bugs uncovered by your CI regression test suite runs.
By James Bornefelt WestfallIn this episode, Thomas Betts and Adi Polak talk about the need for context engineering when interacting with LLMs and designing agentic systems. Prompt engineering techniques work with a stateless approach, while context engineering allows AI systems to be stateful.
By Adi Polak
A 600-run benchmark by Ruby committer Yusuke Endoh tested Claude Code across 13 languages, implementing a simplified Git. Ruby, Python, and JavaScript were the fastest and cheapest, at $0.36- $0.39 per run. Statistically typed languages cost 1.4-2.6x more. Adding type checkers to dynamic languages imposed 1.6-3.2x slowdowns. Full dataset available on GitHub.
By Steef-Jan Wiggers
© 2026 Created by Michael Levin.
Powered by
You need to be a member of Codetown to add comments!
Join Codetown