So this is strange, it popped up on Cloudflare’s RSS feed so I thought it was new. I’m guessing they edited the article but haven’t been able find a a diff against the original 2022 version.
For tracking uniques, why can’t we just set a “first_visit=false” cookie if not present on first request? The number of new unique users is then the number of requests that came in without that cookie in whatever time window. Expiration timeline left as an exercise for the reader (month, week, whatever).
This zero-entropy cookie cannot be linked to a specific person and would not require consent under any privacy law I think.
Guild-style unions seem to be about setting and enforcing cartel pricing, not work quality. At least for the construction and remodeling subcontractors I encounter.
Why can’t Postgres auto-tune these values itself in 2026? Microsoft SQL Server has mostly done a good job of this since about 2005. It will set parallelism thresholds, soak up as much cache RAM and CPU as the runtime environment allows, etc. It will give RAM back when the OS is under memory pressure, and schedule worker threads based on current resources.
A DB with a privileged supervisor process could generally detect how much free RAM, CPU usage/layout, etc at startup and re-evaluate periodically while running.
Illinois bans nearly all fireworks, not just commercial grade. You can basically only buy sparklers or tiny fountains.
You have to visit Wisconsin or Indiana to get anything that pops, spins, bangs, or flies. Even those little ground spinners are banned in Illinois and they are hardly “commercial grade”.
That’s generally too slow though; these things run in kernel space as they scan every I/O stream. Context switching and memory copies would kill performance.
This is market-dependent. We offer email OTP login for small business customers because it is “poor man’s SSO”. You’re basically validating the recipient is still at the company, able to receive at their work email.
Larger customers have IT staff and set up OIDC or SAML with us. We don’t add an SSO tax.
The Nagasaki “Fat Man” bomb was the same plutonium implosion design tested at Trinity.
The Hiroshima “Little Boy” bomb was the uranium “gun” design that was never tested before combat use. The physics and engineering were comparably straightforward so the scientists were very sure it would work assuming the Urnaium enrichment was pure enough.
Vena is one of the most popular enterprise budgeting/forecasting packages. It ships as a new-style Excel extension making Excel the UI for department heads contributing to a rolled up enterprise budget
Bitcoin has no dispute/chargeback mechanism in case of error or fraud. That inherent unsafety trumps just about all other safety concerns for a practical payment network.
Jira is justifiably derided, but Bamboo was truly Atlassian’s entry into the worst software of all time derby. Basically a random event generator masquerading as a CI/CD system.
I’ve observed airlines will do this as well if they have maintenance or gate queues. They will sacrifice 1-2 flights (hours late or even cancelled) to keep many other flights near on-time. Fewer angry customers, better reported average “on-time” metrics.
Concur. My kids and watched a “small” Falcon 9 launch from the mainland park nearest the pad at Cape Canaveral. The noise alone was astonishing; bring binoculars to see detail.
FIPS-140 allowed encryption using 3DES up until Jan 1 2024, and allowed certification of modules containing SHA-1 through the end of 2025. There is some transition-timeline nuance involved, but those examples are in general pretty horrible from a security perspective.