He spouted every kind of hateful shit, and surrounded himself with even more vile shitstains. Every terrible thing imaginable was put on the table. Some Americans may not have liked the alternative but this election was never about “better” or more tolerable” or any thing else except shortsighted hate.
Reap what you so, this turd sand which does what it said on the tin.
spoken as someone who doesn't need health care (yet)
spoken as someone who doesn't need schools (yet)
spoken as someone who doesn't need reliable infrastructure (wtf?)
Better take-home pay only counts if you don't need the things taxes pay for, or (apparently) don't need a supporting community that does need them. That situation, though, is a lot like saying "I'm a CEO with my own jet - I don't need no stinking' roads" but then can't sell anything because all of their product and all of their employees need roads to get to work, to ship, to function.
In addition to this here's one really specific case: ever had a pandas groupby().apply() that took forever often mostly re-aggregating after the apply?
With columnar data DuckDuckGo is somuchfaster at this.
For one of my projects I have what sounds like a dumb workflow:
- JSON api fetches get cached in sqlite3
- Parsing the JSON gets done with sqlite3 JSON operators (Fast! Fault tolerant! Handles NULLs nicely! Fast!!).
- Collating data later gets queried with duckdb - everything gets munged and aggregated into the shape I want it and is persisted in parquet files
- When it's time to consume it duckdb queries my various sources, does my (used to be expensive) groupbys onthefly and spits out pandas data frames
- Lastly those data frames are small-ish, tidy and flexible
So yeah, on paper it sounds like these 3 libraries overlap too much to be use at the same time but in practice they can each have their place and interact well.
If you're particularly envious you may want to consider asking how those who can't drive make do in your location. Life's about making choices and seeking different perspectives might help change and/or inform your priors.
Similarly one of my most important projects reads a lot of api calls returning serialized json. Those calls are expensive so I have, over time, tried many complicated cacheing mechanism.
These days though it's _so_much_simpler_and_cleaner_ to just wrap the call in a decorator that caches the request to sqlite3 and only makes the call if the cache is stale.
I don't worry about parsing the results or doing any of the heavy lifting right away - just cache the json.
Sqlite is so good at querying those blobs and is so fast it's just not worth munging them. Nice.
And using something like datasette to prototype queries for some of the more complicated tree structures is a breeze.
Similar situation here; I try not to unplug mine :)
That being said the heat output is so low my mini lives in a drawer and serves to host time machine, a Jupiter notebook server, media server and a couple parallels VMs.
The fact that it just as easily serves up a display on my tv, iPad, Chromebook etc is extremely nice. It's been reliable enough to act like an appliance & fast enough that I never worry what else is running.
Similar to, say, an ABI but more so, there's no reason to think that cases would present identically. Complex systems-of-systems in homeostasis can be expected to have breakdown behaviour that clusters around some targets with a very very long tail of other less common features.
Nope - this is a real issue inside our domestic borders. The country has two official languages but only one region that legislates one of them as second class.
Additionally - Quebec's insistence on "protecting their distinct and unique culture" tramples all over the rights of other demographics important to the formation of the country. Ex: Montreal sits on unneeded Mohawk land and the insistence on French (very Quebecois French, see numerous stories of relocating citizens of France not passing the competency requirements) but you can't get served in any Iroquoian language and in much of the north many citizens speak dialects of Cree as a first language.
So you have Indigenous people who were trampled, those who signed treaties that were then broken and/or ignored, the Metis who at least got a slightly better deal having negotiated later and spent a lot of blood, and then the Quebecois who were (basically) on the loosing side of a war & abandoned by the mother country in favour of sugar plantations in the Caribbean.
And of course they get the best deal with untenable consequences and have to be entertained every time there's a complaint that can't possibly be backed up. Whether a referendum ever actually passes the province simply can't afford to separate so, uhh, yeah. Sweetheart deals (when compared to everyone else) because, simply put, racism.
So keep some of the context in mind when Canadians complain that the province will outlaw "bonjour-hi" but you can still be served in English at nearly every fast-food joint in Montreal but might very well not get admitted to a hospital because your French isn't proficient enough.
