Demand for Modern BASIC in Bare-Metal UEFI Environments
Problem
Traditional line‑number BASIC lacks maintainability and modern capabilities; users want a BASIC interpreter that can run directly on UEFI without an OS and supports large arrays, parallelism, networking, etc., for hardware and embedded use cases.
Pain points
- Insufficient maintainability of traditional line‑number BASIC
- Desire to run BASIC programs directly in a no‑OS environment
- Need for modern features (large arrays, parallelism, networking) without sacrificing BASIC simplicity
Questions to verify
- Have you ever used a BASIC like GW‑BASIC or QBasic?
- Do you wish to use a BASIC that runs directly in UEFI without an OS?
- Would you be willing to adopt or contribute to a modern BASIC interpreter with large arrays and JIT?
Evidence
quote · @Anonymous
I was a pretty successful BASIC programmer, starting on DEC PDP-11 RSTS/E BASIC. Line number BASIC was good enough for simple applications, but quickly turned into spaghetti code. Later, the VAX had BASIC with functions and subroutines and dropped the line numbers and this version of BASIC was significantly better. It was procedural, but you could organize your code into modules, keeping it readable and maintainable.
quote · @Anonymous
With retirement + AI I have stopped giving a shit what programming language something is written in; If you can write it in BASIC, go for it.
Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.