[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip / qa] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: 1714140221386285.jpg (491 KB, 1671x2363)
491 KB
491 KB JPG
>disable javascript
>almost every other website stops working
How did we get here?
>>
>irrelevant time-wasting question
>>
i want to be in middle
>>
Yuri is for cucks.
>>
>>101171871
im on the bottom
>>
>>101171907
now undress
>>
me on the left
>>
>>101172006
are you a girl?
>>
>>101172085
we are all schoolgirls here
>>
>>101171860
well you see you need javascript enabled so that a script can load a script, which loads other scripts that load other scripts and so on, it all makes perfect sense and is the right way to do things
>>
>>101172091
good point, put your hand on my chest first
>>
>How did we get here?
Google senior dev here... it's because anime posters on /g/.
>>
It depends on what you mean by working
You can read most articles today with javascript off
That's what the internet used to be, text and images and links
In that sense they still mostly work
Fuck cloudflare btw
>>
File: 1691275410944064.png (874 KB, 1050x1400)
874 KB
874 KB PNG
>>101171860
Something something corpos like google wanting to turn browsers into a operating system, whatever who cares the web is dead anyway, post moar cute girls kissing.
>>
File: 112893913_p0.png (1.7 MB, 2200x1587)
1.7 MB
1.7 MB PNG
>>101171860
It's less effort to make everything js-only. Consider 4chan:
>opening a thread delivers server-generated posts
>auto-update generates posts client-side with javascript from server-generated JSON API data
It would be less effort to make the server deliver JSON data only and to render all HTML on client side with JS. If 4chan was actively developed instead of being a single-file PHP script hacked by an unpaid retardcuck every fullmoon, 4chan would probably go JS-only.
>>
>>101172338
>>101172454
i want to be in middle
>>
File: 1693680619628376.webm (1.8 MB, 1280x720)
1.8 MB
1.8 MB WEBM
>>101172454
In my opinion it's easier to build the HTML server side(it's just string templating in the end) and dynamically serving it to the client, it will be also faster on any device because you can use a real programming language on the server instead of javashit.
Having a JSON API is not mutually exclusive with the above.
In a perfect would there would be a "imageboard internet protocol" that doesn't even use HTTP (maybe it also has its own data format or maybe it used JSON) and there would be multiple open-source imageboard software you can install(and you control the updates instead of webshit that potentially updates every time you refresh the page) and the web browser would be niche software used only by academia instead of pdf.
>>
File: 82576895_p0.jpg (346 KB, 900x636)
346 KB
346 KB JPG
>>101172560
>Having a JSON API is not mutually exclusive with the above.
Then you would have redundancy again. Good programmers hate duplicate code.
>>
>>101172560
What anime?
>>
>>101172560
I feel like you're describing email (for the text) and FTP (for the images). And then something to display the images.

