>(2) Given the complexity of the problem and the involvement of hundreds of research groups and dozens of national and international funding agencies, why give a Nobel Prize to just a couple of research group heads for this new understanding?
Because these two were directly responsible for the discovery and the initial understanding of the mechanism of what was going on. The depth and quantity of the resulting research, funding, and all the other streams of new jobs or additional lines of research are follow-on results from the finding, which to me is a metric that highlights the enormity of their achievement and the richly deserved nature of this award.
Conservation of the sequence and temporal expression of let-7 heterochronic regulatory RNA - AE Pasquinelli, BJ Reinhart, F Slack, MQ Martindale, MI Kuroda, B Maller, DC Hayward (Nature, 2000)
Limiting it to three people really doesn't make much sense, and the selection of winning candidates has far more to do with political maneuvering then it does with how scientific discovery works. Similar issues arise in many other Nobel Prize awards, eg the discovery of the mechanism of ribosomal protein synthesis.
Swiping left to right from the leftmost edge of the phone onto the screen will execute the "back" function with or without the presence of a "back" arrow at the top-left corner.
I was actually looking forward to this coming to iOS, but it’s one of the things that work great until they suddenly don’t. Back from a photo in Photos? Swipe down or top left corner. Hide the keyboard? Middle right. Back from someone’s profile in Messages? Swipe down or top right. Back from a PDF in Files? No swipes, just top right. Some of these do make sense if you follow closely how the UI elements fly onto the screen, but are confusing if you don’t.
You can't swipe across the opposing screen edge with your thump without letting go of the full grip on the phone and holding it only partially, risking it to fall. Glass phone body only makes things much worse. You can do it with a back button in a sane position though, without compromising a grip. Android allows navbar gestures since ver.10 and I never enable them because buttons are simply better, even though they take away some space on the screen.
I switched to iPhone 13 Mini because there's no recent and small Android phone anymore. On the Mini, you can easily reach that screen edge. Which just drives home the point that those gigantoscreens are a bad idea.
Dropped my iPhone 13 around 4-5 times, on the floor, in the bathtub without water, on the desk. Not even a scratch. I was afraid of the glass back but this thing _is_ sturdy. "Risking to fall" was a good reason about 4-5 years ago, but since then the devices got much better protected from falling IMO
Dedicated back and home button is the reason why I always buy a refurbished Galaxy S7 after I break/lose it. This is my third is six years.
I like that the price to pay to maintain the same experience actually goes downwards. Who knows how long it will keep working like that?
Hopefully I will be able to put lineageOS or postmarketOS on it when the software eventually stops working. Maybe some day I get to be an amazing linux hardware programmer like Caleb Connolly and am able to mainline S7 support in linux like he did for the SnapDragon 845, whatever that means
> Who knows how long it will keep working like that? Hopefully I will be able to put lineageOS or postmarketOS on it when the software eventually stops working.
You'll be fine, if I break my current phone, my next one will be a Galaxy S4 as well, some people do run Android 12 on it nowadays, the battery is replaceable and the phone is so cheap used that it's not even worth worrying about.
but now they added this task switcher to iPad which also appears when dragging from the left edge, and now going back is like rolling a dice. you don't know how how to go back without triggering the task switcher so it ends up taking multiple attempts to go back without the OS consuming the input
Not on iOS, which I believe OP is referring to. On Android you can swipe back. But I just tried this on my iPad and it does not work. For the longest time I never even _noticed_ that "<back" link in the upper-left corner!
As an iOS app dev, swipe to go back definitely works on native iOS apps. If you find an app it doesn’t work in it’s probably an app built in whatever cross platform UI framework which doesn’t implement the gesture.
Additionally, one can always swipe the bottom bar to switch between apps.
Even native iOS apps have some terribly inconsistent back behaviour, particularly when handling overriding swipe functions.
Eg Photos seems to change Back on almost every view. Swiping back navigates around albums and locations and such. Until you open a photo, then it flicks between individual photos.
If you are looking at a photo and want to return to album view you need to click the Back arrow at the top left.
If you swiped up to view photo details and want to go back to the photo, you need to swipe down.
If you are Adjusting photo details, you need to click Cancel at the top left.
If you are editing a photo and want to go back to the photo, you need to click Cancel, which is at the bottom left this time.
The only place I don't notice a back button in Photos is the top right. But that's exactly where Books puts it.
On Android, every single one of navigations would be performed by the dedicated back button/swipe. Which might explain why the iOS Google Photos app seems to just stick with a top-left back button on almost all views.
You definitely can swipe back on iOS, I do it all the time and AFAIK it's the primary recommended way to go back. You have to swipe from the edge though.
Yes it does on iOS, it might just be that you misunderstand how the mechanic works. Swiping back will never exit you out of an application. But for example if you go Settings → General → About and then swipe back two times you'll end up back on the Settings screen.
iOS happily kills backswipes with inconsistent alternatives.
eg View details in Photos, and swiping back doesn't work. But there are also no back buttons or visual cues. But there are 3 ways to get out of that screen AFAIK, which some might label intuitive.
But if you go one step deeper and Adjust the photo details, the only exit is a Cancel button.
Correct. Poorly named, but Android Automotive is the equivalent of the iDrive software that runs in the BMW center panel (in the absence of any other user device)...CarPlay or Android Auto could still overlay that assuming the carmaker supports it.
You could learn enough HyperTalk to do useful things inside a day - I know; I did exactly that, when I was 11 or 12 and had a chance to find out on a Mac at the museum where an uncle of mine then worked. Granted I already had experience with Apple BASIC, so wasn't a complete programming novice, but I'd never worked in a graphical environment before, and yet still managed to turn out a fairly presentable, if short, "choose your own adventure" style game with some complex world state in just a few hours.
It would be utterly risible to suggest that a child of similar age and prior experience could do the same today, starting from scratch with web technologies. Yes, you can do more with the modern web. But the initial complexity barrier is very much higher.
Not that risable: my 11 year old has gone through the Python Crash Course book and built a basic Django pizza ordering website with a database in a day.
That’s after work his way through much of the book, of course, but... as with any complex domain, the right teacher can make a big difference.
I think that goes to both your point and mine; sure, the website does a little more in that it can be accessed from computers other than the one where it's running, but he also needed a whole book to do not much more than scratch the surface of what we call "web programming".
That's not to say it isn't a significant accomplishment, and he should be proud of it!
I don’t know that it is only scratching the surface - the book gets you into an interactive site that is styled with Bootstrap, uses a database, uses web APIs, pushes to Heroku so it’s HA and scalable, etc.
It’s pretty much all the major elements of web programming but using the more elegant ways of simplifying the experience.
I’m not denying the complexity just saying that there are still many (particularly in Python or in cloud PaaSes) who value streamlining the experience.
I'd still call it scratching the surface in that I doubt it goes into details on how any of those things actually work, and that's an important consideration because it's the basis for knowing how to deal with any of them going wrong. No doubt you'd have been able to provide support in that case, but it still goes to the point of there being a much larger potential depth of complexity here.
I get the sense the book tries to surf the reader over the top of most of that ocean, and that's reasonable enough, but the ocean is still there. I wouldn't consider it all that comparable to Hypercard, which in this metaphor I guess is more like the town pool back when those still existed? People who are ready for the deep end can dive into it, and people who feel like paddling around in the shallow end is more their speed can safely do that too.
I mean, I can, if you spot me Node/Express or even TS/React as the stack to use. Those are at the core of my professional discipline, and I know what's going on well enough with them that standing up a new project, complete with compilers, linters, style formatters, style linters, and so on, doesn't take me much.
But that's building on close to twenty years of working in the field, and a bit over three decades since I first put my hands on an Apple IIe's keyboard and wrote
10 PRINT "HELLO"
20 GOTO 10
Which is the key part, really - I wasn't far past 10 PRINT "HELLO" when I happened upon Hypercard, and I was still able to use it effectively with no more background than that. I don't know that there's anything comparable today.
Yes, todays web is far more complex. But the early web from the time when HyperCard failed was totally different. At that age I absolutely learned enough to make my own home page. For many years that's simply all the web was: home pages, webrings, etc.
Hypercard scripting was intended for non-programmers. Normal people can do wonders with simple tools after little learning. Just like people using spreadsheets. Hypercard made programming available for non-programmers.
The police union requested this. To my knowledge, they don't have any authority whatsoever to call out state national guard or federal troops into a state. Would be as meaningless as me declaring my private property an independent nation state.
I'd say it's more indicative of the randomness of contestant inclusion than anything else. Are the rates of "regular watcher" contestants decreasing? Have the producers changed the type of contestant they decide to include?
To be truly effective at these games, you needed to be watching what the accepted show price of items were...you never could assume your local store price or dealership price.
Because these two were directly responsible for the discovery and the initial understanding of the mechanism of what was going on. The depth and quantity of the resulting research, funding, and all the other streams of new jobs or additional lines of research are follow-on results from the finding, which to me is a metric that highlights the enormity of their achievement and the richly deserved nature of this award.