Comments URL: https://news.ycombinator.com/item?id=50121458

Points: 1

# Comments: 1

The first cancer-related post - https://jakeseliger.com/2024/05/25/the-one-year-anniversary-...

Bess is an ER doctor, but even with all that medical knowledge, navigating cancer care seemed difficult.

So those with no medical knowledge from themselves or family or friends may have a much more difficult time.

Comments URL: https://news.ycombinator.com/item?id=50081054

Points: 72

# Comments: 6

But the above example shows that the body doesn't treat food in that manner - the relatively low carb, higher fat cheese didn't smooth out the higher proportion carb count of the toast.

In the paper, the largest carbs for the ultraprocessed meal was instant mashed potatoes, while the non-processed meal had bananas as the largest carb source followed by craisins/cranberries.

The high carb foods in the unprocessed meal are paired with fiber.

The high carb foods in the ultraprocessed meal are NOT paired with fiber.

The fiber slows the rate of carb intake.

Same thing occurs with protein - same amount of ground beef and steak, ground beef meal will result in faster amino acid ingestion than the steak meal. No idea if there are any pros/cons of the faster ground beef ingestion, but there is a difference in how the digestive system processes the two meals.

see https://www.asus.com/displays-desktops/mini-pcs/proart-mini-...

Asus also lists support for 4 displays and multiple SSD slots while Microsoft supports 3 displays for their dev box.

Not sure about the Ethernet port though. Maybe they expect the user to use a USB port for wired networking?

see https://www.microsoft.com/en-us/store/configure/surface-lapt...

see https://www.techpowerup.com/gpu-specs/rtx-spark-n1x-6144-cor...

But many of the specs on that page are estimates, but given this is a mobile-specific SoC, you can assume that the perf-envelope is lower than the DGX Spark SoC.

The top looks like a crumb/dust magnet.

from the main RTX Spark Dev Box page,

  "Surface RTX Spark Dev Box features an anodized aluminum body with 1,000 air vents built into its grid chassis—a nod to its 1,000 teraflops of compute performance."

Why is the headphone jack on the back???

I think there are two buttons on the top rear left of the box - I'd hope power and reset buttons.

The pics for the Microsoft Surface Laptop Ultra are pretty dark, especially around the ports, as well. I don't see an Ethernet RJ45 port nor is any listed under Key Tech Specs for the Laptop Ultra.

The engadget article just mentions "Ethernet port" for the RTX Spark Dev Box - no speed rating. see https://www.engadget.com/2280520/microsofts-surface-rtx-spar...

The DGX Spark has 10G Ethernet, so you'd hope for about $1K less, you'd still get 10G.

Comments URL: https://news.ycombinator.com/item?id=50000600

Points: 12

# Comments: 10

Very user-hostile.

from https://pubmed.ncbi.nlm.nih.gov/42578920/ (CrM is creatine monohydrate)

  Results: CrM supplementation without exercise training and diet intervention increased lean tissue mass, strength, and muscular endurance while promoting favorable changes in selected blood lipids, HbA1c, and selected markers of cognitive function and memory. Creatine supplementation during an exercise and weight-loss diet intervention increased lean tissue mass, promoted a greater reduction in body fat percentage, and improved muscular strength, endurance, and selected markers of cognitive function and memory. Supplementation was well-tolerated.

  Conclusion: CrM supplementation with and without exercise and diet intervention may help middle-aged and older adults maintain muscle mass and strength while favourably affecting selected markers of health and cognitive function. Individual cognitive and biomarker findings should be interpreted as exploratory.

  https://www.hacktron.ai/blog/hacking-openai

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

The reviews were ~90% 1 & 2 star within the first month of the FitBit Air release.

Three months later, the app has improved to ~80% 1 & 2 star reviews. At this pace, they'll be on v3 of the device when app reviews are decent...

They force everyone to move over to a different app when the replacement app doesn't have all the features/reliability of the old app.

Genius.

Garmin released the Cirqa band at $199 w/o compulsory subscription a few weeks ago. I may switch to that if the FitBit Air acts up.

  Now, our lawyers have made the totally unrelated point uh that we cannot legally agree to contracts such as terms of service or conditions while incredibly innebriated.

Take that LG legal dept.

see https://www.youtube.com/watch?v=6IFVTcM28KA&t=358s

Companies (or their consulting agencies) had tons of webdevs - working on their company public and internal websites, but not many native smartphone devs. Those were the days when people who completed the Stanford iPhone programming course were snapped up lickety-split.

But everyone was clamouring to have their own smartphone app for all the smartphone platforms (well, iPhone, Android, maybe Blackberry)

Hiring enough smartphone devs to fill multiple smartphone-specific dev teams would be like trying to build multiple AI development workstation on the cheap these days.

In the late 2000s, people realized they could write an HTML/JS/CSS website and compile to an app for each J2ME/Blackberry/iPhone/Android platform that would "serve" the website. So their webdevs could be converted to smartphone app developers.

Hey, if you planned your website well, you could use the same business logic for your website AND your smartphone apps.

That was the elevator pitch.

You'd need an actual (maybe two) native smartphone devs for each platform to handle any areas where the marketing didn't meet reality 100%.

But that was doable versus hiring multiple native smartphone devs for each platform.

And in the late 2000s, there seemed to be a lot of potentially viable smartphone platforms - iPhone, Android, Blackberry, J2ME, Windows Phone, Palm's webOS. But we know now that in a few years, all but two would wither away.

Even with native APIs exposed via JavaScript, there were obvious problems with these webview apps. The apps were passable if the app didn't require much user interaction or computation.

Projects like React Native and others tried to reduce the amount of webview usage and increase the amount of native UI controls used.

The mobile platforms themselves aren't going to improve their platform-specific webview to make it easier for webdevs to mimic the "native" experience. Why would they?