Please don’t take me as a GH shill because I’m not. I’m not sure we read the same email given your projects. Actions on GH runners are dropping in cost and there’s a new fractional cost for self-hosted. For the average user, especially those on GH runners, costs are going down. Looking at your repo, you haven’t run anything since July. Your workflow files use GH runners. Nothing in your history suggests you’re leaving the free tier so I don’t get this FUD at all. General Microsoft hate? Fuck yeah. Shitty GH service? Fuck yeah. Plenty of reasons to dunk but this was not one of them. M

I’m incredibly skeptical of the self-hosting email server claims. With the past 30 years of spam, most of the majors make it nigh impossible to do so. I know there are diehards out there that make it happen; it’s not as easy as it was 20 years ago though.

Edit: Very useful HN thread with multiple perspectives (not just my doom and gloom)

The big given example was gigabit throughput. Most consumers in the US, businesses included, don’t have access to internet infrastructure capable of multigig because of regulatory capture. Those that do are already using multigig hardware which, unsurprisingly, hasn’t really changed much.

The current administration believes the same stuff. She left with the admin change yet agrees with things like the current admin’s approach to AI regulation.

My initial take on the sticker was the whole “fire exit git commit git push;” I do see this other perspective now

We’re just quitting without writing? Living very dangerously aren’t we?

It’s still just another type of ID so you can do lookups on it. Nothing would change. UUIDs are used all the time.

Note that the linked article answers your FOSS question.

I assume this is Poe’s Law in action. Elon historically doesn’t understand shit about tech so the commenter is just highlighting something that’s been GA for other tools for years.

This isn’t recent. This has been an ongoing thing for at least 20 years (if not longer; that’s just the earliest I remember having this convo). Yes, it cleans the wound by killing things but it also fucks up the healthy tissue around the wound (see other comments for a more scientific explanation). Having some in a medical kit is useful for other activities such as diluting with water for an ear rinse, diluting with water for various mouth stuff (rinse not swallow), and some skin treatments (again, diluting first).

Strange; the page is shilling for a product that doesn’t use raw HTML for its site.

This is just distributed functions, right? This has been a thing for years. AWS Lambda, Azure Functions, GCP Cloud Functions, and so on. Not everything that uses these is built on a distributed functions model but a fuck ton of enterprises have been doing this for years.

There are an unsurprisingly large number of Ubuntu 16 boxes in the clouds. A quick google even shows a Spring 2024 course from a major US university recommending 32-bit Ubuntu 16.

And as long as you don’t need simple access to most features such as volumes. The podman implementation on not Linux leaves quite a bit to be desired for anyone trying to do more than just run a binary wrapped in a container. I’m not throwing shade because it’s FOSS and anything is better than Docker. Only Docker will work for a production-capable dev environment on not Linux unless podman’s development has exponentially increased in the last year since I tried to move a shop to podman on not Linux.

As long as you’re on Linux, podman is superior and will do all of the things you’re asking about. If you need to also support Windows or Mac, Docker is the only thing that will work (although people have told me Rancher isn’t bad now for a couple of years).

I bring new software into my organization through two methods:

1. Someone has used it before
2. We are reasonably confident in our ability to use existing staff, possibly with a new expert hire or consultation

It’s pretty rare for a large org to do completely net new software. Training is usually a big deal if that happens. Massive layoffs are also a possibility (see enterprises being dumb about containers). Smaller orgs tend not to have this problem. If they do you can usually tell in an interview and just not go there. Devs are constantly experimenting with net new shit (current libs don’t do the thing; gotta find new libs). Again, smart leaders are open to this.

In general, staffing is a huge part of any of these decisions. You might not see the convo but it is most likely happening.

If someone doesn’t understand the difference between swearing at and swearing around, that’s a shitty environment. If I say, “that was a shitty fucking outage” I am using some filler for emphasis so my mouth can catch up to my brain. If I say “you’re a fucking asshole” or “don’t be such a bitch” or “that’s fucking sexy” I am not being professional and I deserve some training on how to not be an ignorant walnut. Even with swearing around, I do think it’s smart to limit yourself to damnation, defecation, and simple fornication rather than gendered swears. There are also some places it’s not wise to swear around, such as client-facing roles because many of the people you will see don’t understand that swearing around is not swearing at.

I once lost a job after the onsite interview. I wait to swear until I I hear them swear. Apparently my use of “fuck” meant I was going to blow up and be a terrible person to my peers. Two years later I started running a department doing the thing I was interviewing for and my staff tends to be fiercely loyal. I’d argue my swearing speaks for itself and have shaped my professional attitude toward swearing around around this experience.

I work in tech and I’m quick to police my language if necessary. I’m also concerned about relative comfort (eg I try really hard not to blaspheme around some Christian peers). I do not swear at people. I do not work in a super corporate environment. YMMV.

I like study (you can find the full article online) and I think there’s been more research down this path in the years since.

I catch a lot of shit for my distaste of GPL. I don’t think I should be able to tell you what you can and can’t do with my source code. I’ve released it into the wild. If I put caveats on it it’s not really free.

This issue has nothing to do with SaaS and everything to do with regular software updates (which are not limited to SaaS). Change the package to “LibreOffice Writer” and the delivery to “pacman -Syu” and suddenly the same bug has the potential to hit me. Hell, I have (well, had) floppies fresh from the store that introduced bugs into existing software back when I was a kid. Bugs will always exist and there isn’t enough regression testing in the world to ensure they don’t happen in the future.

All of your SaaS points are correct they just don’t apply here. We should be mad about the lack of testing in this instance.

That’s not all GNU/Linux though. Either the OP doesn’t understand a very common container OS, Alpine, doesn’t use systemd (also Void Linux and others outside the container space) or it’s something else.