>Every modern website loads 10gb of JavaScript every time you access them
>Every modern website loads 10gb of JavaScript every time you access them
Falling into your wing while paragliding is called 'gift wrapping' and turns you into a dirt torpedo pic.twitter.com/oQFKsVISkI
— Mental Videos (@MentalVids) March 15, 2023
thats what happens when you settle for mediocre tooling like Typescript and Webpack instead of Clojurescript and Shadow-CLJS
nobody tree shakes or optimizes anything and the JS world churns daily, meanwhile the CLJS world is the exact opposite.
Typescript adds basically nothing to the bundle. It's the huge dependency trees with react and css engines that kill you, and react isn't even written in typescript.
Idk how you've managed to misunderstand this so badly.
>meanwhile the CLJS world is the exact opposite.
exactly
nobody uses it LOL LMAO EVEN
I have code written in 2014 in production today meanwhile your code will become obsolete and need extensive refactoring in the next release of typeslop
>Shadow-CLJS
>requires both node and java
just use webassembly written in C
>requires node
it doesn't
>webassembly written in C
you dont even know what you're talking about. this is as stupid as saying "use x86 assembly written in C", but even that is less stupid than your post because most C compilers offer extensions for inline assembly
>it doesn't
At least for the dev environment you absolutely need node, not sure when you create a release build. At least that's what i found with a google search
>you dont even know what you're talking about.
He probably meant use webassembly compiled from C(or any other language that supports targeting wasm)
>that's what i found with a google search
Then you likely never bothered to read the first paragraph in the official manual.
Node only ever comes into play when you decide to use NPM packages in your code or use the convenience scripts from the shadow-cljs npm package. Both shadow-cljs and the google closure compiler exist independently of Node and only need Java to run.
The npm package for shadow-cljs does nothing except give you the shadow-cljs jar and a bunch of scripts to hold your hand so you never have to invoke the jar file directly or use the API manually within a clojure REPL.
what else are they supposed to do? most websites work fine if you have an adblock
>what else are they supposed to do?
NOT contain an inordinate amount of shit. Websites used to work just fine, you cuck.
People like that “shit” thoughbeit
Go to the heaviest site you can think of and open DevTools. JS for the site itself rarely adds up to more than a megabyte. The rest of it is video previews from YouTube and TikTok and hi-res images for your fancy display.
>JS for the site itself rarely addps up to more than a megabyte
implying thats somehow acceptable? a megabyte of js? do you know how much a megabyte is?
you ran hundreds of megabytes of machine code to post this retarded responses, so yes
you are prominently retarded
>50gb data cap
THAT was suffering.
modern websites are slow and bloated while not providing the same info density as before.
I'll give you the rationale:
>Most people are on phones
>Phone theme is not completely broken on desktop
<Save money on making one theme instead of two, at the cost of a margin of users
I say we limit data cap to all "smart" phones to 100MB, that is more than enough for everyone's needs.
Then there will be a large push for small websites, and hyper compressed low resolution video.
YouTube can serve 300x300 videos, along with instructions to recreate the video to a neural net which will run on AI accelerator chips on the phone, playing 1080p or higher on the device.
I say we break everyone's windows periodically so we have less unemployment. Creating artificial work seems stupid.
It's more like 2MiB(150KiB compressed) application data, and the a volley of tacked-on ad services for 25MiB(sent uncompressed for some reason)