So basically you want email.
>>
>>101172590
>Then you would have redundancy
No because you have format the application data to HTML somewhere if you're doing a web app, if you do in on the server you won't have to do it on the client(also having an API that replicates the functionality provided by the dynamically served HTML interface is your choice, you could even have something simpler like a RPC), again in a perfect would you wouldn't have to serve HTML at all because you would serve directly to clients compatible with your protocol, but using a API-only server that talks to a JS-only client gives you the worst of both worlds:
- you need a dedicated client that understands your protocol so you lose the inteoperability that the default web client(browser) would give you out of the box
- but at the same time your protocol is limited to what webshit can do(want to do P2P? too bad)
- and your JS-client is also limited to what webshit can do
This is the wrong way of using use the web, the reason people do it is because subconsciously they understand that the web sucks for making applications, so they want more, they want to make real applications like real programmers! but they are too dumb(or they don't know any better or they have agendas... ahem google... ahem) to realize you could do it another way, so they get stuck mentally in the spiral of absurdity that is forcing the web to become an application platform. JS-only clients are not even the end point of this madness, because even JS people subconsciously understand that JS and the DOM sucks for making applications, so they want more, again they want to be like the big boys so why not reimplement the entirety of computing in the browser using WebAssembly? Maybe we will see CPU and hardware emulation implemented in the browser in 20 years.
All of this madness just because webshitters refuse to learn actual programming languages and platform LOL
>>
File: 1708852702401887.gif (999 KB, 500x281)
999 KB
999 KB GIF
>>101173078
An hypothetical imageboard protocol would not be like email it would be more like usenet or activitypub, it goes without saying that email is not anonymous by design.
>>101172835
Sakura Trick.
>>
>disable internet
>all the websites stop working
>why is this happening to me???
>>
>>101172560
>In my opinion it's easier to build the HTML server side(it's just string templating in the end) and dynamically serving it to the client, it will be also faster on any device because you can use a real programming language on the server instead of javashit.
Because you have never built any larger website. When your front end is made of many encapsulated components, all that interact with each other in nontrivial ways, any such SSR quickly becomes unmaintainable mess.
Also goos client side JS will always be faster than waiting for network, even if at the end of that network is infinitely fast backend.
Also JavaScript has nothing to do with Java.
>>
>>101171878
yuri is actually 200% straight
>>
>>101175104
this, it's 200% because there are only girls so it's straighter than straight
>>
>>101175461
>>101175104
straight cucks
>>
>>101171860
me? on the right
>>
>>101171878
tpbp
>>
>JS is supposed to be terrible
>according to the bnrilliant minds of /g/
>none of these programming gods have ever been able to come up with an alternative that isn't only ever displaying static text, with maybe the occasional image

you can tell most of /g/ is unemployed
>>
>lust provoking image
>irrelevant time wasting question
>>
>>101172251
Are you really google?
>>
>>101175966
Does anime bs provoke lust to you? What a fag
>>
>>101175846
and watching a man doing a girl is not cuck?
>>
>>101175925
Implying you can't do a RESTless api with only GET and POST and targetting the output somewhere. Ever heard of iframes?
You can also use meta to control refresh, redirections. If there is no bloat you wouldn't even notice that the page changed. Internet nowadays is FAST as FUCK, but the bloat takes away all the improvements in hardware, infra, protocols, software.
There is also old techniques to do streaming without javascript by holding a HTTP request on a server and pushing the data continuously without any additional action from the browser. It's like you would have a slow connection that needs to take time to send response, but instead of having a slow connection you send the data in some event loop, stream, generator or whatever depending on the technology on the backend. The backends don't just serve static files. Browsers are rendering elements on the page independently. Look how pictures load after the page is already loaded, it's not javascript.
>>
>>101171878
Non-yuri has boys in them, and you watch those boys fuck the girls you like, that's literal cuckoldry. Yuri is by definition the only non-cucked romance.
>>101175925
JS is objectively cancer, the browser should have used Scheme or Lua as an extension language.
>>
>>101177042
>Scheme or Lua
Scheme or Perl and we are good
>>
>>101177042
>>101176470
At least you get the option to self insert. In yuri you either accept your place as a cuck or become a troon.
>>
File: 1711262327951853.jpg (136 KB, 1216x832)
136 KB
136 KB JPG
>>101177467
Self-inserting is a mental illness.
>>
>>101177627
fantazising over the sex of cartoons and collecting images of it is too https://www.youtube.com/watch?v=_r-Om6aUr5k
>>
>>101175925
JS is ok. Used to be bad, but they have fixed it for the most part.

>>101176883
>Ever heard of iframes?
2000s are calling

>>101177042
Scheme and Lua are much less suitable for making websites.
>>
>>101177627
>Self-inserting is a mental illness.
Now that's just cope. Everybody self-inserts when it comes to pornography, you're tricking your dick into thinking you're fucking a chick (your hand). It's why you don't see the dude getting as much focus as the woman in most porn. Jerking off to lesbian shit because seeing two girls naked makes you hard is alright, but actively obsessing over it, saving multiple images, and constantly talking about it despite being the clear third party is mental illness.
>>
i self inserted into ur mum
>>
>>101171860
Js is required for basically anything interactive (including any buttons that don't link to other pages). Not really surprising

>>101172560
Well, if you're fetching json and constructing posts on the client side (like for thread updating), you don't wanna have two implementations of post construction (one on the server, one on the client). Hence, just send json and do it on the client.
>>
>>101180287
I guess you could move the post construction code into a .js library - on server, call this js to construct posts into html and send, on the client, the library will be webpacked into the ui.js.
This would allow you to not have code redundancy while having both server and client side rendering :)
>>
>>101180287
>>101180321
Another alternative is to return html when updating the thread - hence, it's all rendered server side
>>
>>101177467
>>101178642
BASED
remember that as long as your wife's bull looks similar to you, you can just self-insert as him while you watch!
>>
File: 1718797228136165.png (63 KB, 344x258)
63 KB
63 KB PNG
>>101171860
>>101172338
>>101172454
>>101172560
>>101172590
>>101173481
>>101177627
this is gay
>>
>>101177627
this
>>
File: 1694542290000584.jpg (526 KB, 2045x3000)
526 KB
526 KB JPG
>>101173532
>any such SSR quickly becomes unmaintainable mess
Consider that by moving logic to the client you are adding local state(that you may have to synchronize), a universal rule of programming is that the less state you have the better and it's better to manage it in one place because synchronization is hard.
If your application is complex you can't make it simple, but it's better to keep complexity in one place(the backend), this will make maintaining it easier not harder expecially becaue the backend(the server) is an environment you control, the client could be any permutation of browser/os/hardware, you have no control over it.
>client side JS will always be faster than waiting for network
Why do most JS-only web apps take a good second(or more) to load while showing me empty placeholders then?
>Also JavaScript has nothing to do with Java.
They are both shit but I meant Javashit, not Java's shit if you get what I mean.
>>101180287
>>101180321
See >>101173469
>having an API that replicates the functionality provided by the dynamically served HTML interface is your choice, you could even have something simpler like a RPC
Just serve the HTML, it's literally that simple, we figured out this shit 20 years ago.
>>101180464
Yes.
>>
>>101180570
>Consider that by moving logic to the client you are adding local state(that you may have to synchronize), a universal rule of programming is that the less state you have the better and it's better to manage it in one place because synchronization is hard.
Separations of concerns is more important rule than clamping all the state together. You don't need majority of client side state on the server.

>it's better to keep complexity in one place(the backend
This is false. There is a reason why we stopped using PHP.

>this will make maintaining it easier not harder expecially becaue the backend(the server)
Monolithic design is harder to maintain.
>>
>>101178642
you are not getting hard because of some self-insert (does anyone even?)
I think you might be in a minority self-inserting
watching porn is a voyeurism

people get hard for various reasons
many things can make someone horny

you can get horny by just thinking about something naughty
you can get horny by seeing someone naked in some specific clothes
you can get horny by hearing a pleasant voice of the opposite sex (assuming straight)
you can get horny by hearing/seeing someone having sex
you can get horny by sexting
you can get horny by reading a smut
you can get horny by consuming some drugs
you can get horny by stimulating yourself or someone stimulating you - touching, rubbing or whatever

there is no self insert needed for any of these
you are just a cuck and you try to justify your cuckoldry by saying everyone is like
>>
>>101180570
The issue with server side rendering is simply that it's not practical for everything, whereas clientside is. Requiring a request to render something is a limitation. Of course, serverside rendered web pages can still use javascript, but there's a line where you might as well do it all clientside and just exchange json.
>>
me on the right
>>
>>101180450
>>101180860
>y-you're the cuck! it's not cuckoldry if it's a bulldyke doing it! self inserting doesn't exist!
either make an actual argument or fuck off to your containment board
>>
>>101181520
I've generally found that the people constantly bringing up cuckshit out of nowhere are just projecting, and you don't exactly strike me as any different
>>self inserting doesn't exist!
Your argument doesn't rest upon self-inserting existing, it rests upon self-inserting being the default and only valid way that people engage with it, and that any deviation from it means you either want to transform into one of the subjects or that you're still self-inserting but as some sort of off-screen voyeur who is still part of the scene because they are watching their wife cheating on them
The prevalence of shipping communities debunks this
>>
>>101182139
Fool. Shipping is for cucks too. If you want to see your waifu with someone else, you're a cuck. It's as simple as that.
>>
>>101182240
Your argument presupposes that people only ever ship the one single character they like the most, and therefore holds no water.
Unless, of course, you think that every character you like is your "waifu" and that you can have dozens of them, in which case YWNBAW (you will never be a waifufag) and your opinion has been discarded.
>>
>>101171860
women have NO CLUE how easy they can have amazing sex lives.
>>
>>101176883
tldr;
>>
>>101175104
>>101175461
straight is the new gay
no one is more aware of this than women are
thats why so many of you’re alone
>>
>>101173532
>When your front end is made of many encapsulated components, all that interact with each other in nontrivial ways, any such SSR quickly becomes unmaintainable mess
lol, lmao even at this zoomer adhd take, sorry chatgpt can't help you with everything
>>
>>101171860
>>101172454
>>101172560
>>101172590
>>101173481
>>101177627
>>101180464
>>101180570 the guy too
>>101172338
would make love to all of them
>>
>>101184193
nerd
>>
>>101184216
Guy?
What guy?
>>
>>101171860
Me taking the picture
>>
>>101171860
In 2013, the Snowden leaks made the masses aware that glowies are spying on them all the time. As a result, HTTPS adoption increased, making it much harder for glowies to perform mass surveillance. So in June 2014, glowie asset Cloudflare launched Project Galileo,
>which offers free defense tools and technical support to human rights groups, activists, journalists, and artistic organizations around the world.
In order to fingerprint and properly track people, Javascript tricks are required (otherwise you could just use a proxy or similar). So Cloudflare tries to get as many glowie targets under its 'protection' so all dissidents can easily be identified and tracked. They're actively trying to make the web unusable without Javascript because otherwise you might have actual privacy. This is also why Javascript is an all-or-nothing thing; you can't just allow a specific script on a specific site to access specific functionalities, you have to allow ALL third-party code to run on your device and make full use of everything Javascript is allowed to do. It's possibly to restrict this using third-party extensions, but they're working on that (see e.g. Manifest V3).
>>
>>101182786
They know. They just don't bother.
>>
File: 1707950802819082.jpg (190 KB, 943x1334)
190 KB
190 KB JPG
>>101184216
>the guy
Yui is a cute girl.
>>
>>101184193
Not an argument.
>>
File: 118051413_p1.jpg (235 KB, 827x1169)
235 KB
235 KB JPG
>>101185751
And what a boy!
>>
>>101171860
What's the problem with JS?
>>
>>101187222
too old
>>
>>101171860
I heard that if you disable SSL, it breaks websites too, that's crazy, man
>>
>>101187441
Damn, I'm only few months older than JS.
>>
>>101187222
It's extremely slow and wastes CPU cycles.
>>
>>101185559
>you have to allow ALL third-party code to run on your device and make full use of everything Javascript is allowed to do.
That's not true. There is quite a lot of webapis that require your consent, https, or even manually changing flags. Browsers also implement antifingerprint measures, limiting what kind of data JS can access.

>It's possibly to restrict this using third-party extensions, but they're working on that (see e.g. Manifest V3).
What do you mean? In what way Manifest V3 prevents extensions from limiting what page JS can access?
As far as I know, it only limits what kind of requests can extensions can block, not what they can do after the JS scripts load.
>>
File: 1478179982458.png (373 KB, 2884x2430)
373 KB
373 KB PNG
Today I will remind them
>>
>>101188081
From my experience yurifags are more likely to be cuckolds.
For example I always imagine my waitu being with me. I interact with her through my imagination and I couldn't bear to see her with someone else. But I know some "waifuists" who like a friend of my wife and they very often consider themselves unworthy and rather imagine her being with my wife. If this isn't the very stereotypical definition of cuckoldry then I don't know what is.
That's being said, there is nothing cuckoldy about getting aroused from voyeurism of some random tho girls going for it. But in your example it is explicitly stated that one of the girl might be your waifu, and unless you are some Facebook normie, you should know that waifu is your partner. And wanting to see your partner with someone else is cuckoldry.
>>
>>101171860
Being gay
is not okay
>>
>>101188207
Only if you're a man. It's ok for women to do it.
>>
File: 1693669104032742.gif (236 KB, 280x207)
236 KB
236 KB GIF
>>101177467
>>101177627
I want to self-insert between those dykes.
>>
>>101175925
WebAssembly.
>>
>>101188000
>Browsers also implement antifingerprint measures
Tor Browser does. But mainstream browsers fully spread your anus for the advertising industry, a natural result of the biggest browser (that almost all other browsers are based on) being developed by an advertising company and the only 'competitor' being a zombie artifically kept alive by said advertising company.

No mainstream browser survives https://coveryourtracks.eff.org/ without extensions locking it down.
>>
Is this the Debian thread?
>>
File: 1700027266535555.jpg (220 KB, 1061x1583)
220 KB
220 KB JPG
>>101190828
Yes.
>>
>>101171860
>removes chain from bike
>almost every bike stops working
how did we get here?
>>
File: the purest form of linux.png (920 KB, 2133x1200)
920 KB
920 KB PNG
>>101190828
>>101190929
>>
>>101190963
It's more of a 'remove internet connection from car' situation. The web worked fine without Javascript, especially without the bloated mess it is now.
>>
>>101187613
>>101190963
Neither SSL or JS are necessary for the web to work, both of them are garbage bolted on top of it and serve only corpo interests.
>>
https://web.archive.org/web/20060930205635/www.eti.pg.gda.pl/katedry/kiw/pracownicy/Jan.Daciuk/personal/JavaShit.html
>>
>>101190999
SSL doesn't serve corpo interests.
>>
>Use NoScript
>Nothing works
>Have to enable scripts one by one
>Quite fun when trying to make an online purchase
>And the script hostnames are often non-descriptive and tell you nothing about what the script is for
>And the purchase keeps getting rejected due
>And certain scripts don't attempt to be loaded until at the payment stage, so there is a limited time window
>>
>>101190604
>But mainstream browsers fully spread your anus for the advertising industry, a natural result of the biggest browser
This is false. Things like timer resolution, audio context precision, webgl info, etc is often limited or unavailable. Especially Firefox, but chromium also does it to some extend.
>>
>>101190604
Also here is the result from my brave on my phone. I do not have any extensions installed.
>>
File: 1691349950883562.jpg (108 KB, 850x799)
108 KB
108 KB JPG
>>101191059
It does, SSL/TLS uses trusted centralized certificate authorities which are always controlled by corporations(and potentially indirectly by governments and intelligence agencies), a superior design would be to use a web of trust of even better just do it the way the Tor network does it by storing the public key directly in the domain name and by using a distributed hash table.
>>
>>101191218
You can become an independent CA.
>>
>>101191218
You realize that you could just distrust every single major CA on your machine and operate in web-of-trust mode and manually authenticate certificates for specific sites?
>>
>>101191218
That's not a TLS issue, that's a CA issue. Your browser is at fault, not the protocol. A saner client would just accept certificates individually and store them indefinitely, rather than just asking 'daddy is this okay' every single time and blindly trusting daddy's answer, not bothering to check or store anything by itself (other than 'this isn't on the good goy list, so they must be trying to steal your credit card!').
>>
>>101171860
Did people magically forget the random bloat and shitty addons they kept adding to support more features? ActiveX, Flash, Adobe Air, Java...
HTML isn't enough, in fact, HTML is retarded, why waste bandwidth on redundant tags? what should've been is that the server tell the client how to render the website only once, then only send raw data after it, no formatted or human readable garbage, with maybe a debug mode where it sends something human readable like json.
Now you tell me why the fuck do you need to send a full page and recalculate the whole layout when you only update a part of the page? the server only needs to send the diffs, the minimum changes, the client should handle it, it's a one time cost for the client, this isn't the 90s anymore where servers are powerful and clients are rocks, clients can handle running a bit of code these days, fucking TTF Fonts have virtual machines in it.
Also all that telemetry and ads related js crap should be pushed to the server, if the host want it, he has to pay for its processing power by running it in the server, not the client.
>>
>>101191468
In my opinion we should get rig of HTML-first web and turn it into an opt-in Web API at JS disposal. Modern websites are not "documents", they are software. Browsers should become what they actually are, virtual machines that run JS. DOM, HTML, CSS should be just utility libraries that a JavaScript website can use if it needs to. Or it could implement it's own layout and/or rendering engine.
Next step would be making web wasm first and hardware wasm acceleration.
>>
>>101171860
>disables language that web works on
>web stops working
>"HoW aM i So ReTaRdEd"
>>
>>101190963
>>101191747
Give me one reason why JS should be a hard requirement for websites on top of HTML, CSS and PHP.
>>
>>101191657
That's the point of native apps, or it was before electron shit became mainstream, which means HTML will never die.
Having a specialised app for imageboards for example was very nice, you can access all compatible imageboards and customize them all at once. I think what should've been is that (most) websites should've been under specific categories that the client can render, 99% (if not all) blogs should be the same, why not compress them? It doesn't mean everything has to look the same, they can have different "looks" just fine.
I still blame js because the real issue is having billions of ways and libraries to achieve basically the same thing, it segregated the world and forced repetition. There should be one single (and good) way of achieving the same thing, look at how Figma solved GUI, instead of having millions of custom widgets with their own headaches and autistic special edge cases per platform, everything is composed of the same 3 basics components (a shape, an image, and text), you use those basic components to make literally everything you need, it's simpler, it works.
>Next step would be making web wasm first and hardware wasm acceleration.
I'm fucking tired of having more abstractions and more sandboxes on top of sandboxes, sandboxing should be an OS feature, of better yet, a hardware feature, and you should be able to turn off arbitrary features per sandbox for even more security, wasm is not it.
>>
>turn off monitor
>can't see what I'm clicking on
How did we get here?
>>
>>101191887
>That's the point of native apps
Native apps are not cross platform. Webapps are so popular now because you can visit them from any device, with a single click, without putting trash in your system.

