Python does have real threading. The `threading` module provides os-level threads and synchronization primitives. The only difference between this and multithreading in C or Java is that CPython's GIL prevents more than one thread executing bytecode at a time. This prevents parallelism, but not concurrency.
Note this does not mean that python code is thread-safe by default. At most, you can theoretically rely on bytecode operations to be atomic, which means you'll need to synchronize multi-threaded code with mutexes, semaphores and higher-level synchronization constructs.
> once you’ve taken your picture, you need to: 1) remove remaining silver halide that wasn’t exposed to light, 2) “fix” the remaining silver so it’s stable
Isn't that somewhat backwards? The developer converts exposed grains to metalic silver to create a visible image from the latent one, the stop bath neutralizes the developing solution, and finally the fixer dissolves unexposed silver halide.
It's not owned by the bank until you foreclose, after which it's most certainly owned by the bank.
As an aside, how often is it for the manufacturer/dealer to own the bank that issues auto loans. I got mine from Capital One, and I assumed most auto loans outside of the sketchy loanshark used car dealers were issued by the big national banks
In most states the financing bank owns the title to the car and is the "Legal Owner" as opposed to the "Registered Owner" who is the one who is buying the car.
The used market is likely different but for new cars from Dealerships, GM Financial, Toyota Financial, Ford Credit etc are Billion Dollar subsidiaries.
Is that true? In my state the financing bank has a lien recorded on on the title, but they are not the owner. Maybe that is the exception?
Edit: reading some other comments ... I'm talking about the traditional financed purchase of a car, not a lease. Agree that for a leased car (which is quite common now though I've never done it), the ownership stays with the leasing entity.
When you live in a title-holding state, the title will be issued to the registered owner/operator of the car, regardless of lien holder. Though your lien holder will receive a separate document verifying their connection to the loan, you will be in possession of the title itself.
There are only nine title-holding states: Kentucky, Maryland, Michigan, Minnesota, Missouri, Montana, New York, Oklahoma, Wisconsin. In the other 41 states, titles are issued to the lien holder of your vehicle until the loan is fully paid off.
It used to be quite common; at various times in its history you can make the argument Ford sold cars at a loss to help Ford Credit sell profitable car loans. Even today, Ford Credit (loans/leases etc) is responsible for about 50% of Ford's annual profits:
There have been quite a few years Ford made more profit as a "bank" than they did from making and selling the cars. If you get a new Ford from a dealer and request finance/lease options, its pretty typical for Ford Credit to provide the backing.
Yeah, one of the major uses of http/3 is that it can gracefully handle connection interruptions and changes, like when you switch from wifi to mobile, without having to wait for the tcp stream to timeout. That's a huge win for both humongous web apps and hackernews' idealized static webpage of text and hyperlinks.
The solar cycle is extremely important for premodern agricultural societies, since it allows predicting growing and harvesting seasons. If you're going by the Julian calendar and the Autumn equinox is falling on September 10, there's probably going to be confusion as to when the harvest should occur. In the case of the Gregorian Calendar, Catholic countries rely on the Spring Equinox to schedule Easter, and when it started occurring well before March 21, this made it increasingly difficult to synchronize the religious and secular calendars.
While it's somewhat true, most of the people in premodern agricultural societies couldn't read (especially those concerned with when the harvest should happen), and probably couldn't care less about dates in the calendar. Even today, weather and actual crop lifecycle plays a larger role in agriculture than particular dates.
Even if people were tracking dates, adjusting for a couple of days every 200 years wouldn't be that hard: nobody would remember the good old times when we did the harvest on September 22nd in 1234, and now we do them on September 20th in 1434.
Finally, matching up with astronomical events would sometimes put sidereal year (and day) at the forefront: a day that's ~4 minutes shorter than the solar day making the tropical year Gregorian calendar is based on. Things get murky quite quickly once you start going down that path of what "correct" really is.
Note that in the Gregorian calendar, Spring equinox in 2021 and 2022 fell or falls on March 20th. It's only pretty good when averaged out over a 400-year cycle.
Basically, all of these calendar systems are attempts to "square the circle": find something resembling the least common multiple of non-integer values (solar day length and tropical year length), and then try to mix in a bunch of events observed in a different coordinate system (to overly simplify it, all the night stuff is "sidereal").
So we get back to what is really "useful"?
If you don't care about knowing how many days ago, or on what date in the proleptic calendar of your choice something happened in the past just from the date inscribed on it (eg. imagine a letter dated January 5th, 1605), you would certainly be fine with just dropping 10-13 days somewhere along the way. I can, however, understand when someone thinks it's easier to be off from astronomical events for a few weeks to avoid all that administrative trouble, for instance. However, the biggest practical problem today would be that everyone else has written those 10-13 days off, so it's probably easiest to switch too, especially in the global world we've got today.
But there is nothing intrinsically better in the Gregorian calendar that makes it win on all counts. It's just another agreed-upon approximation.
"spaz" is indeed short for "spastic", but it's not typically seen as an ableist slur like it is in the UK. Presumably, the word had been out of use as a term for people with cerebral palsy long enough in the US that it passed through the "Euphemism treadmill"[1], and is no longer associated with actual disability (similar to "imbecile" or "moron").
BTW I find it telling, that the entire thread has been flagged and killed. If you tell someone in Germany unfamiliar with the NoSQL space that you plan on using "MongoDB" they'll look at you like you said you plan to use "R*tardDB".
It's a genuine real-life problem and the general category of problems is especially well-known in the marketing space. It's probably more widely known in Europe than the US (where English-only is historically the norm) but there are a few examples that occasionally get brought up on HN (e.g. the island "Laputa" being named differently in Spanish editions of works featuring it, although the unfortunate implication possibly being intentional in that case).
Outside the database space there's also Wix, who after problems getting traction in Germany tried to "own" the implication of their name by using "Ich wixe" ("I jerk off" but misspelled) or "Ich bin ein Wixer" ("I'm a wanker" but misspelled) in their German ads. I don't see any company being able to pull this off with a name that sounds like an ableist slur though.
I'm not saying Americans are (intentionally) ableist when they say "spaz" but it's definitely a word that can provoke very different reactions when used in an international context. I don't know enough about the etymology to say whether it's like "fanny" (which refers to two very different body parts depending on which country you're from) or "c*nt" (which pretty much means the same thing regardless of where you're from but can either be a friendly taunt or extreme insult because of cultural differences) but it's certainly something to be aware of.
This isn't the kind of problem you'd want to have with the name of your product is all I'm saying. I guess I'm just happy FerretDB didn't go with SpazDB.
It depended on the climate and society. Pastoralists living on the steppes almost exclusively lived off animal meat and dairy products, while folks in areas with heavy grain production were much more likely to get the vast majority of their calories from staple grain crops.
Note this does not mean that python code is thread-safe by default. At most, you can theoretically rely on bytecode operations to be atomic, which means you'll need to synchronize multi-threaded code with mutexes, semaphores and higher-level synchronization constructs.