277 karma · joined May 15, 2020
Anyway, honey has a higher concentration of fructose so it has a lower GI than table sugar, but this difference is quite moderate (a few percent) - it seems to get overstated a lot on the web. Honey is basically refined/processed fuel produced by bees - and on evolutionary time scales it has been in use by humans about the same as sugar. Don’t get me wrong, it has chemical and physical properties that make it a beneficial sugar alternative - probably most of which is earlier satiety and therefore less consumption. If consumed in similar quantities it’s still going to make you fat. TANSTAAFL.
My grandparents are probably older than average... but the life expectancy was a fair bit shorter just 100 years ago. Most didn’t even get the opportunity to live long enough to have gastric cancer (smoked meats) or a second MI.
The flour you make French bread with is not found any more or less naturally in the environment than the sugar you get from cane or beet.
This whole thing about evolution and nutrition is entirely pseudoscientific woo.
If humans had to eat the same way as our ancestors (ie actual paleo, not some hipster fad diet) humanity would have died out long time ago.
The French thing makes this all the more ironic... I can’t imagine much more triumph in modern processing than the five mother sauces.
Clearly the American diet has a crazy oversupply of sugar... fructose, glucose, sucrose... at the amounts we’re talking about in the average American diet it doesn’t fucking matter (making the whole HFCS controversy always a joke).
This is mere speculation, but I doubt he would have appreciated Plan 9.
The fact is that there are/were some very effective C compilers for Z80, none of them free and far from it. By the time compiler technology advanced through the 80s and 90s the market for a non commercial optimizing compiler for the Z80 and 6502 rapidly diminished. gcc has never in its history been a fantastic 8 or 16 bit compiler. By the time egcs was merged even 68k was rapidly losing relevance.
It is totally possible with modern techniques to make a very effective optimizing C compiler for Z80, but who’s going to do it? There are very few hobbyists with both the chops and the time for something with little commercial value.
The answer is correct in implying that the PDP was better suited as a CISC target for C when optimization is not done.
For one, regardless of the GIL it is still possible to have races in multithreaded python code. You have to worry about RMW because the threads are arbitrarily preemptible at a bytecode boundary. This is not the case with asyncio.
Additionally you can release the GIL when making calls to C code. Asyncio is giving you concurrency by using nonblocking calls, you can’t run two CPU bound threads in parallel with it. But you can do this with python threads. So it’s not true that neither can accomplish more than the other.
Anti corporate soapbox or google job, please just pick one.
So basically the worst form of slacktivist hypocrites.
If you want to see how it’s done search the package name and AUR and you can see the build script right on the website.