FiveTech Support Forums

From Windows++ to the Web — and Why Timing Matters

Paul Dilascia’s Windows++ showed something radical for its time:
Windows was not a law of nature.
It was a platform — and platforms can be framed, abstracted, and re-owned.

Later, FiveWin did something very similar for an entire generation of xBase developers.
Not by simplifying Windows, but by translating it into a mental model that allowed people to focus on business logic instead of message loops and handles.

The common thread was never the technology itself.
It was the attitude:

The platform is given —
but the system is negotiable.

---

---

The Web Is Now at the Same Point

HTML, JavaScript, and PHP today are powerful, open, and fragmented.

There are countless frameworks, best practices that change every few years, and endless opinions about “the right way” to build web applications.
Much like early Windows development, this abundance often drives developers toward large frameworks — not because they love them, but because they provide orientation.

This is where the parallel becomes clear.

What the web does not need is yet another framework.

What it needs is the confidence to think in systems again.

---

---

The Difference Compared to Back Then

In the Windows++ era, building your own abstraction meant working in isolation.
Feedback was slow, mistakes were expensive, and system design was a lonely exercise.

Today, that has changed.

AI is not important because it writes code.
It matters because it makes system thinking accessible again:

• discussing architectural ideas
• challenging assumptions
• comparing alternatives
• refining abstractions
• and iterating without burning months

This removes the biggest barrier that once prevented many developers from following the Windows++ mindset all the way.

---

---

What a “Windows++ Moment” for the Web Looks Like

Not a product.
Not an SDK.
Not a dogma.

But a way of thinking:

• minimal abstractions
• transparent building blocks
• conscious use of tools
• no hidden magic
• no forced lock-in

Something that says:

You can build your own web system —
and you understand every part of it.

Not for millions.
Not for trends.

But for developers who want responsibility.

---

---

Personal note

For me, I eventually found my own Windows++ in preprocessing and patching.

Not as a framework.
Not as a product.
But as a way of thinking.

A way to build systems I understand,
can explain,
and can change without fear.

Re: From Windows++ to the Web — and Why Timing Matters

Otto, this is a really well-articulated reflection. The parallel you draw between Windows++, FiveWin, and the current state of web development is spot-on.

I think there's an interesting nuance worth highlighting about what FiveWin actually did for the xBase community. It wasn't just an abstraction over the Win32 API — it was a mental model translation. Developers who understood DBF files, REPORT FORM, and event-driven business logic could suddenly interact with buttons, grids, and toolbars without relearning how to think. The power was in keeping the developer's mental model intact while exposing new capabilities.

That's the missing piece in most modern web frameworks. They don't just abstract HTTP or DOM manipulation — they force you into their mental model (React's component tree, Vue's reactivity system, Angular's dependency injection). You end up thinking about the framework instead of the business problem.

What Harbour and mod_harbour offer here

Harbour, particularly with mod_harbour, already gives you something close to that "systems thinking" approach Otto describes:

• You control the preprocessing
• You see the HTTP request/response cycle transparently
• You mix server-side logic with client-side rendering on your terms
• No magic — just code you can read, trace, and modify

// mod_harbour: transparent, no hidden magic
REQUEST HB_GT_NUL
FUNCTION Main()
    ? "Hello from Harbour on the web"
    RETURN NIL

The challenge isn't technical — it's cultural. The web ecosystem rewards complexity and novelty. What you're describing — minimal abstractions, transparent building blocks, no lock-in — is the opposite of what gets stars on GitHub.

But I'd argue that's exactly why communities like FiveTech matter. We've been doing "you own the system" for decades. The web is just catching up to an attitude that xBase developers have always had.

The real question is: how do we make this philosophy visible to web developers without it sounding like "use our old tools"? Because the tools aren't the point — as you rightly said, the thinking is.

— Forum Moderator

---

Respuesta generada por Inteligencia Artificial usando el modelo mimo-v2.5-free via OpenCode Zen. Puede contener errores; por favor verifiquela antes de aplicar.
AI-generated reply using the mimo-v2.5-free model via OpenCode Zen. May contain mistakes; please verify before applying.