digikata

I use an app called iCatcher which seems to have a directory of podcasts and will also let you enter rss/urls to download from host sites directly if the podcast creators distribute that way.

Been using it for years because it gives pretty fine grain controls over streaming vs downloading the entries, how many entries to maintain, how often to check, etc.

Generally, I would think the layout would put fuel towards the tips and people towards the cg.

Onshape is nice, web based, built by the creators of Solidworks. Free for hobbyists.

See standards proposals for various next gen links.

https://www.openfabrics.org/images/eventpresos/2017presentat...

System76 and Purism know something to work on improving now...

How does Nix handle areas with extensive package ecosystems? Python, Node et al? It seems like every distro/super packager has different compromises for this question.

The added cargo env variable pointing to the path of generated binaries is a nice quality of life fix. I think that was one of the first annoyances I ran into with cargo and binaries. It was minor but was like a little splinter that stood out from cargo's otherwise nicely integrated build and test capabilities.

I think there is little "getting lucky". If they also run an intense detect, test, and trace capability it might be effective. If they rely only on border lockdowns, or lockdown and lackadaisical test/trace then it would likely be insufficient.

The irony might be the massive human scale effort the NYT is putting in to gather and vet the data. The most interesting self learning side effort for this, might not be analyzing the data, but trying to automate the data collection from public sites checked against the nyt data.

I suspect if you laid transportation networks and commerce centers over the data there would be some alignment.

I had this question of software engineers with maybe access to social data. But I think I posted it at a poor time - no replies.

Ask HN: Usefulness of social network data for epidemic management?

https://news.ycombinator.com/item?id=22440114

But really it seems like a natural reaction to want to help, but I suspect if you aren't already tied in to a network of people/resources with a jump on the issues already, that coming up to speed is more of a idle thought than practical.

I imagine even larger gantry variant of this carbon fiber loom:

https://www.youtube.com/watch?v=j19na8LMBnE

The other thing is that for this area, Boeing the corporation is mostly a brand. The Apollo and Shuttle engineers are overwhelmingly retired or, err, passed. At this point, no company in America really has an edge with experienced employees with designing and qualifying a new human-rated space vehicle. SpaceX and Boeing were really pretty close to the same starting line.

And really SpaceX had a general experience edge in terms of coming off of designing a lot of wholly new and successfully working non-human rated space gear.

Boeing has experience in maintaining working space gear and process, but it's not the same scale of new product and process.

B2G for small startups can work out if you can supply something that the government needs under a small business area. Look at SBIR (Small business innovation research) programs. The need for a network/capital depends entirely on the topic, and I think thats true regardless of B2B or B2G.

Sustaining B2G after the SBIR wins may or may not work out - its best if the area ties into some longer term need/consumable so you have some businesses with the gov't after the SBIR phase ends.

My kid's pediatrician always recommended whole milk. Personally I liked the whole milk w/o additives but would compromise on Vitamin D.

Safety, very much like security, needs to be built in during the design phase - or you're trading off the development cost for an expensive retrofit while gambling with the risk of killing the project (or even setting back that entire class of transportation) by killing people.

Hey now I can claim to think like Elon Musk!

I imagine a semi trailer rigged with a battery, grid connection, and a set of chargers for seasonal surges. Maybe even a deployable solar panel array, but I suspect the PV panel would be too constrained to be much more than a show piece.

This will date me, but it reminds me of the vehicle from "Damnation Alley"

Sounds like manufacturing struggles. Hope they work their way through them and are able to deliver.

The book contains many references, but it's dense. I thought admin overhead tended to go to 15% because of ACA provisions of 85% spending requirement on direct care? I would likely have to do a fair bit of digging to compare how the scope is defined exactly vs an ACA definition. Makes for something of a perverse incentive if the companies want/need to route additional absolute dollars into their service depts - but I don't know how much it actually gets bent in that direction.

Its from a book, Code Blue: Inside Americas Medical Industrial Complex, by Mike Magee. The author is a Doctor and distinguished medical academic and past hospital executive.

Prices for care in Japan are basically systematically set by government committees.

https://en.wikipedia.org/wiki/Health_care_system_in_Japan

In contrast, in the US, there are 16 non-medical, mostly billing personnel per doctor.

The design may call out a specific material and how to manufacture it, say make this part out of 6061 Aluminum, and. mill it in this way. You can look up the standard properties of that material. But depending on how that material is worked, cut, bent etc, you would expect in come cases some changes in the material properties or just sensitivities to fatigue. E.g. if you cut a sharp corner into that metal, fatigue will increase in that corner over the life of the part, so maybe you specify rounded corner - but how much it makes a difference you won't do necessarily a whole specific detailed study on it unless its a critical part or corner. If it's milled, if the machine that day has a duller bit, maybe it heats up the part more, and the material properties shift a bit more due to the heating. All these and are controlled in the process, but are still little things lead to variation, and maybe the controls fail one day and some slightly different aluminum makes in into the process.

For critical parts on the aircraft, there is the backup of inspecting for aspects like accelerated fatigue just for variation of manufacturing, of environmental contributors, etc. It's a lot like security defense in depth - many layers of protection for lives (and aircraft industry trustability linked to profitability too) at stake.

True, the design is one important part, but the design can be 100% on, but the manufacturing and the operational inspections are important to present failures too. Variance from controlled manufacturing conditions can result in parts that basically look and perform ok at first, but are at risk of failing early, that's why aircraft have inspection schedules - that are sometimes increased due to increased cycles on some routes/airports.

(and of course there is the case of the part being damaged somehow, where some of the other comments have linked cases where this happened catasropically).

I don’t know about the legal or other regulatory logistics cost of operating a helicopter, but the physical maintenance requirements for helicopters are likely far far higher than a potential electric vtol vehicle.

What would be nice is a useful mail ML filter which would scan mail flagged spam to trigger a "are you sure this is spam, do you want to delete instead" question.

I wonder if the 40+ layer NAND chips would give a problem for this technique.

There were other considerations against musl there. I'd summarize them as targeting a desktop/server with kernel level system, or at least a mid-to-high end embedded system, has different code, memory, and optimization tradeoffs than the smaller embedded systems that seem to be targeted with picolibc.

Are you trying to do data lifetime analysis in V? I don't see that listed and to me it's pretty much Rust's key feature to enabling a high degree of memory leak and multithreading safety.