This will probably sound crazy to some of you, but I believe the introduction of the boolean type was a mistake.
Every primitive type has a null value, and the "if" statement tests for such a value. Whether a value is true or false is a property of the value. Notice that "true" and "false" are adjectives, not nouns.
That is a simple, internally consistent model with one concept of trueness.
The introduction of the boolean type made this a lot messier: it makes "if" look like type coercion, and introduces two different ways to think of boolean-ness (as an adjective or as a noun) which you must hold in your head at the same time. For example, it became possible to compare things as equal to True or False, doubling the number of ways to express a condition: "if x" and "if x == True" are now very similar, but subtly different, ways to express the same thing. The fact that we have to talk about things as "truthy" or "falsy" as if these were different from "true" and "false" is a further illustration of the mess this has created.
If we had stuck with 0 and 1, we would have avoided all this confusion. It is imperfect but simple; what we ended up with is still imperfect and needlessly complicated.
I still have a printed stack of Python 1.5.7 docs from when I first learned the language.
The addition of boolean `True` and `False` were a huge improvement to the language when they were finally added in 2.3.
I'm not sure why you're making things more complicated than they need to be. Test for truthiness. Conditional statements already evaluate boolean expressions, you're not adding anything explicit by writing `== True`.
> If we had stuck with 0 and 1, we would have avoided all this confusion.
I don't see how. Indeed, using 0 and 1, the int values, as if they were boolean false and true created more confusion. First, int has more values than just 0 and 1--and all of them are "truthy". Second, treating 0 and 1 as booleans is still treating boolean-ness as a noun--but also confusing that with treating it as an adjective for those int values.
PEP 285, which introduced the bool type, gives other rationales as well:
Does it? "bank account has 0 dollars" and "no bank account" are different states. 0 cannot (should not) try to represent both. Same for empty string, empty list, empty set, they are data not nulls. Python has None for that.
But None has its own type; it's not a value of any of the other primitive types. Which makes sense if you use None to represent "no data present" vs. "data present, value is the null value".
Booleans are reductionist and likely harmful, as they allow programmers to avoid thinking in terms of the test they are actually performing: is this a member of some set? If the problem is reworked like that Booleans are superfluous (this representation could be compiled to something as performant as using Booleans).
I am not sure if that perspective aligns with yours.
Not sure why you're getting downvoted so much, but to put this thought into a somewhat broader context:
In an explicitly, statically typed language, bools might be useful as a standard small enum.
In what Python used to be, they weren't, not really.
But for whatever reason, declared typing is now an add-on to the language, and the people who like the verbosity of declared typing also, perhaps schizophrenically, like the terseness afforded by having a standard small enum.
The study calculates that 91.8 million all-age deaths, including 30 million deaths of children under 5, were prevented by USAID funding in the period from 2001 to 2021, and projects that DOGE's cuts to USAID will result in 14 million additional all-age deaths, including 4.5 million deaths of children under 5, by 2030.
The Harvard articfle is just PR for a documentary that focuses on an individual (IE, an anecdote intended to be emotionally manipulative).
As for the article, this is modelling, not data (both the retrospective and the predictive). There is no direct causation being shown. You simply cannot make a claim like "X million people will die because USAID was terminated" based on this sort of evidence. It's not factual. It's not logical. Just emotionally driven claims intended to manipulate public opinion.
> As for the article, this is modelling, not data (both the retrospective and the predictive). There is no direct causation being shown. You simply cannot make a claim like "X million people will die because USAID was terminated" based on this sort of evidence. It's not factual. It's not logical. Just emotionally driven claims intended to manipulate public opinion.
How would one (ethically nor not) perform a randomised trial of this kind of intervention? Like, the Lancet definitely hop on far too many bandwagons for my taste, but it's almost certain that the withdrawal of USAID will cause ~millions of otherwise avoidable deaths.
And ultimately, it's the choice of the US government and people whether or not to fund these programmes. Personally, I think that they are worthwhile, but others may disagree.
But really, you're holding the evidence required here to a very high standard, one that many things you believe would probably not meet.
Thanks, this is more thoughtful than most of the replies I've seen.
I don't think anybody proposed or considered running a randomized trial.
I feel like the evidence standard has to be extremely high if you're claiming that tens of millions of people are going to die in the next few years with the goal of blocking a program from being defunded. Otherwise it's just emotional manipulation- "fight the change by making up numbers that sound bad".
> I feel like the evidence standard has to be extremely high if you're claiming that tens of millions of people are going to die in the next few years with the goal of blocking a program from being defunded.
I mean, this is basically the evidence standard that we use for flu/respiratory illness deaths, along with lots of other hard to measure interventions.
Personally, even if there were no deaths due to USAID being removed, it would still have been a strategically bad thing for the US government to do, in terms of soft power.
Additionally, the US are noted in development circles for circular aid, in that they gave a lot, but then required it all to be spent on US goods, so it was more of a subsidy for domestic producers.
I do agree that lots of people just jump on these numbers uncritically, because of prior beliefs about Musk/Trump/DOGE, but it would be very very surprising if there weren't lots of avoidable deaths due to the cutting off of aid. Like, the same thing could have been accomplished in a much better way by tapering off the aid as programmes expired.
Also: nagging about the specifics of the README's tone of voice, while the 600-1000MB RAM usage drops to 100-250MB seems a little childish to me.
It's still open source! Just like in the pre-AI era they are welcome to submit a PR and improve it in the way they like it. The main dev seems very open to accepting help.
I don't see you publishing something which further reduces the memory footprint?
Given the project is open source, have at it! See if you can help improve it instead of complaining. This is a significant improvement and a cool project!
I run actual Winamp for my music streaming, and windows task manager claims it's using 4.1 MB.
Even that seems pretty high, but whatever, but given y'all are spending hundreds of mbs, I think I'm ok. Yes, spotify has features my subscription music service doesn't have... but the one I use lets me stream with Winamp.
I'm not complaining and it is a cool project (from what I can tell). But I think it's fair to say 200 MB memory usage is a lot without providing source code as a proof. Just by feel when you recall what were computers capable of when they did not have 100s of MB to spare.
I like the direction, but stewarded feels just a little too awkward to type or say to catch on. Perhaps "guide coded"? But it will be really hard to dislodge vibe coded from being generally applied to this concept, I think, in part because it is a catchy little term.
Could you explain the first step, "Manually Labeling Colors ? What did you manually label? I didn't quite follow.
From the way the article is written, it sounds like you presented yourself with a bunch of faces of completely random colours and then manually sorted them into two categories, "plausible skin colour" and "implausible skin colour".
But I feel like I must be misunderstanding, because I don't see why you would do that. Why wouldn't you gather photographs of actual faces and sample colours directly from the photos?
Every primitive type has a null value, and the "if" statement tests for such a value. Whether a value is true or false is a property of the value. Notice that "true" and "false" are adjectives, not nouns.
That is a simple, internally consistent model with one concept of trueness.
The introduction of the boolean type made this a lot messier: it makes "if" look like type coercion, and introduces two different ways to think of boolean-ness (as an adjective or as a noun) which you must hold in your head at the same time. For example, it became possible to compare things as equal to True or False, doubling the number of ways to express a condition: "if x" and "if x == True" are now very similar, but subtly different, ways to express the same thing. The fact that we have to talk about things as "truthy" or "falsy" as if these were different from "true" and "false" is a further illustration of the mess this has created.
If we had stuck with 0 and 1, we would have avoided all this confusion. It is imperfect but simple; what we ended up with is still imperfect and needlessly complicated.
reply