They do specifically mention that some fixes may come to RHEL first.
I'm sure they'll try not to break binary compatibility, but as it appears to be somewhat experimental and targeted to developers, breaking updates may occur. Isn't that the point of this distro -- so such testing can take place before updates are rolled into RHEL?
So, fine for a developer workstation, but I don't see how it can be stable enough to use in production.
CentOS will be useless as a replacement for RHEL. Without the guarantee of binary compatibility, any CentOS Stream update may break your locally installed applications.
And I only recall CentOS significantly trailing RHEL at the major version updates (e.g. 6 and 7). Other updates seem pretty timely, and the major version lag doesn't leave me vulnerable.
I can see this being useful for developers who are building something that needs to be compatible with the next major release of RHEL, but I'm not sure who else it will be useful for.
That's the whole point -- it's continually receiving updates that never break binary compatibility with existing apps/packages. For example, it's a safe target for vendors to target with binary packages, whereas CentOS stream won't be.
rpmbuild will download the sources listed in the spec file, apply the patches, and execute the build instructions to produce RPM and SRPM packages. The SRPM will contain the "as built" source tree.
The RPM SPEC file in that repo will have a pointer to the actual upstream sources for the package. This is a typical scenario -- they are not re-hosting all of the sources to build a Linux distro, just the build steps needed to pull, patch, and build upstream sources.
I know someone who ended up hospitalized from accidentally taking two over-the-counter meds that both contained Tylenol. It just doesn't take that much to cause damage.
From what I've seen with older relatives, if you're able to stay mobile, you'll stay mobile longer and have a better quality of life. I don't think it's impossible to have housing and shops together and still have parking within a reasonable distance -- for example a town center with parking lots a couple blocks from the main street.
Personally I find paper wrapped items from the local deli fine, but I'd be pretty skeptical of any food products shipped only in paper -- too easy to contaminate.
I'm assuming that third parties are a lot more likely to join an external channel on a platform they're already using (and are more likely to be responsive as well).
I think all the existing integration are examples of an indirect network effect -- companies wouldn't invest in providing them if there weren't already users on the platform.
The number may be crazy, but Slack does benefit from network effects. For example, my company has many bots/integrations with other systems, years of institutional knowledge, and connections with multiple external vendors.
Switching would be painful so there'd have to be some pretty compelling reasons. (And who's got time to recreate all our custom emojis? :-))
It's a lot easier to click a button on the AWS console then to get approval to buy new capital equipment, or to get approval to use a new vendor (for which we'd likely need legal review, security audits, etc.).
As an IC you probably have more time to fully read emails, esp. those from your management chain.
I like to lay out the decisions I'm going to make if I don't get feedback, if possible. That seems to prompt feedback when feedback is required -- it seems the human desire to fix mistakes is stronger then it is to answer open ended questions. It likely gives the reader some context as to why you need the information as well.