One simple example that I presented in the other comments: maps. I don't think we ever had (or that it was even possible in a non-networked/poorly networked world) commercial components for maps even remotely close to what services like Google Maps offer.
Similar thing for many tools and services we just take for granted these days (NLP, sentiment analysis, entire game engines, etc.).
The business logic was easier to write in 1990 because the scope was much smaller and the tools much more constrained. But our modern tools are 1000x more powerful, therefore harder to master, true.
I'm seeing that AutoRoute, which eventually became the basis of Microsoft Streets and Trips was first released in 1988.
It certainly didn't have real time traffic, and probably didn't have lane configuration information, or comprehensive business information, etc. But (from descriptions, not personal experience), it showed maps and did routing.
More complex mapping tasks are readily achievable now because more information is computerized and the demand is there, and the portable computing machinery to make it most useful is there.
> One simple example that I presented in the other comments: maps. I don't think we ever had (or that it was even possible in a non-networked/poorly networked world) commercial components for maps even remotely close to what services like Google Maps offer.
Maps are inherently nothing new, instead of a google search, I'd go to my local library and buy a physical map. No need for 3D rendered vector processing over an interconnected network.
Similar thing for many tools and services we just take for granted these days (NLP, sentiment analysis, entire game engines, etc.).
The business logic was easier to write in 1990 because the scope was much smaller and the tools much more constrained. But our modern tools are 1000x more powerful, therefore harder to master, true.