Hacker News new | past | comments | ask | show | jobs | submit | room500's comments login

Some, but sarcopenia caused by rapid weight loss is a well known phenomenon. I think the tie to ozempic is a little overblown, but is is a real issue.

In a “traditional” weight loss strategy, you paired calorie deficit with an increase in physical activity (cardio, resistance training, etc). This increased physical activity helped protect you from muscle loss (your body tended to recognize that muscle was important so it burned fat at a higher rate)

With ozempic, people can lose weight without changing their sedentary lifestyle. Since your muscles are not needed, your body is free to grab energy from wherever it can. In some studies, almost half of weight loss can come from lean tissue.

Is it better to for an obese person to lose weight vs not lose weight? Absolutely. But it would be even better if they also changed their lifestyle to protect their muscle mass.


This doesn’t use multicast. Using multicast is essentially impossible unless you are the ISP or you just want to run it on LAN.

I don’t think Netflix has a fast lane anywhere.

Netflix does offer to give servers to ISPs to put in their datacenters. So if your ISP is seeing congestion on the IX links, it is entirely possible that Netflix still works fine (because the traffic doesn’t leave the ISP and is therefore not hitting the congestion). But that is not a “fast lane”


At that point Netflix should just provide its own VPN / internet access for paying users


Netflix puts servers in datacenters to cache content, so you access it much faster. Not sure what problem Netflix VPN will solve.


You're missing the point. Netflix is fast in these situations because your client can access the server in the ISP's data center and video traffic remains local to the ISP and doesn't traverse the congested link to the IX.

Other companies embed servers with ISPs as well.


But it is apples fault that they let the alternatives stagnate and refuse (until recently) things like RCS that would make SMS suck less.

It is clear that Apple considers iMessage a significant network effect and is not interested in having feature parity between iOS and non-iOS


I thought that is essentially what LLM's do? They learn what words/topics are associated with each other and then stream a response.

In some ways, this is proof that Gemini isn't cheating... It is just doing typical LLM hallucination


Well, sometimes. Sometimes not. https://arxiv.org/abs/2310.17567


Llm's can also do some exploring based on combinatoric play of learned elements.


The usual answer is that it gives time for the market to digest what was released before making knee-jerk trades on it.

Most brokerages (even Robinhood) allow you to trade after-hours. But the volume is lower so it can be more volatile.


I think you would see the opposite. You would incentivize going to grad school for a few years under a student visa. Universities could name their price.


> You would incentivize going to grad school for a few years under a student visa.

That's a significant change in immigration policy that's not covered in 'pause H1B'. I agree in principle that if you align the incentives like this, it would work out.


Nvidia Shield is Android TV. Netflix doesn't build for the Nvidia Shield in the same way that they don't build for every TV model from every manufacturer. They have an SDK that the manufacturers integrate.


It also can install apk packages directly without a store, so there is no barrier to platform adoption


250k is conservative for employee cost. A staff engineer at Google can reach 1 MM total comp. And add in all the overhead a company has (real estate, free food, perks, taxes, etc)

500k-700k is a little more realistic. 1500 employees across all domains (engineering, marketing, product management, customer service, etc) isn’t a huge number


It is consistent when the apps are consistent.

But it will not appear if the app opens the webpage as its own View (instead of opening Safari). In that case, there is no button and the user has to hunt for how to go back. And the user has no way of knowing whether an app will open Safari or will open the webpage itself.

iOS requires users to build muscle memory in learning how to use each app. Android requires users to maintain a back stack in their head to remember what came before. Switching between the two is very jarring.


If it's a full-screen in-app webview, there's a Done button on the top-left; alternatively, you can swipe back from the first page in the webview and it will close the webview and leave you where you were.

If it's a card webview, just swipe it down from the top edge.

> Switching between the two is very jarring.

I think that's the crux of the problem. Someone who's used to one style and has built muscle memory and some kind of hierarchy and ontology of the interaction with the system will have trouble with a different paradigm. That doesn't necessarily mean there's something wrong with either - they're just different, and some people will prefer one over the other.

Switching between GNOME and KDE, or vice-versa, has a similar effect.


To be fair, captive browsers are also a plague on Android apps. I despise them and especially so if there's no way to turn them off in a particular app.


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

Search: