Trips of truth.
Everything "web" is perpetually broken, and instead of fixing things - or perhaps even believing they ARE fixing things - ((they)) keep piling on layers and layers of cruft that only makes web browsers an even bigger attack surface and thus security nightmare. >let's make webGL and webGL a thing, and let's make HTTP/3 use UDP because reasons
I'm not OP, but sure, I'd love to stop using web browsers, and I'd even be willing to go to Stallman-esque lengths and set up a server somewhere that Curls the stuff I want, sanitizes it, and sends it to me to read in PDF format.
But modern web bullshit makes even that extremely difficult, since actual web PAGES (which would be amenable to such an approach) no longer seem to exist: everything absolutely has to be a "web app" these days with fucktons of javashite to render anything. >lol what is graceful degradation
Even fucking LULZ is guilty - have you tried viewing the Catalog without scripting enabled?
>let's make HTTP/3 use UDP because reasons
there's good reasons for writing your "own TCP" (rUDP), if you look at HTTP/3's selling points it should become clear
HOWEVER if done correctly - and I will say that may company does not do it correctly either - web apps can be powerful, fast, bug free and all of that at the same time while running on every device which has a recent browser. You just have to invest your time in it - and nobody wants to pay for that. And you gotta stop >keep piling on layers and layers
these are not needed in 2023. Also do not ever visit the shithole that is /wdg/ on this board. The immense amount of stupidity overthere results in them shilling the next big framework with yet another stupid shitty name at a point when they have not even managed to work with the last big next thing.
>just stop using the web
Easier said than done when so many services are moving to "online only".
Have you ever tried buying a specific type of train ticket at the fucking train station only to be told "sorry, sir, we only sell that type of ticket online"? Well I fucking have.
Restaurants asking you to scan a QR code and order and pay via your phone are another egregious example.
>let's make HTTP/3 use UDP because reasons
there's good reasons for writing your "own TCP" (rUDP), if you look at HTTP/3's selling points it should become clear
Yes, TCP has warts, and I understand how creating a reliable channel on top of UDP bypasses that.
That doesn't make applying that to HTTP a good idea.
Interoperability is one of the most, if not the most important aspect of the web, and without VERY compelling reasons to change things (like running out of IPv4 space), it's best to be conservative w.r.t. the basic protocols.
And the changes - I refuse to call them improvements - in HTTP/3 provide little value compared to the breakage it causes. >but muh performance
If your website needs so many HTTP requests to function properly that you have to multiplex a gazillion HTTP requests and can't afford TCP handshake delays, then you're part of the problem. Slim down your bloody website instead of changing web standards FFS. It's like the WEBP bullshit all over again.
You know cs2's panorama is written in web (coherentlabs afaik) with HTML, CSS, and JS, right?
They even made their own fucking shitty little jQuery clone for their UI.
yeah? it looks great, is responsive and doesn't take a lot of resources
it's the opposite of firefox and the modern web
You know cs2's panorama is written in web (coherentlabs afaik) with HTML, CSS, and JS, right?
They even made their own fucking shitty little jQuery clone for their UI.
>just stop using the web
Easier said than done when so many services are moving to "online only".
Have you ever tried buying a specific type of train ticket at the fucking train station only to be told "sorry, sir, we only sell that type of ticket online"? Well I fucking have.
Restaurants asking you to scan a QR code and order and pay via your phone are another egregious example.
[...]
Yes, TCP has warts, and I understand how creating a reliable channel on top of UDP bypasses that.
That doesn't make applying that to HTTP a good idea.
Interoperability is one of the most, if not the most important aspect of the web, and without VERY compelling reasons to change things (like running out of IPv4 space), it's best to be conservative w.r.t. the basic protocols.
And the changes - I refuse to call them improvements - in HTTP/3 provide little value compared to the breakage it causes. >but muh performance
If your website needs so many HTTP requests to function properly that you have to multiplex a gazillion HTTP requests and can't afford TCP handshake delays, then you're part of the problem. Slim down your bloody website instead of changing web standards FFS. It's like the WEBP bullshit all over again.
: easier said than done.
Sure, it's possible to live your life completely offline, but it's becoming more and more difficult.
I suppose it depends on where you live, but, to give you an example, in my city the last bank branch closed shop, telling customers to use the website instead. >Backward compatibility? Analog fallbacks? What are those?
how hard would it be to create mirrors of popular websites that rip away all the javascript/css/ad tracking bullshit and just posts the content? Seems like an RSS reader + some kind of parser that gets the relevant article content + a web server would do it no?
tf is cs2.exe, there's a new counter strike?
yeah
it's shit
You are shit
kill yourself valve cocksucker shill
seething troon
see pic
i don't get it
>i don't get it
same goes for me with
Thank you very much in the name of the Chinese Communist Party.
nub
im starting to like it
didnt like it at first though
colors could be toned down, and the new inferno sucks ass though
then stop using them??
they'll stay that way as long as you keep consuming
Trips of truth.
Everything "web" is perpetually broken, and instead of fixing things - or perhaps even believing they ARE fixing things - ((they)) keep piling on layers and layers of cruft that only makes web browsers an even bigger attack surface and thus security nightmare.
>let's make webGL and webGL a thing, and let's make HTTP/3 use UDP because reasons
I'm not OP, but sure, I'd love to stop using web browsers, and I'd even be willing to go to Stallman-esque lengths and set up a server somewhere that Curls the stuff I want, sanitizes it, and sends it to me to read in PDF format.
But modern web bullshit makes even that extremely difficult, since actual web PAGES (which would be amenable to such an approach) no longer seem to exist: everything absolutely has to be a "web app" these days with fucktons of javashite to render anything.
>lol what is graceful degradation
Even fucking LULZ is guilty - have you tried viewing the Catalog without scripting enabled?
webGL and webUSB*
> I'd love to stop using web browsers
you can use gopher.
>let's make HTTP/3 use UDP because reasons
there's good reasons for writing your "own TCP" (rUDP), if you look at HTTP/3's selling points it should become clear
I am a professional web dev.
I agree with you.
HOWEVER if done correctly - and I will say that may company does not do it correctly either - web apps can be powerful, fast, bug free and all of that at the same time while running on every device which has a recent browser. You just have to invest your time in it - and nobody wants to pay for that. And you gotta stop
>keep piling on layers and layers
these are not needed in 2023. Also do not ever visit the shithole that is /wdg/ on this board. The immense amount of stupidity overthere results in them shilling the next big framework with yet another stupid shitty name at a point when they have not even managed to work with the last big next thing.
>just stop using the web
Easier said than done when so many services are moving to "online only".
Have you ever tried buying a specific type of train ticket at the fucking train station only to be told "sorry, sir, we only sell that type of ticket online"? Well I fucking have.
Restaurants asking you to scan a QR code and order and pay via your phone are another egregious example.
Yes, TCP has warts, and I understand how creating a reliable channel on top of UDP bypasses that.
That doesn't make applying that to HTTP a good idea.
Interoperability is one of the most, if not the most important aspect of the web, and without VERY compelling reasons to change things (like running out of IPv4 space), it's best to be conservative w.r.t. the basic protocols.
And the changes - I refuse to call them improvements - in HTTP/3 provide little value compared to the breakage it causes.
>but muh performance
If your website needs so many HTTP requests to function properly that you have to multiplex a gazillion HTTP requests and can't afford TCP handshake delays, then you're part of the problem. Slim down your bloody website instead of changing web standards FFS. It's like the WEBP bullshit all over again.
I've never even used half of my 16gb Ram. I don't get why ram usage is a problem.
you don't do anything with your pc
>on linux
>complains about everything
yeah? it looks great, is responsive and doesn't take a lot of resources
it's the opposite of firefox and the modern web
> Is on windows
> complains about anything
you brought this on yourself anon.
You know cs2's panorama is written in web (coherentlabs afaik) with HTML, CSS, and JS, right?
They even made their own fucking shitty little jQuery clone for their UI.
dota 2 used to have an old v8 engine in the game for over a year with known vulns which could own you if you downloaded the wrong arcade game
sounds interesting say more
It's truly the worst!
Unused ram is wasted ram
>(47)
You literally have like 10 extensions and 100 tabs open while shitting on it for its ram usage. 400mb ram on my machine.
and one browser window with 20 tabs...
Way too much. Browsers are supposed to have 1 or 2 extensions and max 10 tabs or else risk shit tons of ram usage nagger
>I hate the modern web and web browsers.
You're free to not use both of them.
Like I said in
: easier said than done.
Sure, it's possible to live your life completely offline, but it's becoming more and more difficult.
I suppose it depends on where you live, but, to give you an example, in my city the last bank branch closed shop, telling customers to use the website instead.
>Backward compatibility? Analog fallbacks? What are those?
yeah yeah, we know you're just flexing with your cs2
how hard would it be to create mirrors of popular websites that rip away all the javascript/css/ad tracking bullshit and just posts the content? Seems like an RSS reader + some kind of parser that gets the relevant article content + a web server would do it no?
>firefox
>modern
The only "modern" thing about it is the tranny and nagger acceptance ideology by the company.
Browsers are not even the whole problem. It's websites that are designed like hot garbage.
The internet peaked in 2007. FACT!
Kek, who cares about a few gigs of ram, I got 128 GB of ram in my machine, OOMs are for poorfags.
It's shit but there is nothing you can do about it. Get more RAM if it bothers you