Interview with Jeff Geerling

A Raspberry Pi blog interview with a prominent open source and hardware creator prompts widespread praise for his calm, technically rigorous videos, influential Ansible and Raspberry Pi work, and openness about living with Crohn’s disease. Commenters also debate how much a creator’s past religious writing or strong views on corporate open source licensing (such as the Red Hat–CentOS fallout) should affect trust in their technical content, as well as the broader responsibility that high-profile technologists have when shaping online sentiment.

Overall reception of the creator and content style

  • Many commenters describe the creator’s videos and writing as calm, positive, and “wholesome,” in contrast to high-energy, clickbait, or outrage-driven content.
  • The production quality and clarity are praised; people liken the tone to educational TV from childhood.
  • Several note a long history with the creator’s work: from early Drupal and Ansible material to Raspberry Pi content and books.
  • The creator is seen as humble, approachable, and resilient in the face of serious health issues.

Religious/personal-blog content and “separating art from artist”

  • Some express discomfort with older, strongly religious and abortion-related posts mixed into an otherwise technical blog.
  • Others defend the right to post personal beliefs on a personal site and argue that disagreement on controversial issues is compatible with a tolerant society.
  • The creator explains the blog dates back to high school/college, intentionally leaves old posts and early videos online to show growth, and acknowledges they wouldn’t be written the same way today.
  • There is brief meta-debate about when a creator’s non-technical views should matter for evaluating their technical work.

Red Hat / CentOS / Rocky / Alma dispute

  • One side argues criticism of Red Hat was overblown, factually wrong, and helped fuel an online “hate bandwagon”; they characterize Rocky/Alma as “freeloaders” reselling long-term support without contributing work, and say Red Hat’s changes didn’t harm the broader community.
  • The other side counters that CentOS was widely used as a RHEL-compatible platform; mid-lifecycle changes to CentOS 8 and later source restrictions disrupted users and broke long-standing expectations.
  • Some ex-employees and community members assert this reflects post-acquisition corporate behavior, and see attempts to constrain redistribution of GPLed sources as contrary to open-source norms.
  • Others maintain the creator’s coverage was measured, not hateful; critics of the creator are seen as exaggerating.

Impact on viewers and learners

  • Multiple people credit the creator with inspiring them to learn Ansible, compile kernels, build Raspberry Pi clusters, and even start ambitious projects like a custom search engine.
  • The content is viewed as unusually accessible and confidence-building.

Health and personal openness

  • The creator’s openness about living with Crohn’s disease is widely appreciated; commenters say it raises awareness and provides solidarity for others with the condition.

Platform and UX meta-discussion

  • Commenters praise the Raspberry Pi site for a clean layout but complain about cookie popups; some argue these are only legally required given certain tracking practices.
  • HN’s automatic title-editing feature is heavily debated: some call it a harmful “anti-feature” that produced an ominous, obituary-like title, while others say it quietly fixes many titles and is net positive since submitters can override it.

Tool/battery ecosystem and “lock-in” analogy

  • The creator’s analogy between brand lock-in for tools and tech ecosystems sparks discussion about proprietary battery standards.
  • Commenters share experiences with changing battery formats, adapters, and brand ecosystems, and some wish for standardized or shared battery systems like existing multi-brand alliances.

Open source vs “source available” terminology

  • There is agreement that licenses like BSL should not be marketed as “open source”; calling such models open source is seen as misleading and against community expectations.