Re:Software will eat software in a remote-first world
by barrkel on Monday May 25, 2020 @06:23AM
(#23299726)
I think it was easier to build an acceptable GUI in 2000 with VB or Delphi than it is today with our web stacks.
[ Parent
| on HN ]
Re:Software will eat software in a remote-first world
by sokoloff on Monday May 25, 2020 @06:40AM
(#23299795)
I also think the standard of “what is acceptable?” was much lower back then.
Re:Software will eat software in a remote-first world
by rsynnott on Monday May 25, 2020 @09:59AM
(#23301173)
I'm not sure that's true. Here's the UI hall of shame, highlighting the worst of the 90s: http://hallofshame.gp.co.at/shame.htm
Most of the stuff there would be just... normal now. It's quite unusual for SPAs to have a decent consistent UX. And the slowness would never have been tolerated back in the day.
Re:Software will eat software in a remote-first world
by contextfree on Monday May 25, 2020 @03:01PM
(#23303816)
the author of that page seems to believe that mouse hover feedback is bad, even when it's a simple highlight?!
Re:Software will eat software in a remote-first world
by barrkel on Monday May 25, 2020 @08:55AM
(#23300468)
I think that's mostly it. Design has a much larger role, and form-oriented development with common controls doesn't cut it. You couldn't imagine an app like Facebook in a forms-style UI, it's almost ludicrous to imagine.
Looked at retrospectively, forms were just one step above green screen applications on a terminal, transplanting one set of structural idioms to another, like for like.
Re:Software will eat software in a remote-first world
by nogabebop23 on Monday May 25, 2020 @09:20AM
(#23300729)
If forms are essentially terminal apps, is FB much different from a teletype news service, with hyper-filtered content and an infinite set of data sources?
I see massive sea change in connectivity and immersiveness of today, but not really in what we're trying to achieve.
Re:Software will eat software in a remote-first world
by lonelappde on Tuesday May 26, 2020 @02:17AM
(#23307984)
2001 was Mad OS X Cocoa. 2020 is JavaScript. The standard for UI was higher then, but was lost to the almighty god of cloud-based web apps.
Re:Software will eat software in a remote-first world
by nogabebop23 on Monday May 25, 2020 @09:16AM
(#23300683)
or MS Access, or Hypercard - we've had productivity boosters, just never anything remotely close to eliminating the inherently hard act of "building software".
Re:Software will eat software in a remote-first world
by visarga on Monday May 25, 2020 @07:52AM
(#23300127)
Yes, but that GUI was only doing local work, we have much higher requirements today.
Re:Software will eat software in a remote-first world
by barrkel on Monday May 25, 2020 @08:51AM
(#23300440)
The GUI was doing local work, but the database could be remote. Delphi's name is even a pun on Oracle.
I'm not saying they were halcyon days. I'm saying that the effort to do things is not necessarily less these days, in part because we have different expectations (not necessarily requirements) today.
Re:Software will eat software in a remote-first world
by petra on Monday May 25, 2020 @07:15AM
(#23299941)
It's even easier to do so with no-code, low-code tools.
Re:Software will eat software in a remote-first world
by JacobiX on Monday May 25, 2020 @08:20AM
(#23300247)
In 2000 using VB, you can build a GUI, make a working Windows application using a minimum amount of code. Also the documentation (msdn) and the community was really nice.
Re:Software will eat software in a remote-first world
by collyw on Monday May 25, 2020 @11:23AM
(#23301992)
20 years on MS Access has been one of the quickest lowest code way to build a functional application. What a mess everything is these days in comparison.