m0dest · HackerLangs

Yes, the decision to rely on modern CSS is more like serving restaurant food that contains cilantro. The predominant failure mode is partial credit.

The quality perception of this user segment is relative, too. That visitor who is using a version of Chrome that is 4 years stale? Their experience on the rest of the web was not pixel-perfect today. Many sites are inexplicably buggy for them. They might even be used to having to switch devices to complete some tasks.

Continuing to surf the web with a long-unpatched browser is also overtly negligent [1]. That negligent 2% of users is not a protected class. As such, you might observe that this 2% of users contributes only 0.2% of revenue / engagement / value and make a self-interested decision to stop supporting them.

[1] Except brief windows of time when old Apple devices continue to get Safari security updates without getting feature updates. Not relevant to the author's CSS nesting example.

m0dest

6 個月前discuss

Even if it's just the build server, it's really hard to defend just having 1 physical server for a project that aspires to be a core part of the software distribution infrastructure for thousands of users.

The build server going down means that no one's app can be updated, even for critical security updates.

For something that important, they should aspire to 99.999% ("five nines of") reliability. With a single physical server, achieving five nines over a long period of time usually means that you were both lucky (no hardware failures other than redundant storage) and probably irresponsible (applied kernel updates infrequently - even if only on the hypervisor level).

Now... 2 servers in 2 different basements? That could achieve five nines ;)

m0dest

8 個月前discuss

So, product idea: A powered "cold storage box" for M.2 SSDs. 2 to 8 M.2 slots. Periodically, an internal computer connects one of the slots, reads every byte, waits for some period of time, then powers off. Maybe shows a little green light next to each drive when the last read was successful. Could be battery-powered.

m0dest

8 個月前discuss

Yeah, regardless of how one feels about the design decision to fail without fallback, the messaging seems like an oversight.

m0dest

9 個月前discuss

It looks like Mozilla does use DNS to verify requests to join the list, at least.

  $ dig +short txt _psl.website.one @1.1.1.1
  "https://github.com/publicsuffix/list/pull/2625"

Doing this DNS in the browser in real-time would be a performance challenge, though. PSL affects the scope of cookies (github.io is on the PSL, so a.github.io can't set a cookie that b.github.io can read). So the relevant PSL needs to be known before the first HTTP response comes back.

m0dest

2 年前discuss

It probably makes sense to start isolating build processes from test case resources.

comments