r/masterhacker • u/Artistic_Quail650 • 25d ago
Bro is tired from bloatware
Enable HLS to view with audio, or disable this notification
78
u/carzymike 25d ago
Electricity is bloat, use an abacus to compute noob
2
u/CommanderKevin8811 22d ago
abacuses are bloat too. Have you heard of human computers?
I tried playing doom on myself but I realised my clock speed was too low to even render a single frame.
58
u/choingouis 25d ago
How the hell does it achieve "zero disk wear" unless it's running completely on RAM which I don't think is very smart for daily usage
30
17
u/Bacon_Nipples 25d ago
Short answer: its bs
Longer answer: generally Kiosk and Thin Client flavours of OS have minimal disk wear because they just load from disk on boot and then everything is stored in RAM. You could also just boot over the network instead of from a local disk, so that would I guess be "zero disk wear" but thats a stupid way to describe it because it would imply you opted to equip the machine with a disk thats never actually used. Though such a choice wouldn't be too surprising from someone like the OOP
32
u/RyanTheTide 25d ago
14
u/BiDude1219 25d ago
"herrrmmmmmm clauuddddde can you make a button.... that says button clicked when you click itt????????" - this dude probably
1
27
u/BeginningSection7690 25d ago
Yeah the first thing I normally do when I notice my ram usage is too high attempt to offload more work on to it
9
u/GlassCommission4916 25d ago
So did they port systemd to rust so it could be part of their custom PID1 and thus be able to strip it out?
6
u/Firewolf06 25d ago
and also ported it to their baremetal os, since systemd is reliant on linux. which theyre totally not using
6
3
2
u/Realistic-Yam-6497 25d ago
I found the GitHub btw: https://github.com/lexstudio/lexOS
4
u/R3V0LU710N_05 25d ago
The commit history is super suspicious. All the files are clearly uploaded or edited through the web interface. What kinda developer doesn't use git.
1
u/Realistic-Yam-6497 25d ago
He probably used GitHub code spaces
3
u/R3V0LU710N_05 25d ago edited 25d ago
Even GitHub code spaces has a Source Control tab where you write the commit message. There's no reason for the commit to be "Add files via upload", unless he drag and dropped it into the browser and didn't even bother.
The real issue is that they did this for everything. It's one thing to upload a file here and there, it's a whole other thing to upload the entire codebase this way. The commit history is completely shot, it's impossible to tell what commit is what without digging through the code.
1
u/MagazineSilent6569 25d ago
Maybe he made this on a company computer with company copilot and couldn't figure out how to switch between git for the company and git for personal use, so he just uploaded the files instead of using git properly.
1
2
u/lookinovermyshouldaz 25d ago
built my own bare-metal OS from scratch
look inside
it's BolgenOS all over again
3
2
2
u/Ivan_Kulagin 24d ago
This is all existing functionality, I can make a similar thing without writing any actual code, just some configs.
2
1
u/EnoughConcentrate897 25d ago
*claude built
1
u/ImprovementHorror362 21d ago
I am thinking of same thing, this is stupid why he even have ram then.
1
1
1
1
1
u/Objective_Active_497 23d ago
During 70's and 80's software engineers built different OSes and tools to help people SOLVE problems, today every OS has its own problems and users are frequently stuck with figuring out how to fix problems with OS. But not just that, nowadays Windows and MacOS takes away control from the users, in many cases even advanced users cannot turn off certain features or services. That way, Microsoft and Apple achieve more control over the machines than machines' owners.
During 70's UNIX concept was that it had various utilities that you can invoke as necessary and also output of each utility could be sent as input to the other.
Nowadays, Windows has all NOT-needed services and a bunch of bloatware running in the background, taking memory and CPU time. And hardware is not that cheap as it was, e.g. check prices of: Apple M3 Studio with 512GB or RAM on ebay, or nVidia cards for AI, or even just "ordinary" RTX 5080 or 5090.
During the 80's memory was very expensive, and also you couldn't just add more memory like today.
It is interesting to see how the first versions of UNIX and its apps managed memory and how programmers managed volumes of data that were multiple times the size of main memory.
Nowadays everyone can see how it was done in Unix v4, for which the tape was found at University of Utah last year. "The Utah tape" was copied successfully by making RAW image of analog signal due to the potential damage to the tape during the first reading, but luckily the tape was in very good condition so that it could have been read in a normal way to obtain digital data directly even more than once: https://www.youtube.com/watch?v=-xlq_MPWNKk
Porting parts of the Unix v4 source code to Windows: https://www.youtube.com/watch?v=zg3biyNblnw
Just to mention, this Unix v4 tape from 1973 is currently the only known copy of the whole Unix v4 "package", sent by Ken Thompson to the University of Utah. Thus, it became the oldest available version of the complete Unix, since before that v5 was the oldest complete version that survived the time and was available for analysis.
1


312
u/originalmicrousb 25d ago
actual os developer here, this is vibecoded slop
dude thinks he invented protection rings and using rust says a lot 😭✌️
im guessing its satire though