It already did since 2 years ago, random “unverified content” bullshit login walls on popular/valuable advice, tens of megabytes of Javascript that took long to load on intermittent/unstable connections and terrible UI in general.
I wrote .compact to run on a Motorola Droid, which was a 533MHz device with 512Mb of total ram, and a kernel which was very aggressive about freeing up this ram.
My respects to you. I really think websites and software in general need to have efficiency in mind again. Webapps should use as few resources as possible, save people’s time, their money and the planet.
Its not even hard to do. People just always reach for the most complex, overengineered things, instead of stepping back and seeing what you need.
I love component based systems. I love real time and custom user interfaces. That doesn’t mean every site needs to be a big SPA. If you’re a primarily read-only site (blog, wiki, etc), then you shouldn’t be sending huge blobs of JS just for your users to read content. As you add interactivity, you can add more JS, but think about what you’re going to do.
And there are ways around all that. Phoenix LiveView gives you an amazing system for building real time apps that are extremely thin and fast, and SurfaceUI lets you embrace Vue style components, easily
It already did since 2 years ago, random “unverified content” bullshit login walls on popular/valuable advice, tens of megabytes of Javascript that took long to load on intermittent/unstable connections and terrible UI in general.
Don’t forget killing of .compact
I wrote .compact to run on a Motorola Droid, which was a 533MHz device with 512Mb of total ram, and a kernel which was very aggressive about freeing up this ram.
My respects to you. I really think websites and software in general need to have efficiency in mind again. Webapps should use as few resources as possible, save people’s time, their money and the planet.
Its not even hard to do. People just always reach for the most complex, overengineered things, instead of stepping back and seeing what you need.
I love component based systems. I love real time and custom user interfaces. That doesn’t mean every site needs to be a big SPA. If you’re a primarily read-only site (blog, wiki, etc), then you shouldn’t be sending huge blobs of JS just for your users to read content. As you add interactivity, you can add more JS, but think about what you’re going to do.
And there are ways around all that. Phoenix LiveView gives you an amazing system for building real time apps that are extremely thin and fast, and SurfaceUI lets you embrace Vue style components, easily