I believe Google's Safari payments are a significant chunk of services revenue too (around $20 billion a year.) Then there's Apple TV and Apple Music, which are not nothing.
And in many cases, multiple times. I wouldn't be surprised if the number of SQLite DBs on my phone was in the hundreds and the number of separately compiled copies of the library is in double digits.
Is the syntax really the stumbling block for most languages? Would Rust's lifetimes or Swift's isolation rules be easier if they used more parens? Are the scoping rule differences between Emacs Lisp and Scheme easier to comprehend because the syntax is similar?
The two leads, Rob Morrow and Janine Turner, are doing a rewatch podcast called Northern Disclosure. They seem to be in season 3 right now. No endorsement, haven't tried it myself.
Yeah, agreed. I liked the idea of Mercurial branches better than git's — in principle I prefer more rather than less metadata in history — but they genuinely had a scaling problem. I can't recall the numbers, this being more than a decade ago, but I tested with a realistic number of branches for a team of developers using short-lived branches for a while and you could easily see Mercurial slowing down.
Back when I was testing bookmarks were available, but Bitbucket was pretty much the only forge that supported Mercurial and their tooling didn't support bookmarks, so that made them a non-starter for many users.
It might be helpful to have a modifier on all the models. It's a bit awkward (not that the naming geniuses at Apple have ever cared about how awkward it's to talk about their products, witness "Apple Watch Edition" and Max Macs) to talk about iPads, because one of them lacks a modifier. "Which iPad" "The iPad iPad", etc.
That's a serious overgeneralization. It's true for some people, but trains mostly don't bump and swerve enough for that to be a significant problem. Finnish trains have lots of seats facing backwards and while they're not anywhere as fast as something like a TGV, they're still often going 200+ km/h. People seem to be just fine. I just spent 1 hour 40 minutes yesterday sitting backwards, mostly reading a book, with no ill effects.
They could do it, but I wonder if it makes sense financially. It's probably easier for a neutral foundry like TSMC to recoup the costs by selling the capacity to whomever for years to come. Apple probably isn't interested in getting in the foundry business, so they'd be the ones who'd have to use all the capacity a production line has as long as it's running.
EU isn't a country, it's a union of 27 countries with their separate legislatures. I live in Finland, a country of five million people. According to your math I think I'm allowed to basically burn a lake of oil every day, right?
I love Yamaha Motor using the tuning forks as their logo. It's a proper beautiful old-timey logo (well, from 1967, apparently, but anyway) and it's just so weird seeing them on a motorcycle.
The parliament seats are also apportioned by state. I don't find that a bad idea, living in a small country, and I don't see why the council seats being divided by country is a worse idea than the system in the parliament.
But this is not about removing the ability to read screen content. It's about removing the ability to read screen content without telling the user.
That's why I think questions about frequency and "most users" (nebulous term, I admit) come into play: yes/no permission dialogs aren't the best and many users do just click through them without thinking, but there's a world of difference between asking several times a day and asking a couple of times a month.
If my usage is far below average, then I agree that it's probably better not try to restrict it. If, as I would guess, I use it more than most, then it feels exceptional enough that letting the user know when it's happening would be fine.
If you could give a permanent permission to a given app, I'd imagine even the daily streamers wouldn't be too badly inconvenienced.
How often do you think most users read the screen, especially using something other than the screenshot tool of the operating system?
As an iOS developer I run Xscope to check details of designs, I don't know, maybe once every two weeks? And I guess I've probably used Acorn's color picker outside its own window during the last year, but I'm not sure about that.
I'd imagine that most users need apps reading arbitrary pixels off their screen less often than I do. I'd appreciate a warning from the operating system when an app tries to do that.