There is essentially zero chemical difference whatsoever in sugar vs corn syrup coke. sucrose disassociates in the presence of an acid into glucose+fructose simple sugars. Just being carbonated will disassociate the sucrose.
> sucrose disassociates in the presence of an acid into glucose+fructose simple sugars
Which tastes different from pure fructose. If you want to taste them side by side, you can absolutely tell the difference. (If you've done any endurance sports, you know what I mean.)
Once digested I agree that the health effects are suspect. But tastewise, fructose, sucrose and glucose are distinct.
I'm confused by your reply. GP's point is that they both dissociate into simple sugars, and thus it doesn't matter what the source is. And your response says correctly that sucrose tastes different than both fructose and glucose, but I don't see how this contradicts him. There is (practically) no sucrose left.
Are you perhaps thinking that "high fructose corn syrup" is predominantly fructose? The name is confusing, but it actually means that it is high in fructose relative to normal corn syrup, not that fructose predominates. HFCS is usually pretty close to 50:50 fructose to glucose, just like sucrose is:
How much fructose is in HFCS?
The most common forms of HFCS contain either 42 percent or 55 percent fructose, as described in the Code of Federal Regulations (21 CFR 184.1866), and these are referred to in the industry as HFCS 42 and HFCS 55. The rest of the HFCS is glucose and water. HFCS 42 is mainly used in processed foods, cereals, baked goods, and some beverages. HFCS 55 is used primarily in soft drinks.
I made no assertion about the taste of sugar vs. corn syrup. There are a number of products marketed as "Coke", and those products have different flavor profiles. Some use sucrose, some HFCS. It might be formulation, it might be packaging, freshness or bottling methodology. Maybe they don't tweak formulas for limited run products or in local markets like Mexico. I have no idea.
Even with the standard fountain formulation, there is a different/better flavor at McDonald's because of the standards they apply to each part of the supply chain. In a few weeks, depending on where you live, there will be two liter bottles of coke with a yellow cap. That's kosher for passover -- try it.
Just a cynical observation here, but its funny how the author still hangs onto the notion that it is "the best" despite that it de facto cannot be "the best."
Also, maybe dont rely on a poorly maintained app for making secure connections to your systems? Just me?
It is kinda weird how all the chat type tools all spit out such cheeseball language despite that the raw models almost never generate stuff like that. It honestly just makes me feel like the people making this shit are so caught up in their own hype bubble that it doesn't even register to them as abhorrent.
The chat models are optimised to keep people chatting. The attention economy is still the economy this companies operate in. Which is weird seeing as I'm paying hundreds of dollars per month to get good results.
woah hold on a sec. that's not how these clocks are actually used though.
It's a huge huge huge misconception that you can just plunk down an "atomic clock", discipline an NTP server with it and get perfect wallclock time out of it forever. That is just not how it works. Two hydrogen masers sitting next to each other will drift. Two globally distributed networks of hydrogen masers will drift. They cannot NOT drift. The universe just be that way.
UTC is by definition a consensus; there is no clock in the entire world that one could say is exactly tracking it.
Google probably has the gear and the global distribution that they could probably keep pretty close over 30-60 days, but they are assuredly not trying to keep their own independent time standard. Their goal is to keep events correlated on their own network, and for that they just need good internal distribution and consensus, and they are at the point where doing that internally makes sense. But this is the same problem on any size network.
Honestly for just NTP, I've never really seen evidence that anything better than a good GPS disciplined TCXO even matters. The reason they offer these oscillators in such devices is because they usually do additional duties like running PtP or distributing a local 10mhz reference where their specific performance characteristics are more useful. Rubidium, for instance, is very stable at short timescales but has awful long term stability.
> Google probably has the gear and the global distribution that they could probably keep pretty close over 30-60 days, but they are assuredly not trying to keep their own independent time standard.
Yeah I really don't understand why they went this direction as it builds considerable additional complexity directly into the application to solve a problem with an external component
I would have probably approached this by implementing a fix for the misbehaving part of k8s, though since there isnt a default LoadBalancer in k8s, I can't really can't speculate further as to the root cause of the initial problem. But most CNI or cloud providers that implement LB do have a way to take feedback from an external metric. I'd be curious why doing it this way wasn't considered, at least.
I had a look and this project is most definitely not open source. Nobody should be making that claim.
Changing the HN headline to soften the project's own bombastic claim isn't really the point of the argument. It would bhe better to highlight any project that is actually working on open source microscopy of which there are many. Flagged
Web search often tanks the quality of MY output these days too. Context clogging seems a reasonable description of what I experience when I try to use the normal web.
THIS. I do my best work after a long vigorous walk and contemplation, while listening to Bach sipping espresso. (Not exaggerating much.) If I go on HN or slack or ClickUp or work email, context is slammed and I cannot do /clear so fast. Even looking up something quick on the web or an LLM causes a dirtying.
reply