Microsoft killed FoxPro in 2007. Anyway, here's FoxPro revived
A new project has revived the discontinued FoxPro programming language by implementing a modern compiler and runtime. The system utilizes Rust and WebAssembly to create a portable bytecode interpreter that runs on various platforms. This architecture ensures that the editor's validation logic remains perfectly synchronized with the runtime execution behavior.
- ▪Microsoft discontinued FoxPro in 2007, but a new initiative has successfully revived the language.
- ▪The revival employs a compiler and bytecode interpreter written in Rust and compiled to WebAssembly.
- ▪The runtime uses a fiber-based model to handle asynchronous operations without blocking the main thread.
- ▪The editor validates code using the same compiler as the runtime to prevent discrepancies between development and execution.
Hacker News (Front Page) files mainly under programming. We currently carry 2,022 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Foxscript |
| Canonical URL | https://foxscript.org/ |
| Publication time | Tue, 22 Sep 2026 21:00:30 +0000 |
| Retrieval time | 2026-09-22T21:28:57.810Z |
| Last seen | 2026-09-22T21:28:57.810Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 1cP_vpPaPlmB · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
The virtual machineA compiler, and a machine built to run what it makesVisual FoxPro compiled your program to p-code and shipped a runtime to execute it. This is the same arrangement, made again: a compiler and a bytecode interpreter written in Rust and compiled to WebAssembly, so one machine runs your code wherever the application runs. The editor checks what you type through that very compiler, so what it underlines and what the runtime refuses cannot drift apart.A running program is a fiber. When it needs something from the world outside (a message box, a modal form, the next record) it does not call out and block; it yields, the work is done while the machine is off the stack, and the answer is handed back.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Foxscript.
Discussion
0 commentsMore from Foxscript
