/g/ - Technology

install openbsd

[Make a Post]
[X]





The Website Obesity Crisis Nanonymous No.7304 [D][U][F][S][L][A][C] >>7314
File: ae5d8691600d520be429505ae864d290a4be665564a6da1ebc40d4d38643aac0.jpg (dl) (161.94 KiB)
In conversations with web performance advocates, I sometimes feel like a hippie talking to SUV owners about fuel economy.
They have all kinds of weirdly specific tricks to improve mileage. Deflate the front left tire a little bit. Put a magnet on the gas cap. Fold in the side mirrors.
Most of the talk about web performance is similarly technical, involving compression, asynchronous loading, sequencing assets, batching HTTP requests, pipelining, and minification.

All of it obscures a simpler solution.
If you're only going to the corner store, ride a bicycle.
If you're only displaying five sentences of text, use vanilla HTML. Hell, serve a textfile! Then you won't need compression hacks, integral signs, or elaborate Gantt charts of what assets load in what order.
Browsers are really, really good at rendering vanilla HTML.
We have the technology.

Nutritionists used to be big on this concept of a food pyramid. I think we need one for the web, to remind ourselves of what a healthy site should look like.
Here is what I recommend for a balanced website in 2015:
- A solid base of text worth reading, formatted with a healthy dose of markup.
- Some images, in moderation, to illustrate and punch up the visual design.
- A dollop of CSS.
- And then, very sparingly and only if you need it, JavaScript.

Instead, here is the web pyramid as we observe it in the wild:
- A base layer of HTML
- A huge pile of crap
- On top of it all, a whole mess of surveillance scripts.


full article:
http://archivecaslytosk.onion/Gt8AU
https://idlewords.com/talks/website_obesity.htm
my email:
maciej@ceglowski.com

Nanonymous No.7309 [D] >>7311 >>7316
It's true websites are bloated messes, but so are browsers and specs. We need a hipster movement that has its own rendering engine and websites that only support like HTML 4.01 and CSS 1.

Nanonymous No.7311 [D] >>7312 >>7347
>>7309
Those versions of HTML and CSS are still a mess that needs to be nuked. The web needs to be completely scrapped and redone.

Nanonymous No.7312 [D]
>>7311
Computers as a whole need to be scrapped and redone. Look at all this intel bullshit and proprietary bullshit.
Hell, the whole fucking society and world we live in needs to be scrapped and redone.

Nanonymous No.7314 [D]
>>7304
> A solid base of text worth reading
No! I dont like reading! I prefer big pictures, expecially moving.

Nanonymous No.7316 [D]
>>7309
Those versions of HTML und CSS suck even more than HTML5/CSS3. I code in those versions, and my sites are very lean. When testing them, I make sure, that they work on the torbrowser with at least the medium security level, and have at least basic functionality without JS.

The bloating comes from somewhere else: Most webdesigners aren't able to code, and therefore use stuff like wordpress. Wordpress is extremely reliable on all kinds of helper libraries, and also makes use of all kinds of surveillance scripts, so the owners can see what happens on their site without being able to read server logs.

Nanonymous No.7317 [D] >>7318 >>7319 >>7320 >>7323
It's possible to achieve good things while using modern technology.

If you're looking at modern consumer machinery, like cars, sewing machines, and so on, most of those are crap today, and break down within years, while they were well made 50 years ago, and were meant to last at least for decades, or even forever, if they were well maintained. I'm still using a sewing machine from the 1970s, which I've bought for nearly nothing, and which I'm maintaining myself, so that it works just as good as a modern high end sewing machine costing as much as a used car. Speaking of cars: My car also is a very old, very cheaply bought, and very well maintained high end car, which still drives better than most modern cars, but requires considerable skill from the driver, and has much shorter maintainance intervals than modern cars. But you can do the maintainance yourself with readily available tools, while modern cars often require extremely expensive tools, like special screwdrivers costing several hundred bucks each, just to turn a screw.

