[-] pkill@programming.dev 4 points 2 years ago

the 'I' in LLM stands for intelligence

[-] pkill@programming.dev 4 points 2 years ago

fr the system is in such a deep terminal crisis that talking to people in their 20s feels like talking to pensioners since in countries like the US or UK the life expectancy is declining due to not being able to afford healthy food, stressful and precarious work, mental health crisis and addictions, worsening healthcare, climate change, moldy cramped housing, proliferation of larger and thus more dangerous cars, new zoonoses etc. etc.

[-] pkill@programming.dev 4 points 2 years ago

typescript is a linter

[-] pkill@programming.dev 4 points 2 years ago

a webpage that simulates a systemd shutdown when that one stupid service won't stop?

[-] pkill@programming.dev 4 points 2 years ago

on chromium screen sharing works flawlessly though.

[-] pkill@programming.dev 4 points 2 years ago* (last edited 2 years ago)

well in my experience it was opensuse tumbleweed or Manjaro that were significantly less stable, but perhaps my perception is a little bit skewed since I use artix and it's certainly not too rarely just the bloated, tightly coupled nature of shitstemd that causes some of arch's issues.

[-] pkill@programming.dev 4 points 2 years ago

continued existence of capitalism does that already

[-] pkill@programming.dev 4 points 2 years ago

hmm strange, maybe some applet but when I was using it on my 3rd gen i7 laptop it never went silent and the CPU usage could spike to even 20% when idle

[-] pkill@programming.dev 4 points 2 years ago* (last edited 2 years ago)

CENZOPAPA MENTIONED!!! xD! 🟨

[-] pkill@programming.dev 4 points 2 years ago* (last edited 2 years ago)
[-] pkill@programming.dev 4 points 2 years ago

I'm old enough to remember years of people complaining about overzealousness in closing threads as duplicate on forums, even when the issue might have been somewhat specific but the user could have just been unable to correctly recognize all factors at play with their issue (things like firewall, dependency versions and their configuration, environmental variables, hardware etc.) or the issue was actually caused by new bugs or API/ABI changes.

But at least there was some redundancy reduction and things were usually well categorized and tagged and many places actually implemented some pretty decent fuzzy search for similar existing issues. Instead we've ended up in both users and maintainers really wasting their time on something already resolved much more often.

If you don't have time/are too stubborn for that, good luck skimming through tutorials to extract the info you need and pasting/adapting others' code all while hoping there were no breaking changes since the snippets you want to use were published. At which point you might as well go ahead and browse type definitions and function signatures if you're lucky to use something written in a self-documenting style.

[-] pkill@programming.dev 3 points 2 years ago

no need to hide your beautiful black eyes 😍

view more: ‹ prev next ›

pkill

0 post score
0 comment score
joined 3 years ago