Give an inch take an inch
Give an inch take an inch
Give an inch take an inch
STOP. DOING. UX.
Computers were meant to do math, not make pictures.
Trillions of pixels illuminated, but no real life benefit has been discovered.
GUI. Ray Tracing. Generative Adversarial Networks and Diffusion Models.
Terms dreamed up by the deranged.
They are playing you for fools!
GUI. Ray Tracing. Generative Adversarial Networks and Diffusion Models.
Those things can have their place. But not on a restaurant website when I'm trying to order curry.
It's infuriating!
I just want static html webpages back. The sheer volume of scripts that run just to display text these days drives me nuts.
Agreed! Bring back usenet and keep the normies out. Judging by all the fascist uprisings, they weren't ready for it anyways.
lol, Committee for the Extermination of Eternal September.
The guys that went to the moon were engineers and highly trained to use the computer. We can dream to have users half as competent.
After separating from the Command Modupe for lunar descent, there was a faulty abort switch discovered on the Apollo 14 lunar module that required Alan Shephard and Edgar Mitchell to reprogram the lunar module computer in lunar orbit.
Well how else is google gonna keep tabs on you.
Heh
Unused RAM is wasted RAM. Apps like Chrome use available RAM if it's available, but they should be releasing it for other apps to use when there's high memory pressure.
It's the same with disk caching. If you have a lot of free RAM, the OS will use all of it for caching files.
my problem with certain programs, chrome included, is they tell the os "no, you can't have this ram back. i'm using it"
i understand the logic of your argument, but it's never played out in life
In some cases, the RAM actually is in use by the site. That's especially the case on sites with heavy client-side logic. In that case, it's not Chrome's (or Firefox's) fault, it's the website's fault. If you hover over the tab, it should show memory usage in the popover.
Chrome has a "Memory Saver" feature where it'll unload tabs that are offscreen/hidden which helps quite a bit. Not sure if Firefox has something similar.
No, the reason why browsers use so much RAM is because every tab is it's own process and sandbox. That and lazy handling of content.
Edit: apparently i overestimated the overhead of process & sanbox per tab? So it's more lazy handling, i.e. keeping pictures in RAM instead of pushing them to cache?
Sandboxing does use some RAM, but it was a big win for security. One site can't crash the entire browser or use a security hole to get access to data on other tabs. Still, the majority of the RAM is taken by the site itself. The processes do share some RAM - they're not entirely isolated.
Back in 69 more people were carrying the load of logic in their heads. Its been a double edged sword of progress with more responsibilities offloaded to automation
My desktop with 64gb sat idling with a web browser open:
You got 32gb to play with chump
The NASA computers were among the most advanced computer science of their day. They were built by engineers with cutting edge technology. Chrome is a web browser, an absurd behemoth intended to view everything from a static page from twenty years ago to a dynamically assembled webapp using frameworks even the app's creator doesn't know one tenth of, but still has to import, and the whole thing is built to spy on what you do while you surf for cat pics and pussy pics for the ten trillionth time, feeding google's monopoly.
Not even apples to oranges. Apples to the lump formerly known as the planet Pluto.
so many reasons to ditch chrome and google altogether...
Link to the memory module used: https://airandspace.si.edu/collection-objects/core-memory-module-saturn-v/nasm_A20210580000
It's more impressive when you see this giant block of wires in person.
Isn't it great that we don't have to be so efficient anymore?
I blame WYSIWYG CMSs
People in 1969: What is a browser tab?
You know those paper folders? Yeah imagine that each flap is actually a screen.
You're welcome.
Good thing they didn't need chrome to go to the moon.
You can do math without a computer, it turns out.
Putting shit on the moon is very easy from a maths PoV
That's not why we were able to get Apollo 11 onto the moon using only 8 kilobytes. The real reason is because we used the most batshit sorcery mankind may ever know to eek out every last ounce of usefulness we could muster from those 8 kilobytes.
Games were impressive in this way too. Computers and consoles didn't have much CPU power or memory, so they had to squeeze every little bit.
This was still happening even with 5th gen consoles. Crash Bandicoot couldn't fit in the Playstation's memory so they ended up overwriting system memory and memory allocated to features of Sony's standard library they weren't using.
These days, game development is more "boring" in that aspect. Systems are powerful and frameworks like Unreal Engine handle all the core stuff. That's not necessarily a bad thing though - it lets the game developers focus on the game itself.
There was some sorcery involved, yes. But that does not mean it wasn't a fundamentally easy problem. Orbital mechanics are the easiest and cleanest physics around. That's why classical mechanics was so incredibly useful: it's a near perfect predictor for movement in the sky. There ain't no friction no nothing. Just clean positions, gravity, and propulsion.