Because root is not the ultimate authority of what goes on in the phone; the hardware is, and the hardware contains a TPM (Treacherous Platform Module). The TPM has secret cryptographic keys it never shares with anyone, neither root nor an unrooted OS. When the phone starts, the TPM checks if the OS has been modified from what the manufacturer supplies or not.
The bank's app can then ask the OS to sign documents using the TPM's secret keys, and the OS forwards such requests to the TPM. The TPM refuses such requests from modified OS but obliges requests from an unmodified OS. The bank's servers refuse to accept documents not signed by the TPM.
Root can't pretend to be a TPM and make up some secret keys to sign documents with because the TPM's signature is itself signed by Google, so the bank can tell the difference between root's signature and a treacherous signature.
After reading the top-left block of text titled "Optimizing Webkit & Safari for Spedometer 3.0", what the fuck am I supposed to read next? Am I meant to go recursively column by column, or try to scrutinize pixels to determine which of the blocks are further up than the others, skipping haphazardly left and right across the page? A visual aid: https://imgur.com/a/0wHMmBG
Columnar layout is FUNDAMENTALLY BROKEN on media that doesn't have two fixed-size axes. Web layouts leave one axis free to expand as far as necessary to fit the content, so there is no sane algorithm for laying out arbitrary content this way. Either you end up with items ordered confusingly, or you end up having to scroll up and down repeatedly across the whole damn page, which can be arbitrarily long. Either option is terrible. Don't even get me started on how poorly this interacts with "infinite scroll".
Well not all content is meant to be read in order. A layout like this is good for content where you want to incentivise users to read in whichever order you like. So if the order is confusing you, chances are there wasn't meant to be any order at all. E.g. if you search google images google guesses some relevant order for you, but it is layed out in a dense way so you can scan with your eyes and decide which thing is most relevant for you. Whether you scan the screen left-right, top-down, randomly, bottom up, or ehatever is totally your choice.
Using such a layout for a novel or something like this would be really bad UX. But using it for an image gallery? Or a series of random articles that aren't priorized? Why not?
> Columnar layout is FUNDAMENTALLY BROKEN on media that doesn't have two fixed-size axes.
You can use plain old CSS columns (which don't have the automated "masonry" packing behavior of this new Grid layout, they just display content sequentially) and scroll them horizontally. But horizontal scrolling is cumbersome with most input devices, so this new "packed" columnar layout is a good way of coping with the awkwardness of vertical scrolled fixed-width lanes.
What a weird comment. You read whatever you want next, ever read a newspaper? You scan it all and pick the article you are interested in, then read that. I don't understand these comments, they work perfectly well in real life (and fixed size is arbitrary, I can make a super wide or super long newspaper too, the axis size does not affect this sort of layout, see infinite scroll for example, as there is only a fixed amount of content on the screen at any given time).
> You scan it all and pick the article you are interested in
Okay. What order am I supposed to scan in so I don't lose my place and accidentally skip a block? Scanning column by column gets me cut off partial boxes that I'll have to remember to check again later, while scanning side to side forces me to keep track of each individual block I've already looked at, as opposed to a single pointer to "this is how far I've scanned". Alternatively, I can scan roughly left to right, top to bottom and just live with missing some blocks. That's not ideal either, because hopefully if you didn't think I'd like to look at all of them you wouldn't have included them on the page.
You're right that you can make a newspaper that's really inconvenient to read, but you wouldn't, because the failure case you'd end up with is CSS Grid Lanes.
This is so funny that I'm not even sure what to say. You can ask your exact questions about a newspaper but somehow 99% of people manage to read them just fine. I think it's just a you problem that you are looking for an exact algorithm on how to scan a page with multiple sizes of content; in reality, people just look over it all and keep track of what they have or haven't looked at all in their heads.
In a newspaper the answer is simple. You linearly scan the leftmost column to the bottom of the page, then the next column, then the next, and so on until you get to the end of the page. At no point do you ever need to keep track of anything other than "this is how far I've gotten" to make sure you haven't missed anything. Columnar layout make sense in newspapers because both axes are fixed in size, so all you ever do is one long linear scan with wraparound.
If one axis is fixed, and it is in the case of grid lanes (it's not a fully pannable infinite canvas like Figma after all), you just keep reading the content that's on the current screen, then you scroll. I really don't see how it's any different to, for example as I mentioned previously, a long newspaper with many pages; each "page" is one "screen" worth, analogously. It's like infinite scroll, either vertically or horizontally, where instead of just one item in the list, you have a few. And if we're being really pedantic, Figma users do perfectly fine keeping the context of the content in their minds even in an infinitely pannable canvas. And also, generally newspaper readers do not do what you say, scanning column by column, they instead glance their eyes over all of the headlines then pick which one looks good then they read the article attached to that, it is a free form process.
So again, I will contend that this is not a problem for the average reader. I really cannot see where the difficulty you seem to say lies.
Not exactly the 19th century, but in 1980 Softsoap bought up a year's worth of manufacturing capacity of hand pump mechanisms in order to block competitors from entering the consumer market for liquid hand soap.
Seconding Fullmetal Alchemist. I hear the remake (Fullmetal Alchemist: Brotherhood) is usually regarded as the better version. More suggestions: Neon Genesis Evangelion, Death Note, Sousou no Frieren, Cowboy Bebop, Nichijou, Tengen Toppa Gurren Lagann, Bakemonogatari. There's also quite a few good movies, anything by Studio Ghibli is great, and so are Akira, Perfect Blue, and Ghost in the Shell.
Some of those those aren't really going to appeal people unfamiliar with the conventions of the genre and some of the big personalities, e.g. Evangelion is a deconstruction of the once popular giant robot genre and Hideaki Anno's personal couch trip rolled into one.
Brotherhood follows the plot of the source material comic, which is regarded as having a better ending. The original series aired concurrently with the comic and had to diverge when it passed where the ongoing comic ran out of chapters.
Functioning democracies do yank out their elected representatives. Not randomly or even arbitrarily of course, but when they step egregiously out of line. Votes of no confidence, recall elections, impeachment, general strikes demanding resignation, and a smattering of other measures are crucial checks on the abuse of power. Electing someone to be untouchable for a set period of time is a recipe for malfeasance with examples going back as far as the invention of the term "dictator".
Re-read the comment I replied to and check if that comment was referring to everything being great already because those systems are in place or if they were calling for some kind of ad-hoc popular vote at any point during a mandate based on not liking the policies, rather than for egregious actions as you described. Your reply is theoretically correct but not what I replied to.
People managed to keep trees in cities just fine prior to the mid 20th century so I can't imagine it's an insurmountable obstacle. Beyond cutting the trees down, other valid solutions include (but are not limited to) letting the leaves be on the ground by the tree, using a rake, planting tree species with smaller leaves, or allowing the leaves to be picked up by the regular street cleaning trucks.
Trees are really only a lot of work if you insist on keeping a grotesquely unnatural manicured garden; the only tree I've got that's any significant amount work is an apple tree that would turn half the yard to a rotten apple tripping hazard if you didn't pick them up. A couple more need trimming every few years to keep a path clear, but I would chalk that up to user error in choosing to plant them slightly too close to the path.
Contrary to what the "just tough it out" types would have you believe, noise pollution does cause appreciable harm to public health. Making lots of noise in a dense neighborhood where thousands of people live is just not worth the marginal efficiency improvement of blowing vs raking leaves. Tangentially, this is also one of several reasons why speed limits should be 30km/h in cities to limit rolling noise.
Someone who thinks Jerry Pallotta's "Who would win?" books are a good example of science communication directed at children should not be taken seriously. I'd go into why, but here's an actual zoologist doing a much better (and entertaining) job of it than I could: https://www.youtube.com/playlist?list=PLgtE7_5uJ2p5Oeied2x4L...
The bank's app can then ask the OS to sign documents using the TPM's secret keys, and the OS forwards such requests to the TPM. The TPM refuses such requests from modified OS but obliges requests from an unmodified OS. The bank's servers refuse to accept documents not signed by the TPM.
Root can't pretend to be a TPM and make up some secret keys to sign documents with because the TPM's signature is itself signed by Google, so the bank can tell the difference between root's signature and a treacherous signature.
reply