>Having a specialised app for imageboards for example was very nice, you can access all compatible imageboards and customize them all at once. I think what should've been is that (most) websites should've been under specific categories that the client can render, 99% (if not all) blogs should be the same, why not compress them? It doesn't mean everything has to look the same, they can have different "looks" just fine.
That's just RSS.

>I still blame js because the real issue is having billions of ways and libraries to achieve basically the same thing, it segregated the world and forced repetition.
Nah, that would make web real repetitive and soulless. Right now you can use JS and other tools to make your website like no other.

>everything is composed of the same 3 basics components (a shape, an image, and text), you use those basic components to make literally everything you need, it's simpler, it works.
That's why I'm in for making HTML and CSS opt-in so you could make your websites from such primitives or even just some abstracted GPU command buffers.

>I'm fucking tired of having more abstractions and more sandboxes on top of sandboxes, sandboxing should be an OS feature, of better yet, a hardware feature, and you should be able to turn off arbitrary features per sandbox for even more security
That's the point! Right now browser is a document viewer that has a script interpreter in it that has entire virtual machine as a library in it. I'm advocating for making browsers the virtual machines that run wasm, preferably on hardware or JIT compiled, and only provides other stuff as opt-in apis. That's much less abstractions.
>>
>>101171860
VGH FVYVKO
>>
File: kissu.png (1.31 MB, 850x1200)
1.31 MB
1.31 MB PNG
>>101191657
At that point, just make a different protocol. Why is the Hypertext Transfer Protocol used to transfer software rather than hypertext documents?
>>
>>101192457
Retard
>>
>>101193794
It's just that by name. Content type can be whatever, and it works fine for binary blobs like wasm modules.
>>
>>101171860
The client devices are more capable than those of the last. And because their are more clients, the server load needs to be reduced somewhat.
>>
>>101171878
Let me guess, you would rather watch something that includes a d*ck?
>>
>>101175925
You dont need any more than that faggot. The internet should be 100% html
>>
>>101191657
kys kike
>>
File: meow.png (2.52 MB, 2500x1548)
2.52 MB
2.52 MB PNG
>>101194550
But >>101191657 was complaining that the standard of using the hypertext transfer protocol to transfer documents written in the hypertext markup language didn't fit the modern use case. As pointed out elsewhere in the thread, HTTP's functionality of returning a document in response to a query is not sufficient for the modern web, in which 'pages' are in practice software rather than documents. Doesn't it make more sense to create a different protocol for this new use case, rather than trying to push a square peg through a round hole by modifying either the peg or the hole?
>>
File: 1647226685934.jpg (805 KB, 2000x1500)
805 KB
805 KB JPG
>>101171860
because most web developers forgot (or never learnt) how to engineer a solution. They stopped at being programmers. Monkeys that put pieces together, and never advanced beyond.
>>
>>101195496
I was talking about HTML not HTTP. I don't have anything against HTTP. It would be completely fine for JS or wasm-first websites.
>>
>>101171878
only dick i ever want to see is my own
meanwhile you enjoy watching other men fuck chicks
that makes you the cuck
>>
When will jirai-kei women appear in America?
>>
guess what, if you disable css, your page will loke like shit too
>>
>>101175925
he got it right, /g/ is majority unemployed as proved by this >>101194902
>>
>>101178642
girl on girl action is by far more erotic than boy on girl
>>
>>101198816
>loke like shit
According to whom?
>>
>>101201209
>i fucking LOVE Times New Roman black text on a pure white background, i can't get enough of it
>>
>>101201263
You can change all of that without CSS.
>>
>>101171860
Stop browsing corporate websites and you'll be fine.
>>
>>101173481
What about bitchan ? If only there were more instances...
>>
CSS is fucking crazy. It's overly complicated and turing complete. It's typical webshit bloat and one of the many reasons why it's nearly impossible to write a new browser engine that's compatible with most of the web.
>>
>>101171860
I want to impregnate both of these of-age attractive young women
>>
>>101201867
of what age? one of those girls is 14
>>
>>101201923
I have no idea who the characters are, and they are both 18 in my headcanon
>>
>>101173469
>understand that JS [...] sucks for making applications
What? How can a programming language "suck"? Especially a relatively terse higher-level language? What do you expect to be different between different languages, the ability or inability to for-loops or something?
You sound like a novice.
>>
>>101187905
>It's extremely slow and wastes CPU cycles.
No it isn't? It's the fastest interpreted language (except maybe Lua? But who cares), and is able to compete with some compiled languages like Go. Also a typical good JS app architecture relies on heavy parallelization, which also should be handled entirely asyncly (the only area where I make an exception in the JS ecosystem is some of the file I/O handling and in general atomic shit), so most of these single-thread speed comparisons between languages (determined via toy problems) are theoretical wank anyway.

If your JS app is slow, then congrats, you almost certainly are being blocked by I/O and network. Not like JS can help here.
>>
File: dread.png (34 KB, 802x418)
34 KB
34 KB PNG
>>101171860
>no javascript
>just werks

How did they do it?
>>
>>101203933
>just werks
No, it doesn't.
>>
>>101191825
Why is CSS needed?
>>
>>101171860
me on the left
>>
>>101209949
me on the right
>>
>>101171860
offloading server computation to clientside
>>
>>101199041
What kind of job requires js on the internet other than being a webshitter?
>>
>>101171860
>Disable your house's electricity
>Attempt to turn on the lights
>They stay off
How did we get here?
>>
>>101215059
>Have electricity in your house
>Attempt to turn on the lights
>They stay off because you need an lamp app with an internet connection
How did we get here?
Just like electricity is enough for lamps html is enough for web pages.
>>
>>101215941
Luddite detected.



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.