For a sight that is so necessary to most Americans, it's really lacking in basic information and excessive in unnecessary information
[1] - https://www.dmv.ca.gov/portal/ [california dmv]
[2] - http://www.dot.state.wy.us/home.html [wyoming dmv]
[3] - https://dmvnv.com/index.htm [nevada dmv]
And to your point on URL's I don't think there is any real pattern. https://www.flhsmv.gov/ is Florida's state level DMV and counties have their own separate sites for local tag/tax offices.
PEBKAC. You've been scammed. That's not a DMV site. It's a web site that does very well playing Google's SEO game.
Search and Gmail seem to be first-class citizens, but almost everything else seems like it's in maintenance mode. I also know from friends who work(ed) there that Google's culture rewards things that are new, not improving existing products.
Google Assistant is a particularly egregious example of a product that has gotten worse over time.
The product is getting slower, more bloated and less user friendly with each release. That's been going on for many years now. I really wonder what's happening at that company.
Recently I've been seriously considering switching to OneNote.
If it sounds like I have a better approach in mind, I sure do. My main stacks are TypeScript on Node & Browser. Tools for these builds could easily be type safe by being built with TS as an assumption, and easily debuggable by being piped in stages just like a normal Unix chain. This doesn’t have to be wildly inefficient, the type system knows enough to determine what can be processed concurrently, and intermediate build products could be virtual without hitting the FS.
A naive approach just to prove this out would disregard those efficiency considerations and just literally pipe a series of builds with existing tools, each one taking the previous product as input.
Have tried Woven of recent times but it doesn’t cut it. I miss Sunrise (MS bought them).
