Why is single page meme getting forced on every website?
>destroys back button
>url goes apeshit
>cant close the tab/window because of backgroud xhr/ajax
>browser history fucked
>scroll position is cucked
>loads 500gigabyes of javascript
>java=memory leaks
>feels like gay version of internet
Because everyone wants their site to feel like a phone app, but they don't want to pay for a consultant to tell them that's stupid. So instead they rent a pajeet for a few months to build and "support" their grand idea.
>open in new tab
>about:blank;
>reading large amounts of text
>page refreshes or freezes
>has to scroll all the way back down
How primitive
I wish I knew
single page websites + hamburger meme should be reserved to mobile devices. Doesn't really have anything to do with javascript thought. You can do it without it.
disable javascript
If it's done properly you won't even notice. URLs and back button can work properly.
And if you do it right, it's significantly faster, unless you're an autistic who believes that all websites should be HTML only.
>it's faster unless you do this thing that's actually faster
It's faster compared to doing the same thing not as a single page application. If your website is a static page you most likely don't need to bother, but lately it's rarely the
case
Just think about it logically. Loading just the thing you need via AJAX is obviously going to be faster than loading the whole page.
Leave it to the webshits to instead just increase the size of the webpage to the point where all benefits are lost.
>Loading just the thing you need via AJAX is obviously going to be faster than loading the whole page.
I will guarantee you that a basic, plain HTML site will load faster. By the time you've downloaded all the scripts you'd have already got the plain HTML many times over.
Fucking this.
This is just lazy vs eager loading problem. If you just visit the site once, then sure. But if you navigate through it, SPA will be better. For example on a site where you browse pictures, you'd often view 20+ pictures on one browsing session. With plain HTML + CSS website, you'd have to download the whole package every time, while a SPA will only fetch the images after the initial load.
You're shitting on a good concept just because webshits can't implement it properly.
Na. AJAX and the scripts isn't an issue, it's the shortcut frameworks that every shitty developer uses instead of coding what they need for the site.
They're bloated and slow but they do the job without them having to do the work.
Jow Forums is actually a pretty good example.
Is it faster to click the refresh link at the bottom of the page (or whatever 4chanX provides but not automated) or refresh the whole page?
I know what you mean but your anger is misplaced. People have been building shitty websites misusing infinite scroll and the history API for years, now any idiot like me can grab react + react-router + redux + ssr or the vue/angular/whatever versions and have a functioning SPA that you'd never know was a SPA in a couple hours. Hello world is ~20kb over the network in React or Vue. A fully functioning site with a UI framework can easily be under 200kb and will use less data and be faster after the initial page load.
In summary you're mad about 4 year old tech and not paying attention to current memes
Because webfags are NPC's and garbage "people".
>cache doesn't exist anymore if you don't bloat your """""""app""""""" with 100s of requests and gbs of garbage.
The only difference would be the size difference of the html and json. This completely ignores that you can still use JavaScript to update the page without it being a single page application meme.
>destroys back button
Use the History API
>url goes apeshit
Use the History API
>cant close the tab/window because of backgroud xhr/ajax
You can always force it and most people will, but if your main thread is blocking 100% of the time, you're doing something wrong.
>browser history fucked
Use the History API
>scroll position is cucked
This one is actually kinda' legit, but you can work around this.
>loads 500gigabyes of javascript
Server side rendering
>java=memory leaks
Git gud
>feels like gay version of internet
Iranian homosexuality enthusiasm board
SPAs are popular because its actually more efficient than reloading the whole fucking page for every navigation event. Most of your issues are solved with a bundler and a service worker.
The thumbnail looks like a giant pink dick.
Cache only works on content that is exactly the same.
If 99% of the html page to be delivered is identical to the cached version it still has to download 100% of the new page.
So if you are smart and have your scripts external then they will load from cache and can pull the 1% of new data instead of all 100%.
>Most of your issues are solved with a bundler and a service worker
What is this? Also doesn't good server side rendering require js is run on the sever? I would rather kms than run js on the server.
Angular is actually good.
> url is clean and readable (its called routing)
> lazy loader already exists + IVY engine is very good so no 500 GB of JS
> it's less gay than internet back in the day of internet explorer shit