There's a good chance you have other options. Regardless of how you feel about the company's head, Starlink would probably be one of them, with likely better performance than you're dealing with on ADSL.
But you cannot just sue a company because their network connected software doesn't work well on slow networks. Let alone a project like OpenSSH. It would be like me suing a game studio because my PC doesn't meet their listed minimum requirements to play the game.
Hey, it is one thing to buy a new computer, it is another thing to ask people to move.
A better analogy is a bank redlining neighborhoods. The cost to run fiber to difficult rural locations pays itself easily if you look at a 25-year time span and is an order of magnitude less than building a new housing unit on the West Coast.
One half of my comment was actually about how you most likely have a better performing alternative option right where you already live. And even if you didn't, they're not asking you to move. You could argue they're not even asking you to use their software, you're electing to.
It's OSS with no warranty. You can compile it yourself with the option disabled. It's only ever on for pty connections (physical user with a keyboard), there's no added traffic for ttys.
So it's AWS Fargate with a different name? That's cool for cloud hosted stuff. But if you're on prem, or manage your own VPS' then you need SSH access.
Except you've replaced something good with something worse. IPMI really isn't an improvement over having SSH to the system. It definitely has more security holes.
Can you SSH into broken grub? Can you change BIOS settings?
Also giving access like that outside your home network is not a good idea. So security issues does not matter that much.
I didn't say not to use IPMI, I said it's not a security improvement over SSH. For exactly the reason you point out, giving access outside your home. Nothing wrong with exposing SSH provided you take it seriously and know what you're doing. Nobody in their right mind would ever put IPMI on anything but a protected isolated network.
Telling someone they're biased must be the most low-effort comment there is. Everyone is biased about any subject where they have even a nuanced self interest in. And in your case, you didn't even specify which part of their comment was allegedly being affected by bias. Nor did you acknowledge your own bias.
"which cost almost nothing for low traffic" you invented the retort "what about high traffic" within your own message. I don't even necessarily mean user traffic either. But if you constantly have to sync new records over (as could be the case in any kind of timeseries use-case) the internal traffic could rack up costs quickly.
"vastly superior to self hosting regarding observability" I'd suggest looking into the cnpg operator for Postgres on Kubernetes. The builtin metrics and official dashboard is vastly superior to what I get from Cloudwatch for my RDS clusters. And the backup mechanism using Barman for database snapshots and WAL backups is vastly superior to AWS DMS or AWS's disk snapshots which aren't portable to a system outside of AWS if you care about avoiding vendor lock-in.
Not the person you asked, but I think it comes down to past experiences/family environment/etc. Theres poking fun at someone to signal "i like you anyway"... that is real. There's also people who cross the line with their words, and use "i was just joking" as an excuse to be cruel.
If someone has experienced a lot of the later, it makes sense that they don't really trust the former.
Not OP. It's not about the words or the intentions, it's about the fact that we can talk about anything in the world, do any activity together, and you want to do something I'm not comfortable with.
That said, I understand relationships are about give and take. I couldn't be in a romantic relationship like this, but I'll indulge my friends or my cousins. I have a friend who engages in "countersignaling" often. Our connection is generally worth the uncomfortableness, but sometimes it is unbearable.
With age Ive found myself much more comfortable with folks "being mean, but in a friendly way" as they intend it. When I was younger though, I never understood why folks didn't instead just "say the nice part." Like, if your friends are always glad you join them even if you're always late, making fun of you for being late with a big smile can still feel pretty bad for you. Much better to say "hey please don't be late" and also "we really enjoy you spending time with us."
With age Ive come to see that for reasons I don't understand, lots of folks have a massive aversion to saying clearly the things they appreciate about the people around them directly. Eh, their loss.
I think there's a bit more to it than that. Being mean in a friendly way is sort of a sport, for some people finding a good quip is about the mental challenge of wordsmithing. It's easy, and not all that creative, to say "don't be late" and also with certain people can come across more negatively than just jokingly berating them, believe it or not. It sounds more serious. Something like, "glad you made it, Leland! We were just posting a GoFundMe to buy you a watch." Said in the right way with people you are very familiar with keeps a lighter tone, and less like I'm actually upset (even if I may be.) Not that I'd ever say something like that in a professional setting or to people I'm not actually strong friends with; those people just get a "glad you made it, Leland!"
It's also sort of the same reason shows like It's Always Sunny in Philadelphia are funny. When you're jokingly mean to a friend, you're being a bit of a caricature, an exaggeration. That's part of the fun of it, too. And why it can get a point across while keeping it light.
They're always more common in metro areas of the US. You must be from a relatively rural area and don't get out of it much.
That said, uh, the use of getting a taxi to drive you to or from the airport was just not having to park at the airport which generally costs a lot of money, and in certain areas is a little sketchy on whether or not your car will get cracked open while you're away.
That's a little reductive. I grew up in San Diego and went to school in LA and had the same experience with taxis - never took them. But now I use ubers in those cities whenever I'm there.
The US has tons of cities like this that I imagine would have issues with taxis - all parts of the bay area peninsula / east bay, cities in Texas, Denver, etc. Most cities are not like the NYC/Boston and even in places in Chicago, unless you lived downtown likely didn't see taxis driving around.
I think everyone knows and silently understands that the people responding/emoji-ing in those channels all day every day are doing so at the cost of work output, and that there are a lot of people working that aren't typing away about the last audiobook they listened to. I think you've created a stressful situation out of something that isn't inherently stressing.
Generating business value is not your only responsibility, though. Most companies expect you to be a team player, to stay in touch, to communicate across departments, and so on.
So depending on your work environment, communicating and responding quickly may be implicitly expected and not conforming may lead to stagnation in your career.
The opening story is about how the narrator was replaced by AI, but trades workers cannot. And that doesn't strike you as setting up AI to be central to the article?
But you cannot just sue a company because their network connected software doesn't work well on slow networks. Let alone a project like OpenSSH. It would be like me suing a game studio because my PC doesn't meet their listed minimum requirements to play the game.
reply