Also Kanopy if your local library is a subscriber. Basically anything you might see at a film festival, that could be considered "art house", and a remarkably long tail that goes back to pre-Hayes Code Hollywood (for example).
> The temperature and humidity values that iOS Weather reports are objective and "dispassionate", no?
You sound like someone who has never lived anywhere that people bitch and moan about the temperature on the weather reports being wrong because people think it's warmer than weather stations report, and get into arguments that the weather stations aren't placed correctly.
Indeed. I have a Nokia 950 and in many ways WinPho was a really nice phone OS; Microsoft's endless jerking about of developers as it went 6.5 -> 7.x -> 8 -> 10 did it no favours.
Apple enforces the rules that applications must only harvest data in the ways that they describe. That's behind Facebook's tantrum about the App Store.
Google said it would introduce an equivalent policy, but then backed off, and does not enforce it.
Why are you so desperate to break the iPhone experience? Because you can have that. You can have a Pine phone, you can have an Android device, you can have Sailfin. Why are you unhappy with all the choices for phones that provide everything you say you want?
The thing that is most striking to me about your explanation is that the change was made six years ago; it seems that anyone responsible for a company's tax position and cashflow (CFO, accountant, etc) should have been planning for this between then and now. Much like the SVB panic, a great deal of this seems to be people running companies without either paying attention to things that could have a significant impact, or hiring someone who does.
"You can't have systemd in Debian, what about kFreeBSD"
"You can't use Rust until it supports DEC Alpha"
...there are no shortage of examples where open and free software is held back by hyper-niche interests, where our pet twenty and thirty year old, long-dead projects and processor architectures create absurd barriers to improve anything.
A point which may not be well-understood by people unfamiliar with French economic history is that for much of post-WW II period, France's power prices have been dramatically lower that other Western European countries (for industry, anyway).
One of the challenges that moves to get away from nuclear generation have caused is the prospect of hurting the French industrial base more than it's already been undermined by offshoring.
(The other concern is keeping an independent nuclear arsenal, which is completely coupled to having reactors.)
Same, but it's largely been that way since the early 90s.
It's weird getting pitches from US FinTechs that are solving problems that literally only exist because of how painfully backward that US financial infrastructure is.
I fully expect my first electric car will, when it arrives, be a Hyundai or Renault/Nissan, or somesuch from a company that builds cars which happen to have an electric drivetrain, rather than whatever this shit is.
"Zero assumption" would have been a better phrase, but that horse is not just out of the stable, he's met a nice lady horse and is raising a family of foals and grand-foals.
The thing is that over-focus on perimeter security is still a huge problem, and one reason that e.g. ransomware owns orgs with depressing regularity. There's nothing wrong with perimeter controls in and of themselves. But they become a substitute for actually security what's on the internal network, so once you've bypassed the perimeter, it's all too easy to roam at will.
The people over-relying on perimeter security are the folks buying a big sixties car and assuming that seatbelts and traction control are no substitute for chrome bumpers.
It didn't help that rms was using it as a "hah hah that time I put one over on Steve Jobs" a decade later when I saw him speak. No idea if he still does.
If you're trying to get people to try your new editor, no matter how awesome the ideas that you're trying, you're going to lose a chunk of your audience if it doesn't support C syntax highlighting, a chunk if it doesn't support Python intellisense, and so on and so forth. You can have the best idea in the world, but people will play with it, and decide that they love it but can't use it for "real work" unless you slog through adding native support for a bunch of languages and runtimes/compiler suites.
That's a huge burden.
Now, if you implement LSP, you get "for free" support for C#, C, Python, Rust, etc etc. People can evaluate your editor on its merits as a text editor, not on whether you had the time and energy to add support for their favourite language.