They might be useful for some things in some situations and they are here to stay… for now. They won’t be the future though.

Reap what you so, this turd sand which does what it said on the tin.

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.

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.

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.

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.

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7556303/ https://www.frontiersin.org/articles/10.3389/fcell.2022.8248...

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.

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.

It's the most flexible computer I own. It could be even more so, which I would appreciate, but that depends largely on apple.

For the work I do I can code *locally* but I *don't have to*. Comparing it to a Switch is completely missing what makes them different. Even an attempted reductio ad absurdum should be a little more rigorous than that.

When I'm home I don't really need the iPad for this (much). There a few use cases where it's clearly better than my MacBook Pro though: the screen is veerry nice outside and I've written more in a hammock than you'd think. Also - airplanes which I am on more often than I'd like to be. an iPad Pro with the magic keyboard is fantastically shallow. It fits on a tray better than anything else.

I don't know about C#, it's not an ecosystem I swim in at all, but there are multiple python options (including Pyto, the venerable Pythonista and jupyter notebook hosts like Juno & Carnets). There are js environments like Scriptable and Play.js. And it's not Xcode but Swift Playgrounds offers, of course, swift including swift.ui and the ability to redistribute those projects (with some limitations) including submitting directly to the App Store.

I get it; I use an iPad a lot for a great many things. It's not perfect - I have a long list of things I would like to see addressed. Low effort complaints like "let me know when I can code on it" are just that though; low effort. So those who complain "how to code on it?" or about how it exactly match the workflow they use on a completely different platform etc just sound.... whiney.

Low effort noise when some basic infrastructure could enable so many other workflows. I like my iPad, I use it every day, I hope to use more with less friction soon-ish. Yup, same thing every June.

Musk brings absolutely nothing to the table in any of these arenas and has been publicly terrible at at least two of them.

The internet is full of agendas, opinions and viewpoints. All this move shows is that there's also at least one idiot will to watch 45billion evaporate.

Ok, ok, it's Elon. So he's willing to talk about it and anything substantiative coming out of this will probably arrive just after full autonomous self driving vehicles.

This is not a good look.

I really don't get the outragefilter here - Apple (take 'em or leave 'em) lays out for the public a system for checking uploaded content for illicit material that everyone else is already checking for and just didn't tell you. And somehow the disclosure is reason to get pissy?

Don't get me wrong I'm not saying the only alternative is to love the largest corp that's ever existed because that's a dumb-ass false dichotomy. I just don't understand the vitriol expressed in certain quarters over this issue when you know that the rest of FAANG, and smaller players, are doing no less and never even bothered to figure out how to do so with even an iota of respect for their users. Hell y'know google's using your photo backups to sell you advertising at least, training models in the mid, and at worst going to comb through everything you ever brought within their arms reach the moment local law enforcement makes them. If they're not doing so already.