metaphor

Not just any snake...these are Burmese pythons[1].

[1] https://youtu.be/0wXeRStcG6A?t=173

Consider water spinach[1]---a.k.a. swamp weed in Florida, but also known as kangkung amongst Asian households---to which the USDA apparently classifies as a "noxious weed". It can be prepared for consumption in many ways, but I especially love it in a Filipino sour soup dish called sinigang[2].

If you want to buy this "noxious weed" in Florida (or anywhere in CONUS, for that matter), you'll need to skip Walmart and make a trip to your local Asian produce store, where it can be found profitably sold for pennies on the dollar. Why? At face value, the ethnic majority simply don't consume this green, and in any case, its natural supply far outstrips market demand, making it far less attractive for most sellers to justify retaining inventory.

Now consider pythons that have invaded the Florida Everglades. Suppose the market for this were to flip in a similar way that beef oxtail has: a cut of "trash" meat historically shunned by the ethnic majority (but favored by certain ethnic minorities and the poor for its low cost and exceptional flavor) which has seen a major market repricing upward driven by the popularity of certain ethnic dishes. Or how short ribs (kalbi) and skin-on pork belly (samgyupsal) have seen significant upward repricing and market availability as KBBQ restaurants grow in popularity throughout the country (fire suppression equipment and commercial fire code compliance being primary enablers around my locality).

In the case of beef/pork cuts, the market simply recognizes value and prices are set consistent with supply/demand...it's just optimizing margins on an existing large scale process.

But would such a scenario really work out when the source of meat is an invasive species that Florida is looking to wholesale exterminate? I mean if the market wins, the state has a problem; and if the state wins, it's difficult to imagine how the market naturally materializes. Gator tail in the South is the closest proxy equivalent I can think of, but for all intents and purposes, it's a novelty dish which has hardly gained market traction at scale.

I don't know...random food for discussion, so to speak.

[1] https://en.wikipedia.org/wiki/Ipomoea_aquatica

[2] https://en.wikipedia.org/wiki/Sinigang

Source?

Consider a contractor in a software maintainer role; accounting for this as capex makes zero sense.

> What if your neighbours climb on your roof and start banging on your windows at night?

Worth noting that in the US, castle law[1] is ardently defended and not something to be tested by FAFO.

[1] https://en.m.wikipedia.org/wiki/Castle_doctrine

To be fair, the concept of iced tea as an objective desire is considered the provenance of blasphemous original sin by a not insignificant percentage of natives where the parent hails from.

> La choy is to soy sauce what Maruchen is to real ramen

Oh come on now, surely Maruchan deserves a bit more credit...at the very least, no one is breaking the bank while desecrating their soul.

In contrast, at my local Walmart, a 15-oz bottle of La Choy is priced +50% higher than its (subjectively superior) Kikkoman alternative of the same size!

Yes[1].

This includes every major appliance in my primary home...and HEPA air cleaners too.

[1] https://www.energystar.gov/about/federal-tax-credits/air-sou...

Bad faith argument, and certainly not the case for homeowners intending to leverage certain tax incentives[1].

When I tapped this two years ago, it was for a ducted heat pump system replacement where the only immutable requirement was that the system had to have earned the ENERGY STAR label. SEER2 rating was a mere secondary consideration that had no impact on credit qualification; 14.8 was my saddle point.

At the time, ductless mini-splits had to be ENERGY STAR certified and SEER2 > 16 to qualify.

[1] https://www.energystar.gov/about/federal-tax-credits/air-sou...

Paraphrasing this[1]?

[1] https://github.com/pytorch/pytorch/pull/132936/files#diff-98...

Nope[1]:

> Is Julia named after someone or something?

> No.

[1] https://docs.julialang.org/en/v1/manual/faq/#General

(2023)

Previous discussion: https://news.ycombinator.com/item?id=35858778

The complaint[1] by the SEC against Qwest during the dot-com bubble...you decide if Nacchio serving "a trumped-up 6-year federal prison sentence" was appropriate.

[1] https://www.sec.gov/files/litigation/complaints/comp18936.pd...

Curious how the blog post published April 10 goes out of its way to highlight Speedometer 3.0...almost 2 weeks after 3.1 was released[1].

[1] https://browserbench.org/announcements/speedometer3.1/

High probability the target interprets prompt as routine automatic update notification and does nothing.

It's not clear what would actually happen, but it also seems plausible that the hotplug event gets triggered by merely (un)plugging a USB-C charger while folio is closed.

The exploit struck me as exceptionally nasty given screen mirroring[1] is one of Supernote's attractive features.

Am I correct in understanding that the public debug key firmware signing faux pas was plugged in Chauvet 3.21.31 [2], while the unsolicited/unauthenticated P2P file transfer hole was plugged in the most recent Chauvet 3.23.32 [3]?

The changelog doesn't list any updates released circa December 2024 despite disclosure timeline noting that Supernote "...plan[ned] to address the issues in the December update."

[1] https://support.supernote.com/en_US/Tools-Features/1791924-s...

