AnandTech speculates on a 128-bit DRAM bus[1], but AFAIK Apple hasn't revealed rich details about the memory architecture. It'll be interesting to see what the overall memory bandwidth story looks like as hardware trickles out.
True; rent should be suspended due to the crisis. The mechanics are tricky, and much worse, I have no hope of the actual policy leadership required to see this through here in the US. We're like an off-road vehicle with a suspension system built of cheap glass.
> we’d be figuring out how to temporarily suspend rent, loan payments, and taxes
This. Under society-wide crisis, it's madness that the economic impact is supposed to just stop at landlords, moneylenders, etc. There are instances where individual organizations are trying to do the right thing, but the only humane thing to do is spread the impact (and recovery measures) across everyone.
Cameras. High capacity removable flash media used by digital still and video cameras is often formatted as exFAT. Despite MS' licensing, FAT/FAT32/exFAT are essentially the "file systems of interchange" for removable flash media.
Didn't the writers of VOY ever read the TNG Tech Manual?
Nope, in fact they were expressly prohibited from writing about the technology. In the scripts, instead of doing their built-world-homework and writing that coherently into the story, they just had to put "[TECH]" in to the scripts. Then the technical consistency editors came along and filled that stuff in. Not even kidding. This led to some of the really disastrous (IMO) early scenes in Voyager such as one where two characters (Cpt. Janeway and B'Elanna, iirc) are bonding while solving an crisis technical issue... and the dialogue is a total hash because it was "co-written" using a completely insane method.
Honestly, just using the basics of "responsive web design" (search phrase) is most of it. That is, implementing your site using CSS media queries to adapt your layout across multiple device sizes. Contrast that to using hacky device detection to deliver some entirely separate and "mobile-specific" site. One anti-pattern that often happens is the "mobile" detection is wrong, and delivers some phone-sized UI to a tablet. Instead just leverage CSS to make your site look good at the user's current display width, whatever that is, without having to know anything about the device. This is also great for desktop users, e.g. who might have your site in a browser side-by-side with something else, or similar.
All of the "evergreen" browsers have a mobile design view built into their dev tools these days. You can enable that, switch between specific device screen profiles, and continuously drag the "screen size" handles to watch your site's behavior at different sizes. This is great for development, since your web inspector view stays at full size.
Combining CSS media queries with CSS flexbox is a hugely powerful way customize the end-user experience for different devices. Flexbox not only makes basic layout adaptations straightforward (or free!), it lets you handle some otherwise tricky cases using tools like reordering support.
It's probably also worth searching for "mobile first web design" for further resources.
Nonsense. iPad has had "iPadOS", since the iPad-specific features like Split View landed in iOS 9. This is just Apple communicating more formally about that strategy with its userbase, and increasing support for iPad-centric workflows.
Consider that most of the iPadOS features shown are refinements of or much-asked-for enhancements of existing features:
- Multi-document Split View
- Slide Over app switcher
- Network share and external media support in the Files app
etc.
[edit: props to snazz, who corrected me on the iOS split view release.]
Yes, this. This bridges some gaps for sites that are built as either mobile-specific (but not truly responsive), or as desktop-only. I would have thought that the whole device detection, mobile-specific thing would have died many years ago, but it is stubbornly persistent. True responsive sites have worked fine for ages, and should continue to do so.
On the desktop-only site side, it looks like Apple has also done some interaction refinements for problems touch-based users can hit on these sites, especially around distinct hover vs. click interactions, the need to "tap-twice" to essentially "focus then click", etc.
I have a lot of problems with surge pricing in general, not the least of which (in this example) is that it creates two classes of 'net users: those with enough disposable income to probably not care about surge pricing ever and those for whom it's a burden. Yes, that's a reflection on larger societal issues, but it's still there.
Worse, surge pricing is often a distraction for nearly everyone. IMO, it's not ethical to implement surge pricing without allowing a user some mechanism to opt-out of it and to understand why they aren't getting bandwidth at that time. But having put that stake in the ground, the UX now requires that the user waste mental decision energy on ... business bullshit[1].
Last not far from least, it aligns the incentives of carriers against providing enough coverage to handle capacity. We're learning how to handle higher density wireless scenarios (cf. articles on stadium and other heavy-use event network systems). Would we rather incentivize trickle-down of these systems into high-traffic public areas (e.g. commuter zones), or just further line the pockets of a few near-monopolist carriers at our own expense?
[1] This relates to why users rightly don't like metered billing -- it creates decision pressure. A payment structure that alleviates use of decision energy is a value add.
[1] https://www.anandtech.com/show/16226/apple-silicon-m1-a14-de...