The difference between old stuff and modern stuff is: Modern consumer goods are not made to be maintained, but to be used by the stupidest customer possible. You buy it, then you use it until it breaks down, and then you throw it away. That's the product cycle of consumer goods. It's often not even possible to clean and lubricate stuff, because everything is encapsulated, and lubricated with a grease, that chemically breaks down within a decade, so things will wear out rapidly after that.

The behaviour of modern consumers is similar to how niggers run society into the ground, when they take over a country. They take over, use stuff without maintaining it, then this stuff breaks down, and then everyone dies without oudside intervention. Modern consumers are like niggers.

This doesn't mean, that modern goods can't be made to be used by reasonable people. I code my stuff very lean and efficient, and with good style, while still using modern technology. But my kind of coding environment requires considerable skill to make use of. Most webdevelopers don't have this amount of skill, so they're using stuff like wordpress, which is meant to be used by stupid people. The laptop I code on is a slightly older W-series thinkpad, which is their highest-end series, and is meant to be maintained, and not to be thrown away. Same with my printer: It's a high-end industry printer, which prints very cheaply in the best quality available, but it's meant to be maintained and repaired. I can assure you, that all my stuff is very well made, in a very good condition, and lasts for a very long time. And all those things were bought cheaply in used condition. But you won't find stuff like this in the consumer sector, because consumers are like niggers.

Nanonymous No.7318 [D][U][F]
File: 6223471913a4eb44d49d4151917ef9be06d1388967488e65c6af67878a2eb729.jpg (dl) (609.45 KiB)
>>7317
You can always find good quality stuff by checking for a "Made in Japan" sticker. If you see something is made in china, toss it in the gomibako.

Nanonymous No.7319 [D]
>>7317
>t. citizen of former soviet bloc

Nanonymous No.7320 [D] >>7323
>>7317
Very well said, i agree with everything.
>The difference between old stuff and modern stuff is: Modern consumer goods are not made to be maintained, but to be used by the stupidest customer possible.
This is so true. And it's even worse if this kind of "dumb everything down and make it worse in the process" philosophy infiltrates outside consumer goods into professional goods like programming languages, libraries and frameworks for example.

Nanonymous No.7323 [D] >>7332
>>7320
>if
I hope that was some sort of typo or dyslexic slip, it already happened long ago.
>>7317
Very true.
My dad started off as an electrician in the early 70s, he bought a voltmeter to do his job. It works to this day.
He's a boomer though, so he decided to replace it just because. Every new one he bought broke down in a few months of everyday usage and somehow was imprecise as hell.
Eventually he wanted his old one back, but I took it for me and I'm not giving it back because I like things that work more than I like him.

Nanonymous No.7332 [D]
>>7323
>dyslexic slip
yes, i mean't that i's bad in general, it's clear that it's already happening since years

Nanonymous No.7347 [D] >>7355 >>7362
>>7311
>Those versions of HTML and CSS are still a mess that needs to be nuked. The web needs to be completely scrapped and redone.
then what do we do?
what is wrong with HTML and CSS? what to do to be good?
should style be in separate file like CSS or no, should there be a single document?
should the web document be text like it is now or should it be binary?
should the headers be compressed like the rest of document? or maybe there shouldn't be headers at all?

Nanonymous No.7355 [D]
>>7347
>what is wrong with HTML and CSS?
They are overly complicated. It takes a tremendous effort to create a rendering engine, let alone an entire browser engine.
>should style be in separate file like CSS or no
Yes, style should typically be in a separate file that way multiple pages can share the same styling.
>should the web document be text like it is now or should it be binary?
I do not have a solid opinion about that.
>should the headers be compressed like the rest of document?
This is related to HTTP which a whole other mess. I think headers are fine. I do not really see a need to compress them.

Nanonymous No.7362 [D]
>>7347
>should style be in separate file like CSS or no, should there be a single document?
There shouldn't be style period you fucking idiot.