Netbooks. Jfc that performance of a mid-tier smartphone whereby they'd become unusable in a few years for anything heavier than lxqt or some tiling wm, a simple music player like audacious, vim and static websites (accessed only using something lightweight like Netsurf, Badwolf or Palemoon as well). I don't remember what happened to mine but I'm pretty sure that even mpv with no scripts would drop frames like crazy on FHD x265 matroska videos. I'm so glad that ultrabooks started to become more affordable and nowadays I'd be able to buy an i7 t440s for the price of my acer aspire one back in 2011.

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.

typescript is a linter

on chromium screen sharing works flawlessly though.

continued existence of capitalism does that already

try https://www.composingprograms.com/

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.

Also one really good practice from pre-Copilot era still holds, that many new users of copilot, my past self included might forget: don't write a single line of code without knowing it's purpose. Another thing is that while it can save a lot of time on boilerplate, you need to stop and think whenever it's using your current buffer's contents to generate several lines of very similar code whether it wouldn't be wiser to extract the repetitive code into a method. Because while it's usually algorithmically correct, good design still remains largely up to humans.

If it ain't gonna replace any of the existing keys, then IMO great. One more key for modal editing, tiling WM ricing, suckless embracing, Luke Smith watching nerds to use in mappings.

Also don't get me wrong. Molly might be written by less experienced programmers. And if it was written from scratch, it could be very likely it would contain more vulnerabilities per 1000 lines of code than standard Signal app. But it's mostly just it's a hardened superset sans some nasty stuff. I'd compare that more to how Calyx or GrapheneOS are to plain AOSP than how some low maintenance random custom ROM from XDA with fuckton of bells and whistles that will leave your bootloader unlocked is.

I advise you stop using Signal Desktop immediately, they keep the database key in plaintext. Exposed over 5 years ago and still not fixed. Frankly I find this pretty pathetic. Making this safer could be as simple as encrypting such files with something like age and perhaps regenerate the keys on a frequent basis (yes I know full disk encryption is somehow a viable solution against unwanted physical access. But instead, they'd rather focus on security by network effect by adding shiny UX features instead of fixing infrastructural stuff, like improving trust by decentralization, not requiring phone numbers to join, or adding support for app pasphrase (which is available in case of Molly, along with regular wiping of RAM data which makes things like cold boot or memory corruption attacks harder)

Yeah they did a very clever thing for the past decade or so, by slapping their illuminated logo onto their laptops, then aggressively contracting TV studios to have the actors use Macs