>Sorry, this site requires JavaScript to be enabled.
For a flat blog post? Like, seriously?
For a flat blog post? Like, seriously?
also, most offensive is the use of 3rd party js hosting. given the tiny size of the 3rd party libraries (relative to 1st party code), add them in to the code from your own site (which you're already bundling up. SMH)
[from jsdelivr.net]
polyfill.min.js (31.8kb/96.8kb) (wire/resource)
url-polyfill.min.js (1.9kb/6.1kb)
react.production.min.js (4.7kb/12.3kb)
react-dom.production.min.js (36kb/116kb)
[from liaison.dev]
bundle.a7c7d78d57.immutable.js (108kb/375kb)
actual website code: https://github.com/liaisonjs/liaison/tree/master/website
About the fact that I have used Liaison to build its own website, I agree that it might not be the best choice. :)
For now, Liaison doesn't support server-side rendering, but it is something that could come eventually.
cooming soon: web assemply web 3.0 which (I fear) might feel a lot like flash web pages from the early 00s. I hope I'm wrong.
I don't know want to call what we have now.
There are some benefits, of course. Stable and standardized UI is finally available as a baseline for devs (much like early Windows/iOS software) and all roads are clearly leading toward a unified design model for phone apps/web/desktop. Bloat and needless complexity are the biggest issues at the moment, but all the frameworks seem to be (finally) focusing on becoming more snappy.