Perhaps web publishing shouldn't be presupposed to be 'software development'?

zztop44 · on Nov 12, 2023

But very often it is software development. And there isn’t always some bright line between them.

Like it or not, the web is an excellent platform for delivering software applications to users, especially one-off or infrequently used applications.

Let’s use software development tools, rather than web publishing tools, to develop that software.

docmars · on Nov 13, 2023

It's worth mentioning that the friction to deploy a web app is nearly zero these days, depending on how complex it is.

As an example, shipping a macOS or iOS app, via official means, requires a lengthy review & approval process, upfront costs, buy-in into native languages with little to no use outside of these platforms, a limited selection of tools, and hard decisions about which version of the OS to support based on the features you need vs. the market share of older versions.

People (and teams) choose web development for the lower barrier to entry, and as a platform, browsers get products most of the way to their goals, and fast.

skydhash · on Nov 13, 2023

My preference is local first desktop applications. Sometimes it’s because I prefer files, sometimes it’s because native apps are more fluid and more egonomic.

zztop44 · on Nov 13, 2023

What about for getting quotes on insurance? Or booking a restaurant? Or a flight or hotel? Submitting your taxes? Getting printable directions to a trailhead? Proving feedback on someone’s Figma document? Previewing a 3D model before getting it printed…

Is it your preference to install a new local first desktop application any time you wish to do any of these things?

skydhash · on Nov 13, 2023

That depends where the data and the logic all. If they only store the data, but I’m doing all the computation, it may as well be a local app (figma, the 3d viewer..) or at least have an API so I can build my own interface.

I’m not against Web Apps, but many take my browser as free real estate.

nvm0n2 · on Nov 13, 2023

Shipping a macOS app doesn't require view of any kind, beyond notarization, which is just an automated malware scan and takes only a few seconds.

zilti · on Nov 12, 2023

Hopefully WASM will fill that area, and browsers can go back to being browsers.

shadowgovt · on Nov 13, 2023

Not as long as the only way that wasm interfaces to the DOM is through the JavaScript layer.

raincole · on Nov 13, 2023

Then use Wordpress. Or Substack. Or even Wix.

"But we need this and that custom dynamic logic..." well now we're in the realm of software development.

docmars · on Nov 13, 2023

The line is very blurry, and the moment you'd like dynamic, interactive content embedded within that static content is when it's time to reach for a view library like React.

At that point, I'm just going to start the project with React / Vue / Svelte every time because almost 100% of the time, I realize I need to support the features they offer that raw HTML/CSS cannot, or if they do, are very poorly implemented by browsers, hitting limitations with them that become frustrating and prevent you from achieving the scope you're aiming for.

Using any of those three libraries/frameworks is painless, and I can get a project going rapidly and with high confidence that I can support any functionality, interaction, animation, content, routing, and other common web problems, with great ease.