[2] https://support.supernote.com/en_US/change-log/changelog-for...

  [System] Enhanced security for system upgrade verification.

[3] https://support.supernote.com/en_US/change-log/changelog-for...

  [Supernote Linking] Enhanced the security of transferring files through the Supernote Linking feature.

That's all motherhood and apple pie, but it's a red herring with no basis in pragmatic reality (i.e. not how the calculus of utility-scale power generation industrial planning/ops works), and wholesale disingenuous to posit that even a residual percentage of those households---say, asymptotic to the proportional marketshare of Firefox users in the state as a comparatively low friction proxy aspirational target---would even attempt this hack...to say nothing of its trade-offs or implied liabilities to the end user iff successfully implemented...or how Comcast would be incentivized if adoption achieved a critical mass that made the hack observable (either technically or monetarily) on their end.

Not to discredit the author for sharing the insight, but the hard sell of saving 2W consumption simply isn't a prime mover here. If anything, mitigation of implicit side channel RF interference when the hack is paired with a OpenWrt router (as the author apparently intended) makes a lot more compelling sense...but now we're talking about bootstrapping an additional appliance into the setup, rendering contextual discussion of power savings objectively moot.

My condolences...looks[1] painful.

[1] https://www.pge.com/assets/pge/docs/account/rate-plans/resid...

Uhhh, sanity check: If you lived in a state like Hawaii where the cost of residential electricity approaches outrageous territory (i.e. ~$0.50/kWh), then you'd be hard pressed to save $1 per month trimming -2.4W nominal consumption with this hack.

Perhaps I'm just naive, but this struck me as the buried lede:

> ...but even in bridge mode, the gateway broadcasts several hidden SSIDs with no option to disable the radios.

I use --- to represent em dash in prose here, e.g. [1][2]. The behavior is just a residual of long time exposure to TeX.

[1] https://news.ycombinator.com/item?id=41833665

[2] https://news.ycombinator.com/item?id=41774199

Was thinking the same thing as well. I've hunted in this region a long time ago (on a private hunting club in Ocala) with an old friend from uni who explicitly advised that wearing gloves while handling wild hog was an absolute safety must because of infection risk.

> Accurate (within 3deg F) weather predictions

Sniff test: ASTM E230 standard tolerances for the venerable Type K thermocouple is +/- 2.2°C or +/- 0.75%, whichever is greater.

Expectations are in need of recalibration if anyone thinks a single number is going to meaningfully achieve that level of accuracy across a volume representing any metro area at any given point in time, let alone two days out.

To be fair, it's probably naive to blindly assume that a company like Philips, with a long history of litigious behavior, isn't playing patent continuation games.

Perhaps less widely known is that if you market a commercial product that actually uses PWM to modulate LED intensity, you're liable to be litigated against by Philips for patent infringement?

Wild...yeah, I know. Heard that from a buddy in Austin over a decade ago. Vaguely recall that he had to redesign using some sort of current driver instead to avoid the legal encumbrance.

More details in the DoJ press release[1].

[1] https://www.justice.gov/usao-mn/pr/federal-jury-finds-feedin...

I'm a R&D plebeian; not my job. We have a lifecycle management team that monitors metrics---e.g. system availability, failure rates, spares inventory, obs, etc.---and postures as risk/budget considerations permit.

In the aggregate, these legacy systems are on the right tail of the bathtub curve quickly approaching EOL, hence their modern replacements already being fielded. As legacy systems are decommissioned, reclamation buffers the spares inventory pool. Push come to shove, cannibalization in the field keeps most balls rolling at the cost of diminished availability/throughput.

Based on a sample size of 2 legacy systems in our lab that saw daily use over the past decade, things definitely broke, but I don't recall the production Alpha hosts every giving up the ghost beyond CMOS battery replacement nuisance.

We still have a few support Alphas laying around just in case, but virtualization[1] on commodity bare metal effectively renders them redundant.

[1] https://www.stromasys.com/solution/charon-axp-alpha-virtuali...

From the article:

> The BG29 chips will be available in 5 mm × 5 mm QFN and 2.6 mm × 2.8 mm WLCSP form factors

That "wireless oral health monitor" example is a concept from Lura Health[1] that integrates a marginally smaller BG27 (2.3mm x 2.6mm WLCSP)[2].

[1] https://lurahealth.com

[2] https://www.silabs.com/applications/case-studies/small-bluet...

To clarify, assume in good faith that pivot in context means compelled towards involuntary action---i.e. unexpected loss of local data, as opposed to a matter of routine shift in workflow---where the remote forge is being tapped for its secondary function as off-site backup.

The question was more intended to probe remote UX resilience near the limits of pain when faced with massive git repos which primarily capture binary assets/artifacts.

Paraphrasing UX expert Johnny Lee:

  UX = P_Success*Benefit - P_Failure*Cost

...and yet with every new generation of tech, it's never surprising how the hype cycle results in a brazen dismissal of the latter half of this fundamental relationship.