lane centering is a bit too annoying for me, i need to keep my hands on the wheels anyway.
33 karma · joined July 7, 2020
lane centering is a bit too annoying for me, i need to keep my hands on the wheels anyway.
there's also the relatively static pricing of these and generally growing wages, making short upgrade times more common.
I lived in Brisbane, Australia for a year. The good state of public transport there (at least for my use, commuting to/from Uni (UQ) and the city from Toowong) made car use non-essential. The sidewalks are maintained and have enough space to the road to not be alarmed by cars. To get further/certain parts of Brisbane is still a chore as it's still a car-centric infrastructure, but comparing it to Jakarta, Indonesia/metro US, it's much better. Public transport in Jakarta is an option for most, but the last-mile experience with subpar sidewalks (especially the lack of shade) make it such a chore.
I felt much healthier to walk and take public transport for my daily commute, and not to mention the beautiful views on the way. The increase in my Quality of Life is very apparent. I really miss it, and looking to move to Brisbane or another city with similar/better commute/transport paradigm in the future.
I think a lot of the "best-practices" for SPA is trying to do this. But as streaming the data transfer is not yet common, the data is abstracted as a giant JSON object to be a parameter of the UI as a stateless function (React+Redux/MobX/etc, Vue+VueX). When enforced correctly on the project level, what's complicated _is_ syncing the data to the server. I think you'll like Supabase's subscription approach to reactively bind the JSON for the client.
I think a separation between the info-web (document-content heavy) and the app-web (needing stateful data sync) will be more clearly defined in the next few years. Nobody likes trying to sync data between the client and server over HTTP calls; we just have to wait for streaming to be the norm for the app-web (and native apps, ofcourse).