agsnu

A private tour company has been flying an A340 down there for a few years https://www.youtube.com/watch?v=CBRX3QJJ0Jg

Sure and I don’t mean to minimise the value/effort - I’m sure the “look at” may involve actually investigating the issue themselves by looking at the implementation, speaking with the responsible engineers, etc. I am also sure it is a hard problem to solve - while Apple is massive and well resourced these days their developer community is also humongous and I am sure there is a tremendous amount of noise. But my point is merely - TSIs are not a panacea

Almost every time, developer technical support will look at the internal bug and if there is no known workaround will say “sorry that’s our bug and engineering is investigating, we don’t have anything to tell you, please keep an eye on the feedback and we will update you if anything changes - in the meantime here’s your TSI refunded”.

Surely Klarna’s model relies on some portion of folks being charged late fees? Seems only marginally less predatory…

Trees also provide a significant cooling effect by releasing water vapour into the air from the soil (evapotranspiration), which you won't get under an umbrella.

It would be fair to say it's "quite simple" to port macOS apps to Linux if macOS apps were written against the Unix/POSIX API, but they are generally written using Apple's macOS-specific proprietary frameworks, meaning a Linux port of a GUI application would really be a re-write.

Ignorance is bliss

Of course Swift is now almost a decade old, so it's increasingly rare to find a pure Objective-C codebase

earlier thread https://news.ycombinator.com/item?id=35158145

Flu spread among all humans (not just those supplementing vit D) was massively reduced in recent years because of a little thing called COVID-19 and all the social distancing/lockdowns that led to...

But on the flip side, Apple provides a much longer support lifespan for iOS devices than Android vendors do. I wouldn’t want to use the latest Chrome on a device running iOS 9 anyway.

I miss Audion.

Apple breaks too much stuff in software updates. I want to control what versions of key libraries I'm integrated with and rev them on my own schedule.

I'm just holding out for a Jetpack Compose for iOS :)

I remember in the mid-00s, Mac laptops suddenly became popular - one of the reasons was you could take them around and plug them in to TVs/projectors and they just worked, but Windows was really hit-and-miss. Now it seems like that's flipped, and MacBooks have random external display issues these days... Sad.

It looks like this aims to be a replacement for people want to use an Android-based OS but don't want to rely on Google services, normally for reasons of philosophical objection to big tech's de facto surveillance capabilities. So presumably users of GrapheneOS, CalyxOS, LineageOS, etc.

Also since Google is blocked in China, Firebase Cloud Messaging doesn't work there. Android has something like a 75% market share in that market. Some vendors have their own offerings (e.g. Xiaomi MiPush, Huawei PushKit) etc, I could buy that a popular centralised solution would be more attractive than doing N integrations.

Actually, it was changed to macOS in 2016 for 10.12 Sierra, to align the branding across Apple's various platforms (iOS/macOS/tvOS/watchOS).

They don't. People just saw a G450 moving from Nassau and assumed it was SBF. Seems more likely to be Joe Lewis, who lives in the Bahamas but frequently travels to Argentina.

BowelsOfTheMemoryMgr

See https://ludwig.guru/s/has+precedent for a plenty of examples of using "has precedent" in non-legal contexts.

Tesla is currently engaged in litigation over allegedly firing employees without providing necessary 60 day notice period under California law, denying them pay as a result, so it would appear that Musk has precedent.

Since OCSP fails open and response stapling is still only deployed on a minority of servers, it doesn’t provide much of a guarantee…

Having a commit in isolation that "does the suggested thing" reduces the cognitive load on the reviewer(s) because you can see the conversation history and the specific changes in response to that comment without having to re-parse the entire branch changeset from first principles.

Basically the trade off is, re-write history before review or after.

If you re-write before review, you lose some context about the evolution of the changeset - also the GitHub UI can get confusing (because some conversation comments will apply to commits that no longer exist on the PR branch). Keeping the pre-review iteration visible in the context of the PR can make it easier for someone else to come along and join the discussion later.

If your feature branches/PRs are short-lived, then the size of a squashed merge is still quite small, and the pre-review iteration is irrelevant. If for some reason the pre-review iteration is interesting, it's still there in the context of the PR, which is back-referenced from the commit message.

oopsy daisy

Hopefully the British people don't receive their moral compass from elected officials either, given the recent occupants of the office of Prime Minister...

That's BBC

No

Coutts is of course not an EU bank any more. Sigh.

BYOD is very common these days, MDM can only defer updates if it's a managed device. Most people don't want to carry two devices and most companies would like to save the cost...