quicklyfrozen

That's not a realistic goal. Even at 20 MPH, a well timed jump from between parked cars could leave someone closer then your reaction time.

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.

For dracut, the spec file defines the source as http://www.kernel.org/pub/linux/utils/boot/dracut/dracut-049...

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.

Geoff doesn't count :-)

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.

We don't do it directly, but there are certainly municipal water supplies that are downstream of other town's waste water treatment plants.

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.

Yeah, I agree that the sound system in the theater is painful (do they think we are all deaf?).

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.).

Not everyone understands the principle of the nest egg.

Being social and connected with our family unit is also deeply embedded in our DNA.

Honestly clicking on the article just leads to paywalls or ad laden disasters that just consume my CPU (or complain if I have an ad blocker).

HN just works, so it's a lot less work just to read the discussion here.

I've seen the exact same scenario play out with an e-commerce site using MySQL.

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.

I'm not sure there's any possible way to achieve a real lockdown in the US when half the population doesn't even believe in the severity of the virus. How would you enforce it?

And a strict lockdown would require most people to have enough supplies in place to last the few weeks, which is likely an impossible demand for our supply chain to meet, and also impossible for those who live paycheck to paycheck.

How is it dysfunction to keep your devs focused on the tasks you've already identified as the most important?

I can't imagine how producing a PR for this with test cases, getting it reviewed, then shepherding through a typical QA/Staging/Prod pipeline would take less then a day for any code base of reasonable complexity.

Perhaps it wouldn't literally take 8 hours, but the focus shift of working on this would likely keep a dev from making much progress on other issues that day.

We started down a road with more home cooking through things like Visual Basic. I remember seeing lots of useful things built by non-professionals during the era of VB 6, but it seems like nothing in the web era has filled that void.

Personally I'm usually looking through a bunch of responses trying to find the one I'm interested in, and that workflow sounds pretty awful.

Or use the same haptic feedback as the touchpad.

Right now I have 6GB for VMs (for ~12 docker containers) and 8GB for various IDEs and editors. Probably typical for those on my development team. Surprisingly Chrome isn't even the top ten for memory footprint on my laptop.

So far 16GB has been fine on this 2017 MacBook. Wouldn't turn down 32 though :-)

It's probably still normal to talk on the phone while driving in Boston, but it's no longer legal unless hands-free.

I lose my job for supporting the wrong candidate?

They were always going to struggle to get app developers to port to Windows Mobile, so I'm not sure it was ill conceived to provide a single target for desktop and mobile, with the hope that more developers would take the time to support all form factors if they could use a single code base.

It was a gamble that enough native desktop apps would remain for this strategy to pay off, but they lost to web and electron apps.

This can be fun if it's a particular client request that causes a hard failure, and the client retries several times before giving up. Before you know it, all your instances are restarting and no traffic is being handled...

So fail early, but not too hard.