Comment Back to Simplicity: Why OpenEdge SpeedScript and htmx Feel Like a Breath of Fresh Air

[JamesBowen]

For the last decade, web development has increasingly gravitated toward highly sophisticated JavaScript frameworks. React, Angular, Vue, Next.js, state management libraries, build pipelines, transpires, dependency managers, and complex front-end architectures have become standard components of modern application development.​

While these tools undoubtedly solve real problems, many developers building business applications are left wondering a simple question:

Do we really need all of this complexity?

For organisations developing traditional line-of-business applications, most screens ultimately perform a familiar set of tasks: Create, Read, Update and Delete (CRUD) operations against business data. Yet the technology stacks used to build these applications have become increasingly elaborate, often requiring significantly more front-end code than business logic.

Rediscovering Server-Side Rendering​

Working with OpenEdge 12.8, I have found myself increasingly drawn back toward a simpler development model using OpenEdge SpeedScript and htmx
For OpenEdge WespSpeed developers, this approach feels surprisingly familiar. It resembles the proven architecture of classic OpenEdge WebSpeed, where server-side code generated HTML directly and the browser rendered the result.

The difference is that htmx brings modern user experience capabilities without requiring large amounts of JavaScript.

Instead of building complex client-side applications that consume JSON APIs, the server simply returns the HTML fragment required to update part of the page. The browser swaps the content automatically.

The model is refreshingly straightforward:

1. User clicks a button.
2. htmx sends an HTTP request.
3. SpeedScript executes business logic.
4. Server returns HTML.
5. Browser updates the page.

No virtual DOMs. No state management frameworks. No JavaScript build pipelines. Just HTML over HTTP.

Why htmx Fits OpenEdge So Well​

One of htmx's greatest strengths is that it allows developers to extend standard HTML with powerful capabilities using simple attributes.

• A button can trigger an AJAX request.
• A form can submit asynchronously.
• A table can refresh automatically.
• A modal dialog can load dynamically.

All of this can be accomplished with minimal JavaScript, and often with none at all.

For OpenEdge developers, the benefits are obvious. We can focus on what we already know best:

• Business rules
• Database access
• ABL development
• Server-side application logic

Rather than splitting application behaviour across multiple technologies, the majority of the application remains within OpenEdge itself.

Full-Stack Control​

Another aspect I particularly appreciate is the level of control. Because I own both the front end and the back end, I can precisely determine what information is rendered the browser and what HTML is returned. The server remains the source of truth.

A SpeedScript page can generate exactly the markup required for a specific interaction. There is no need to expose large API payloads or create additional layers simply to transform JSON back into HTML on the client.

The result is often:

• Less code
• Simpler architecture
• Easier debugging
• Faster development

For many internal business applications, that simplicity has real value.

AI Makes the Approach Even More Effective​

AI-assisted development has made this model even more compelling.

AI Large language models are exceptionally good at producing HTML, CSS, and htmx markup. Given a rough description of a maintenance screen, AI tools can quickly generate:

• Responsive layouts
• Data entry forms
• Validation feedback
• Search screens
• CRUD interfaces
• Modal dialogs
• Tables and pagination

Because the application relies primarily on HTML rather than complex client-side frameworks, the generated output is often immediately usable.
In many cases, I have been able to create fully functional and responsive maintenance screens with little to no custom JavaScript.
The amount of effort required to move from concept to working solution can be remarkably small.

Do We Always Need React, Vue, or Angular?​

This is not an argument against React, Vue, Angular, or similar frameworks.

These technologies excel when building highly interactive applications with complex client-side state, rich user experiences, offline capabilities, or sophisticated browser-based workflows.

However, many business applications simply do not require that level of functionality.
The reality is that many enterprise applications spend most of their time displaying forms, lists, search results, and reports.
For these scenarios, introducing an extensive JavaScript framework can sometimes feel like bringing a construction crane to build a garden shed.
The framework may be powerful, but the problem being solved is often much simpler.
As developers, we should always choose tools that match the problem rather than defaulting to the most fashionable technology stack.

A Practical Alternative​

htmx is not the right solution for every situation.

Applications with complex client-side interactions, real-time collaboration, advanced visualisations, or extensive browser-side processing may still benefit significantly from React, Vue, Angular, or similar frameworks.

However, for a large category of business applications, particularly those developed with OpenEdge, htmx and SpeedScript provide an elegant and highly productive alternative.

By combining: PASOE Web Transport, SpeedScript and htmx developers can build modern, responsive web applications while keeping the majority of their logic where it belongs: on the server.

Conclusion​

Modern web development does not always need to be complex. Sometimes the best solution is the simplest one.

For OpenEdge developers looking to build responsive business applications without becoming immersed in a large JavaScript ecosystem, htmx and SpeedScript are worth serious consideration.

You may discover that generating HTML on the server is not a step backward at all. Instead, it may be a practical and highly productive way forward.

My advice is simple: Try htmx and SpeedScript. You might be surprised by how much you can accomplish with so little JavaScript.