Hacker Newsnew | past | comments | ask | show | jobs | submit | Pomfers's commentslogin

Prions are attracted to or at least congregate in and around nerve cells. That's why as they spread around, they always eventually end up in the brain.


Do we know if prions are especially attracted to nerve cells, or if nerve cells are just a typical cause of death by prion disease?


Depends on how you define LEO. I think the commenter was probably thinking of Very Low Earth Orbit, VLEO.

First graph is a list of deorbit times: https://www.nasa.gov/smallsat-institute/sst-soa/deorbit-syst...

As expected, higher altitudes, higher mass, and lower surface areas correlate to longer deorbit times. It looks like altitude has an extreme effect on deorbit times, as you can see the 100 KG satellite (solar min) deorbits in a little under 2 years at 400 KM, but over 15 years at 500 KM. So 1.25x the altitude results in 7.5x the deorbit time.

Stuff at 800-1000 KM can take centuries to deorbit, and that's within both NASA's (under 2000 KM) and the ESA's (under 1000 KM) definitions of LEO. There is a definition for VLEO of under 450 KM, which would have fairly short deorbit times, and therefore a relatively mild Kessler Syndrome.


Indeed. It's something investors should worry about for the data centres and if SpaceX will bankrupt itself instead of giving them a return on their investments, but it's not something where general space enthusiasts should worry about Starlink: the timescale for orbital decay is long enough to kill a company, but short compared to a lifetime.


No one understands everything here. When it comes to software development, everyone I know says they're only really knowledgeable about what they work on. Most other areas, they'll have at best some passing knowledge of. It's like how doctors become specialists in just one part of the human body. There's maybe 5 people in the world are are a qualified dermatologist, endocrinologist, neurologist, and cardiologist at the same time. It's the same thing with engineers.


That's not true. I understand most of things posted and discussed here. And I'm not some amazing 100X programmer. Having a CS degree definitely helps.

However HN is definitely skewed towards the obscure and the nostalgic with a dash of genetics and cosmology. Most of the programming happens in traditional languages - C/C++/C#/Java/Javascript/PHP/Python, and HN would make you believe everyone is writing functional stuff with monads and functors in LISP or Erlang.

The community is great though, very knowledgeable.


Your impressions 1 and 2 can both be correct, and there still be an association between artificial sweeteners and type 2 diabetes.

It has been shown for decades that this association exists, it's establishing cause, and causal direction that's hard. Does consuming artificial sweeteners cause diabetes? Or does having diabetes cause the consuming of artificial sweeteners?


No, the "Potential for reverse causality cannot be eliminated" means that instead of artificial sweeteners causing diabetes, causality can be reversed: Diabetes causes the intake of artificial sweeteners.

All these studies just show an association, but can not prove the direction of causality. For whatever reason, the idea that diabetic and overweight people deliberately seek out zero sugar sweeteners so that they can enjoy sweetness without making their situation worse just doesn't seem like a plausible explanation to them.

Personally, if you can't definitively prove something is bad for you after 45+ years of research, I just don't care anymore. People can occasionally drink Coke regular without issue, I wouldn't be worried. Most of the time, diabetes is not caused by merely occasional consumption of sugars.


"I have never seen a thin person drinking Diet Coke."


I've seen a lot of people getting Xiaomi air purifiers. Had no idea they put DRM on the filters, and they cost more. Really glad I went with Winix years ago, cheaper filters that last longer, and no DRM. I don't get why people can't just put a reminder in a calendar in the future to let them know to replace the filter instead of dealing with this stuff.


AMD consumer cards do compute, but do not have a developed or well supported ecosystem (ROCm is a mess).

Misguided segmentation or a high level architecture problem however, it is not. A specialized product will perform its specialty better than a general purpose product. There's minimal demand for a card that's good at both compute and gaming. These people exist, but are few compared to those who only care about one or the other.

The benefit of splitting GCN into RDNA and CDNA was immediate. Comparing the Radeon VII (GCN 5) vs RX 5700 XT (RDNA 1), you'll see that they're fairly evenly matched on gaming, trading blows with the Radeon VII slightly ahead when averaged. The RX 5700 XT takes a very heavy loss on compute benchmarks. Both are TSMC 7nm, but the RX 5700 XT has fewer shaders (2560 vs 3840), a smaller die (251 vs 311 mm2), and lower power consumption (225 vs 300 w) which shows how much more efficient it is at gaming. That much lower power consumption and noise, and a couple hundred dollars cheaper made it a much more compelling card for gamers.

CDNA cards are apparently missing components needed for gaming, like render output units. Hence, they have no official support for DirectX, OpenGL, or Vulkan. I've never seen anyone get one of these working for gaming. In exchange, their compute performance is so good that a number of companies are buying these cards over Nvidia's, despite the overwhelming CUDA ecosystem. In 2013, a GCN based supercomputer made the top 100. That is the one and only GCN based system to ever make the top 100. Compare to now, where 8 of the top 10 most energy efficient super computers use CDNA accelerators, as does the number 1 fastest supercomputer outright.


> These people exist, but are few compared to those who only care about one or the other.

They're few, but they're very important, because 5 years from now, they will be the ones working for the companies that AMD will want to sell their compute cards to.

The reasons you cite may still be more important. I'm not saying AMD made a bad decision. I'm just saying that neglecting the path from hobbyist to professional (or student to professional) is not insignificant.


Consumer cards that are okay at compute do that job almost as well. And RDNA meets that bar... when the software works.


> I'm not saying AMD made a bad decision

No, just a cool trillion dollars of market cap are saying that, nbd :)


AMD's compute oriented cards used to come with displayport output, but I haven't seen one of those in a long time. These cards are definitely GPUs in that they can handle graphical workloads, but I don't think anyone is trying to make them work for video games or the like.


I heard a rumor somewhere that Stadia ran on MI25s - not sure if that's true but certainly there have been a lot of them floating around on eBay in the past year.


IIRC the graphics hardware was dropped in CDNA architectures (MI100, MI200, and MI300). For example, I don't think there are texture units.


AMD still sells firepros (EG the W7900) like that.


That's just a variant of the RX 7900. It's an entirely different architecture.


My choice as well. I like the colors my camera puts out mostly, so I only really need to make a few adjustments here and there. DarkTable doesn't even conform the RAW to the preview JPEG, so I end up wasting a bunch of time just getting the RAW to look normal in the first place. RawTherapee also seemed far more intuitive to figure out.


Yes, before editing. All the other RAW editors I've seen, including the other FOSS editor RawTherapee, will automatically adjust the sliders to match the embedded preview JPEG. DarkTable doesn't do this, all my RAWs load in looking really strange.


You can set presets, I don't. Because the jpeg version doesn't have to be the "right" version of the photo (there actually is no such thing as right, hence my preference to start from a pure raw file).


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: