It does, a bit. If I wanted to make a rubber some keyboard, I'd have startup costs in the thousands of dollars range for molds and such. But I can make PCBs for a mechanical keyboard for only $30.
The cost of mechanical keyboard is far lower in low quantities.
There are some similar statements: "mechanical keyboards aren't much better than normal keyboards", "mechanical key switches aren't much better than normal key switches", to which "some mechanical keyboards are much nicer than standard keyboards" aims at the former.
I feel to say about "mechanical keyboard vs standard keyboard", these niche ergonomic keyboards should be considered.
I only recently discovered these weird keyboards. So I figure that's as good an excuse as any to extol these benefits. (And complain about how weird a standard keyboard is!).
Capital required to come up with a keyboard design is a much more minor factor.
I'd guess the hardware is the problem. Most antennas I've seen on access points are larger than the entire Pi Zero W. While I'm no radio expert, I'd expect APs to use the smaller antennas if they were capable of being as good as bigger antennas.
Ah, that reminds me of an article someone here linked to a few years ago: [1]. That claims the efficiency is -3.5 dB compared to a typical -1.25 dB dipole in dedicated wireless equipment. Not bad; the difference is only a factor of ~2 in power for x8 reduction in size.
> Compressed sensing in this context is made possible by the fact that the signal’s frequency content is highly sparse.
The fact that the signal is so regular is what makes this possible. You're sampling the same signal many times, far more than twice the frequency of the highest frequency.
If the signal's frequencies changed over time or if there were more frequencies in the signal, this wouldn't work or would require far more data.
I haven't read 100% of the article, but from skimming over it, I see no mention of p-traps [1]. How exactly are these fumes getting into places when there's essentially an airlock in every drain connection?
From the article, it doesn't sound like it's coming out of the drains. It sounds like chemicals are being released when they fill pipe sections with steam which then dissipates into the surrounding air.
The fumes exposure is probably just due to the person's proximity to the job site, not from a plumbing connection.
I'm familiar with vents, but indoor vents are basically one-way air valves. I don't know if this is required by code, but it's definitely common practice (you don't want poop smell coming out of your vents)
The article states that airborne particles and gasses can travel quite a distance to affect people that aren't in the localized application area of the CIPP sites.
A p trap can dry out. In my case the resulting sewer gas introduced 120ppm of CO into that bathroom, which started to dissipate and set off CO alarms on the next floor up.
This is common knowledge among the fire fighters here. They knew what was up once they found it.
So, how could VOC be entering buildings where they’re doing CIPP retrofit? Now you know.
The website is under active development at the moment and their are incomplete parts. For the code links please take a look at the following tutorial on GitHub at the moment.
I found this comment: "In V3 the hobby field is explicitly disallowed. This is not backwards compatibly as it breaks previous field that did contain a hobby field" in https://cuelang.org/docs/usecases/datadef/
So if you add a field, you break existing code that doesn't know about the field.
This is wrong. CUE has optional closed schemas marked by a double colon. The V3 entity you’re talking about is explicitly declared to be a closed definition and therefore disallows unknown fields in entities that claim to accord to the V3 type. Not all definitions are closed.
Even for those that you choose to close, it’s a matter of having different code for different definitions. The claim that it just automatically breaks isn’t true even when closed definitions are used.
BTW, this feature speaks to CUE’s intended purpose as a configuration language. It is (or at least can be) nice to ignore unknown fields in transmitted payloads for forwards and backwards compatibility. But if I’m trying to configure some software and misspell a field, I probably want the configuration file to fail validation, not have the software run with an unintended configuration.
Are you familiar with the concept of context? It's helpful because it allows easier communication by not requiring words to mean the same thing at all times.
In this case, it is helpful because we can scale our understanding of the poster's disappointment to allow us to not have to consider how it might be disappointing relative to, say, global thermonuclear war or a first kiss, but only need to think about it in relation to the other topics of discussion.
I highly recommend using context whenever communicating.
I can be disappointed when viewing a web page while simultaneously being disappointed in humanity's collective response to climate change. Context matters.
Yes it would be nice if the browser prompted more suspicion in those cases when a self-signed cert changes than when one is simply used for the first time. (Theoretically the changing of a regular CA-signed cert shouldn't prompt any suspicion, but I wonder...)
The cost of mechanical keyboard is far lower in low quantities.