BeeBase, a programmable relational database with graphical user interface

Overview & Positioning

  • Presented as a small, programmable desktop database for hobbyists, somewhat like a mini-Access/FileMaker with a Lisp-like scripting language.
  • Core appeal: cross-platform (Windows, Mac, Linux, Amiga), nostalgic Amiga support, and a GUI-based RAD-style database builder.
  • Some commenters are excited by the “retro” feel and the fact it grew from work started in 1994.

User Experience & Onboarding

  • Positive reactions to the general look, but several ask for better onboarding:
    • A prominent “Get Started” button on the homepage.
    • A simpler, more visual tutorial (images/GIFs) instead of dense text.
  • One comment notes the UI shows many rows on a small screen, hinting that layout/density could be improved.

Error Messages, Naming Rules & Community Expectations

  • A user hits “Invalid name” when creating a table called users; later finds table names must start with uppercase ASCII letters.
  • Criticism that the error message should specify the rule; relying on page 8 of the manual is seen as poor UX.
  • Counter-arguments:
    • Many databases (e.g., SQL systems) also have cryptic error messages; some expect users to read manuals.
    • For a niche, script-heavy tool, learning quirks via manual and trial/error is considered acceptable.
  • Meta-discussion about tone:
    • Some interpret “it’s in the manual” responses as dismissive or user-hostile.
    • Others see this as blunt but normal for free OSS; debate over how much developers “owe” users.
  • Restriction to ASCII/uppercase names is criticized (e.g., inability to use non-Latin names).

Data Storage & Technical Notes

  • BeeBase project files use SQLite3 format.
  • You can:
    • Export/import via an official facility (per docs).
    • Open and modify the file directly with other SQLite tools, but only if you follow BeeBase-specific rules (detailed in the manual).

Scripting Language

  • The embedded language is a homegrown Lisp dialect.
  • Syntax and some core functions resemble Common Lisp, but it is much smaller and specialized for database programming and GUI control.

Comparisons & Alternatives

  • Compared to MS Access, FileMaker, LibreOffice Base, Lotus Agenda, Notion, Airtable, and SharePoint/PowerBI ecosystems.
  • Some feel the whole category of desktop RAD databases has declined; modern users often prefer multi-user web tools.
  • One person wonders if BeeBase could replace Access at work, but is unsure whether its scripting can match VBA for tasks like manipulating XLSX.

Desktop vs Web & Multi-User Access

  • Discussion that multi-user expectations have “killed” many desktop database tools:
    • Web stacks provide multi-user infrastructure more naturally.
    • Desktop apps can use HTTP/gRPC backends, but then you’re effectively also building a web-style server.
  • Some users want personal databases with mobile access and data sovereignty; suggestions include nuBuilder, direct SQLite + GUI clients, and PHPMyAdmin.