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.