Guessing absolute failure rate previously not encountered by current graphing tool, incorrect scaling factor. Or, it was decided at some point that always reporting 0.000XXX% failure rate, even if correct, didn't offer an intuitive metric, so zeroes were intentionally truncated.
A physician relative pointed out the Dutch healthcare system as a compelling, hybrid public/private alternative to strict single-payer schemes. Gist of his recommendation was that single-payer systems may not be the silver bullet they're touted to be, and that alternative models are being tried out. I.e., viable solutions may turn out to be hybrid healthcare systems, where negative effects can really only be minimized rather than eliminated. https://en.wikipedia.org/wiki/Healthcare_in_the_Netherlands
A third way is the ~20 state governments who've subscribed to this model peddled by ALEC, barring municipalities from deploying infrastructure, on the grounds of preserving competition. Given the typical size of incumbent providers, this instead has the effect of preserving duo/monopoly, which critics argue is its intended purpose. https://www.documentcloud.org/documents/1908390-alec-model-m...
The ability to negotiate healthcare benefits as a group is indeed a popular justification for unions in fields not historically associated with union labor. Freelancers Union is an example, in addition to others mentioned up-thread. https://www.freelancersunion.org/benefits/
Quoted below is an except from a listserv discussion with a WISPA committee member working to draft that org's FCC filing. I'm sharing this, to fill in details on the assertion of "uncertainty in regulation" that is being bandied about, i.e. that the assertion isn't devoid of substance. But again, I don't share this view myself, believing that the absence of any Title II regs at all bodes worse than the burdens they or may not impose.
------
The Commission asked what the definition of ‘reasonable network management’ should be. The original (2010) version called for “reasonable network management” and defined it as:
"A network management practice is reasonable if it is appropriate and tailored to achieving a legitimate network management purpose, taking into account the particular network architecture and technology of the broadband Internet access service."
In the Title II order this was changed to:
“a practice that has a primarily technical management justification, but does not include other business practices.”
What does “other business practices" mean? From an engineering standpoint I can design and build a network that never requires ’network management'. We used to have that network - it was called ‘circuit switched’ and it was an engineering marvel. What I can’t do is build that network today and deliver broadband at competitive prices without some degree of oversubscription. The level of oversubscription is ultimately a management (and economic) decision. If all network management practices are then ‘business practices’ it becomes very difficult to decide what network management can be justified as ‘primarily technical’.
The valid arguments I read from industry groups like WISPA cite significant uncertainty in what Title II regulations would actually look like in practice. Given that WISPA is basically a trade group of small ISPs, some mom-and-pop scale, burden of any new regulation is a significant concern. My personal opinion strays from this, since the incumbent ISPs that WISPA membership generally competes with stand to benefit even more from the tact of deregulation (and presumably make further progress in driving more of them out of business).
The sci-fi series Three Body Problem sustains the argument that intelligent civilizations evolve into being compelled to mask their existence from interstellar detection, as a matter of survival. General idea is there are always bigger in the ocean, and the time required for interstellar travel is so long that non-zero probability of any newly detected life being hostile becomes intolerable. I.e. civilizations survive over Gyr timescale by concealing themselves, and destroying any neighbors who make themselves observable.
Despite its immense size, Betelgeuse can be described as a "red hot vacuum." The density of its outer atmosphere / corona is very thin compared to our sun, so it's readily distorted into irregular shapes by the star shedding gas/material.
tinc is also a popular lightweight VPN, although it's targeted for embedded. It does nevertheless support the libreSSL fork mentioned upthread. https://www.tinc-vpn.org/
Counter-argument would be that permitting states to stipulate their own criteria for measuring bandwidth delivered would further motivate providers to build out infrastructure that actually delivers the quality of service they're claiming. (Or at bare minimum, compel more honest advertising.) Otherwise, providers will A) tweak their infra to spoof popular speed test methods, and B) lobby the FCC to soften the regs that apply to them. Indeed, they do both already. Your speedtest.nets are regularly skewed by providers siting its nodes inside their networks.
I hardly need 50mbit/s+ for residential use, yet I know perfectly well I'm not actually getting that bandwidth allocation by any meaningful measure. Running curl against cachefly routinely surpasses 50m, even during peak, yet transfers from other destinations will creep down to 10m.
Besides reasons already mentioned above (and adding my own emphasis on suboptimal power performance), CPUs have GHz-scale clock domains, thanks to pipeline stages that minimize the number of gates traversed on each cycle. FPGA designs often run at frequencies ~10x slower. While one could instantiate pipeline stages using FPGA's logic calls, it's badly inefficient use of silicon. Maintaining separate clock domains, on the other hand, also consumes lots of silicon due to needing to isolate the domains, to avoid injecting noise into shared power/ground planes.
It is true some modernist architecture hasn't aged well due to short-sighted deployment of the building materials and techniques available at the time. Frank Lloyd-Wright was particularly bad about this, and that could be attributed to the fact he was usually designing for ostentation. At the same time, there are modernist buildings demonstrating very intelligent choices over a the structure's long-term durability and maintainability. E.g. Bauhaus residences that put windows at the corners, to optimize on holes cut through exterior walls vs. natural light let in. Likewise for metal Lustron homes built during the 1940s in the US.
Agreed. Money can't buy everything, including experience and awareness gleaned from personally facing the problems such NGOs target. The knowledge accrued could demonstrate value later.
Access to useful wireless bands for mesh topologies is a hurdle. The unlicensed bands (e.g. wifi) are such precisely because they're generally junk w/r/t to propagation and atmospheric absorption. The licensed bands are unsurprisingly gated by license holders in a way to enforce exclusive access, which often does not correspond to full utilization of the available bandwidth. Especially so with license holders than just squat on their bands indefinitely.
There is very little about design and manufacture of ASICs that is cheap, unless you're selling them by the millions. Two previous employers evaporated because they couldn't sell enough units to recoup VC investment in building semi-custom ASICs. The kicker is that each employer was already selling a previous generation of their product using more plug-and-play, less custom, ASIC libraries. The customized next-gen products were intended to be more performant and power efficient, which they were, but they still sunk both companies.
Agreeing with ajross above. Indeed, Chris disclosing his legal strategy may prove unwise to his own case, but his experience is becoming common enough to be relevant to anyone who may observe (what they think to be) police misconduct.
Besides its concussive pulse, the weapon is designed to draw in air from underground/fortified structures in the blast radius. E.g. asphyxiate people hiding in tunnels. It no doubt will leave a crater, but my understanding is that the crater would be less than that left by a similar quantity of TNT.
Private practices would indeed have their expenses arranged in the fashion you describe, i.e. with those qualifying expenditures counted as business expenses before pass-through. The caveat is that titling the private practice as the malpractice policy holder, so that the insurance costs become business expenses, exposes the corporation to lability, not just the individual physician. For practices involving multiple physicians, or which own/rent property to operate a clinic, this liability exposure can be undesired. Relating from a relative who is a physician, who has been a contractor and an employee, I have to stress the general point that professional expense accounting for doctors is quite unique, due to substantial involvement of insurance and regulatory concerns. It's not easily relatable to other professions. Likewise, doctors, despite making very generous compensation, are often still frequently struggling with their employers/contractees, or with 3rd parties like insurance providers, pushing costs onto them. Since telemedicine doesn't really exist in significant form, doctors don't always have the option of quitting and finding better work in the same city/state.
These data would be more informative, were they also paired with vocational costs MDs also incur, usually unavoidably. Malpractice insurance, prep for board exams, for example. Note that the latter can include having to travel to conferences, or similar events, to stay current in the field, and there may not always be an employer to reimburse such costs. Likewise, insurance rates will vary between disciplines, eg. higher for radiology vs psychiatry.
Given that it's not economical for cloud providers to let too many of their customers monkey with resource provisioning, I gather such efforts on the part of the customer can only be so effective.
Under other circumstances I'd agree this is poor strategy w/r/t preparing for possible future legal defense. Detail here may be that Fowler may soon find herself gagged from disclosing further details, especially if surviving terms in her employment contract with Uber allow for it.
At least from NASA's standpoint, looks like they budget single-digit $Billions for human spaceflight, out of a yearly budget in the range of $18B. I'm not sure how cleanly that can be broken down per-mission, since stays aboard the ISS can now exceed 12 months. https://spaceflightnow.com/2015/02/02/nasa-outlines-fy-2016-...
There is a difference between shaping traffic to better fit the capacity available, and constricting traffic since you're incentivized to push alternate traffic from a business partner. The latter is what NN advocates are trying to discourage, and it does arguably mess with the 'level playing field' notion.
For code that is generally in open source land, you may be able to get some traction cross-compiling for x86 and using tools like qemu/virtualbox to test higher-level functionality. However, it's usually the peripherals and whatever high-speed serial links (e.g. wifi) that you need to get better visibility into.
Comment made in other threads is that this particular isotope of iodine is very short-lived (8 days) and a known product of uranium and plutonium fission. So, its source is assumed to be recent fission event, or medical radiotherapy generation. Any unrecovered material from defunct satellites probably no longer undergoing active fission.