It’s more of an issue with torrent seeding. You need to be able to accept incoming connections to seed, so you need a VPN/router to allow incoming traffic to a certain port to reach your torrent client.

So, not a problem for leeching, but if you are trying to meet ratio requirements, could be a big problem.

Sports gambling is just terrible for everyone except the bloodsuckers that run it. Sports teams don’t want it because it incentivizes cheating / rigging games. Personal bankruptcy and domestic abuse skyrocket when people lose money they can’t afford to lose. Now the apps feed an unstable addiction literally all day long.

Thanks to the Supreme Court for pulling a bullshit ruling out of their collective asses in 2018 that makes everything worse for average Americans.

Shit, I don’t even gamble and I’m just sick of their logos and ads all over every thing when I watch a game. Used to be they had “Gambling Prohibited” up around the stadium, now they may as well own the teams.

Pace makers keep you from dying so they’re sort of on a different level of need. Also, if corps did planned obsolescence on one, you’re probably not around to buy another.

If they were invented today, they would definitely have a predatory subscription model for “monitoring” your heart, or require occasional maintenance at cost to the end user.

The prequels were redeemed? That’s news to me.

I’m with you on 1 and 2, but “reduced lingual skills” I think is a bit of a stretch. Becoming fluent in another language takes a lot of effort and people only do it if they have a good long term reason.

I think it’s more likely this would cover the vacation / short term business case that is already covered by human interpreters (or apps already) instead.

I agree. I have become more amenable to things like Flatpak or Podman/Docker to keep the base system from being cluttered up with weird dependencies, but for the most part it doesn’t seem like there’s a huge upside to going full atomic if you’re already comfortable.

I wouldn’t do a mailing list these days, but as someone who spent the early part of my career interacting with devs that preferred this method, it’s actually pretty ergonomic by a 2005 standard. A message thread aware, text based email client that can turn messages into patches in a keystroke makes it actually pretty comparable to modern code review…

I think it’s hard for younger devs to get this because they’re used to email being stuck in a crappy, unthreaded browser interface or Outlook etc. (which are terrible for mailing lists) and most collaboration taking place in code review and chat platforms like Teams/Slack but for decades before these were feasible, email was the way…