People have eaten whole grains throughout human history. Diabetes was quite uncommon.
Excess sugars and processed grain is new, not whole grains.
Meat isn't nutritionally complete. You get scurvy with just meat. All meat diet isn't great for your kidneys either.
The amount of animal protein in diet like we have today was inaccessible for most farming communities which did not have diabetes like we do today.

That's a rather big leap in logic.
Eat less animal protein. Eat more legumes. Legumes are a complex package of protein, complex carbs and fiber. They are the healthiest diet for metabolic syndrome.

They produce about 2% of emissions of beef of equivalent nutritional value.

Are insects that almost no one finds appetizing, more "market-efficient" than legumes like Soy?

I know. I mostly live in US.
I largely stopped buying prepared food products except when I am away from home.
I cook everything myself and carry a packed lunch.
In late forties, I have a BMI of 21 even with a relatively sedentary lifestyle, all because I avoid ultra-processed foods and simpler carbs (not keto).

I bake bread. That sugar is supposed to be an amount immediately consumable by the yeast. Not much should be left behind.

I don't consume any dessert on a day to day basis, just for infrequent occasions. No cup cakes for me. The last donut I had was in 2019.
But I do want a sweetener for coffee and for my breakfast protein shake. My fruit intake is a bit high and I don't want any more added sugar.
If I don't do a sweetener, I have to do savory, where I need to account for sodium. I want to keep both sugar and salt intake low, even though I do not have any markers up yet.
If a small amount of sugar is fine, so is a small amount of a sweetener.

"I built most of the UI in C directly, meaning that each UI component had to be manually constructed in code," says the anonymous WinGPT developer. "I was surprised that the set of standard controls available to use by any program with Windows 3.1 is incredibly limited. You have some controls you'd expect -- push buttons, check boxes, radio buttons, edit boxes -- but any other control you might need, including those used across the operating system itself, aren't available."

This is a rather amateur attempt. The best RAD tool for Windows 3.1 was Delphi. With Delphi, it was trivial to construct a good looking UI that does HTTP with Delphi. You get lots of "controls" and the code for a project like this is minimal.

> Have you ever visited the salad idle in a supermarket? No, probably not. I doubt you've heard of the concept of exercise either.
> I'm sure you and all the other fat whales stuffing their fat faces with burgers would love to believe diet has no effect
> for your sack of lard physiques.

Do you think any of this language is productive? All you had to do was list studies that countered his claims, rather than assert with insults.

RTA.
"Apart from in articles that are specifically about AI"

What the LLAMA leak did was create a free experimenter community. You no longer needed an institutional affiliation. The skills the community developed with it, even if the model itself isn't free for for-profit products, will carry over when a totally unencumbered model is released. You can be sure that there will be a future model trained with public money will be released from EU or elsewhere with research tax dollars.

Falcon has a better license and so will LLAMA as Yann LeCun indicated. We should reasonably expect to see completely unencumbered model this year or the next, at most.

> I think most Python is written by amateurs who don't have to maintain it.

Technically true. Python was designed as a teaching language. It is probably the easiest language you can teach that is also completely practical. So yeah, it attracts a lot of first time programmers. That used to be BASIC in the decades past. First time programmers do write bad code.

Python code that you would encounter in recognized libraries, like the ones included in Anaconda, are all quite cleanly written and are very easy to read. I also find nearly all scientific code written by non-professional coders to be quite readable. It is by far the easiest language to read when written by even moderately experienced programmers because it was designed to read like pseudo-code.

> But it is unsuited to real world work where code might be expected to run for decades

Also true. Nobody picks Python for projects intended to run for decades. It's meant for learning, scripts, ever evolving projects like web projects, scientific code and so on. Nobody should pick it for write once and forget it for decades kind of code. That's just not its domain. Of course, that would happen from time to time unintentionally. Do you prefer to read Perl code from a couple of decades ago instead?

> there are different types of whitespace and invisible characters which do in fact turn up in real files

You are supposed to just use 4 spaces for indentation.
https://peps.python.org/pep-00...

Your problem is noob code, not Python. All noob code has its own set of issues. Good luck tracking pointer errors in noob C code and so on.

The alternative to noob Python code is noob Perl code, not professional Rust code.

The syntax is fine. For something designed in 1991, it is remarkably elegant.
Performance was not a design priority for Python. It was always intended to be used with C etc.
If it bothers you, try Julia instead. It was designed with more modern functional, numeric and performance considerations and principles.

I didn't check, but why wouldn't it? Except for the Python 2.7 to 3.0 transition, all Python versions are compatible with previous versions.

> You've never had to do any programming as a job, have you?

Really? You think people don't have Python as a programming job, especially when it has been around for decades and is at the top of the popularity boards?

> In the real world, code had to be edited under uncertain circumstances quite often, and usually when doing so time is an issue. Having code fail to work because the editor at the end of three ssh hops isn't set up for whatever magic invisible formatting the fucking retarded language insists on is not acceptable.

No more frustrating than code failing because a brace or a semi-colon is missing. For those of us who used Python as our main language, finding incorrect indentation is as effortless as finding a missing brace.

> Braces cost nothing, do they? They make the parser easier to write.

Braces save effort for language implementers and cost user effort.

> So, why not just fix it? Why is it such a problem for the language team to just make the text clearer?

It is already very clear; it just isn't to you. Perhaps you lack enough experience with it.

> Could it just be ego?

Yes, it could be yours. Python wasn't designed for your preferences. But it generally suits the preferences of its intended users just fine. Personally, I want to see the off side rule anywhere it fits. People appreciate different things.

https://en.wikipedia.org/wiki/...

As an analogy, many can't get used to the Lisp syntax. It exists for a reason. If you can't grok it, just move on. Don't assume Lisp programmers are stupid or irrational because you can't get used to the parenthesis. I am not too comfortable with it since I use it infrequently. My editor is also usually not setup to best handle lisp syntax when I run into it. It could be an annoyance, but Lisp just isn't going to be "fixed" for that. The parenthetical syntax serves a purpose, just as significant whitespace does, whether you appreciate that purpose or not.

In Python's case, you just need to have a few lines around to paste into your editor config. An extra step but not a huge deal. As a professional, you are expected to deal with such things. It should be no more tedious than setting up auto-format in that editor for other languages.

Python was conceived in late eighties and first published in 1991. Still complaining about significant whitespace, and idea that originated in 1966, which is in its fundamental design decisions, is like complaining about pointer syntax in C or begin and end blocks in Pascal. It's not going to change.

https://en.wikipedia.org/wiki/...

It's not the first and it won't be the last language to adopt it.

The only abomination here is your inability to appreciate things for what they are. The world isn't centered around your preferences.