I started using Svelte. I got stuff done pretty fast, and I was able to do most of what I wanted to do with a nice ease. copious-world. Maybe someone wants to contribute.
I used a set of components OAT some years ago. It was pretty good. But, every stared using jQuery. And, OAT hasn't changed much in a long time.
There are some frameworks that are just better than others. In particular, you can get benchmarks on running the frameworks. React and Angular are sort of big and slow.
In the end, you can see that WASM based pages do things faster.
And, yes all of that has to do with web apps, not the pages. I started writing a page generator that makes a fairly static page. But, some parts of the page are left of for lazy loading. Maybe the code that manages the lazy loading is sort like an app, but I am fairly sure it doesn't got that far.
I my mind, a page gets a certain amount of use or interest. If the user can begin to load parts of things that he is interested in, then the page can slowly build into either his desired view, or that his page can slowly become a web app. But, his first experience with the page will just be a static page that tells him something he wants to know.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I started using Svelte. I got stuff done pretty fast, and I was able to do most of what I wanted to do with a nice ease. copious-world. Maybe someone wants to contribute.
I used a set of components OAT some years ago. It was pretty good. But, every stared using jQuery. And, OAT hasn't changed much in a long time.
There are some frameworks that are just better than others. In particular, you can get benchmarks on running the frameworks. React and Angular are sort of big and slow.
In the end, you can see that WASM based pages do things faster.
And, yes all of that has to do with web apps, not the pages. I started writing a page generator that makes a fairly static page. But, some parts of the page are left of for lazy loading. Maybe the code that manages the lazy loading is sort like an app, but I am fairly sure it doesn't got that far.
I my mind, a page gets a certain amount of use or interest. If the user can begin to load parts of things that he is interested in, then the page can slowly build into either his desired view, or that his page can slowly become a web app. But, his first experience with the page will just be a static page that tells him something he wants to know.