There's a typo in the headline. It's supposed to read "Microsoft Forms Superintelligence Team Under AI Chef Suleyman 'To Serve Humanity'".

I use the magsafe on my laptop. I almost always use the laptop in the same place and only charge it there, so it's not getting mixed into my collection and picked back out, and the magsafe is somewhat easier to fumble into place than USB-C. If I was using it long enough somewhere different to need to charge it, I'd grab a USB-C (probably already nearby), rather than collecting the magsafe from where it's set up.

They could include things like special lines at immigration, rather than just visa requirements. Arriving in Amsterdam with an EU passport is much less of a hassle than arriving with a US passport, but they both count the same on this report. Then there's the question of whether you need a permit to stay indefinitely, or just the passport.

The person who made the report is a professional penetration tester. His usual method is to look for anything that could be wrong and then test whether it actually is. What he found is that the AI tools came up with potential issues he hadn't thought of, and they weren't all wrong, so it's a valuable tool to him because he normally runs out of ideas rather than running out of time to test them. He complained about the UI making it hard to go through large lists of reported issues exhaustively, and he only used the suggested fixes to get a better idea of what the issue was supposed to be. So it's clear that the tool's output wouldn't be directly useful to a maintainer, but it does serve a purpose.

I got a third-party cable for my phone that my phone recognizes as being able to charge it faster than the cable that came with the phone could. They should probably warn you that they don't have a cable or charger, in case you're getting a phone because you lost everything and don't have that stuff, but the first-party stuff isn't better these days.

I think it's even more interesting, in that one or two humans have to decide whether to question a call, and they have to identify calls that were wrong, not just ones they want to overturn, and they don't have a great angle to figure out what the algorithm would do. I think it's going to be fun to see batters try to do the ump's job, while standing to the side and considering swinging at the pitch.

I think the real issue is warm parts of China selling to cold parts of India without including the features that aren't needed near the factory. We know lots about battery chemistry, but rural farmers have had more immediately relevant things to know about up to now and don't have a good source of information on this new thing the government is pushing, so they skip things that sound like luxuries and end up with something inappropriate for their purpose.

Incidentally, this is why Windows is the best platform for photo editing: once you step out of the undemanding use, and need GPGPU and 64-bit support, you use the platform that had both of them first: "PC" as most artists would call it. 3rd party plug in library is bigger too. Try and explain that to most photographers or artists and you will first get an reflex snort, then silence, then "but I like Mac" with a laugh(photogs) or a whine (artists). Idiots.

Glad to see you agree; GIMP isn't a replacement for Photoshop, it's a replacement for Elements.

The problem is that people use Photoshop, a complete and mature set of editing tools designed for people who know what a wratten number is (which is why I've never needed a photoshop class/book, though I've no doubt I would benefit from one), often used at levels between Elements and MS Paint. And that is the user the GIMP developers code for. And the reason otherwise bright people claim that GIMP is a replacement for Photoshop; they conflate poor use of software with the software itself.

There are pieces in my (well, one) fine art portfolio that one simply can't make in GIMP. Claiming that it's "limitless" (not directed at parent - he sounds like he knows what he's talking about) is intellectually dishonest. I would love real competition for Adobe, but alas.

My main desktop has 24GB; my home away from home one has 12GB and it's painful.

I don't think you realize how demanding certain tasks are - my Photoshop CS5 process is usually idling at 15GB. I actually put some composited art pieces on the backburner because they simply weren't possible, even with working with collapsed layer copies - the free transforms necessary to do certain stitchess (often freehand because I often value human perception over "properly" corrected edge convergence) simply caused CS5x64 to die in seconds on my i7/6GB setup. 24GB - and give me 240, I'll use it - was the difference between having something in my head and something complete. And that was merely 10,500x3,700/16-bit but was made of 15 (20+MP/16-bit) images selectively mixed plus an hour or two of clone painting. True story: when I installed Adobe Lightroom 3 (an image colection manager) I realized that it switched the "Open in Photoshop" link to the 32 bit version... after I simply tried to open a flattened, preprint image four or five times and failed with RAM errors. I had just moved up from 6GB, so I was still used to seeing those errors, so I sat there reclicking a few times like an idiot... before it clicked.

An 80MP back only costs $30,000 - as a capital cost for fashion and product photography, that's nothing. 165MB a shot. Some people put these on large format cameras and slide them across a frame taking 20+ images to recombine later.

Film scans are huge, especially when oversampled for archival purposes. Scans are not done in black and white, and may have a 4th (RGB+IR) channel. Migrant Mother and the rest of Lange's WPA work? 4x5 (inches). Most of Ansel Adams? 8x10. At a recent camera industry show, one custom large format camera maker described a recent commission to build a 20x24 vacuum back (to prevent film from buckling, making an irregularly curved imaging plane). When I asked why (emulsion coated) glass plates weren't used (like they were in astrophotography for decades after they were "obsolete" to maintain critical even field sharpness) he answered - it doesn't scan well. I can only image that guy's headaches.

Imaging is everywhere, and the nominal file sizes are just the start - transforms and layers start multiplying sizes very quickly. Why shouldn't a doctor be able to pull a 10,000 slice axial scan and compare it to not only that patient's previous 20 scans (say 5 years, every three months) but the historical scans of 50 other patients, perhaps scaled and superimposed. Might not be rigorous enough for a study, but back of the envelope experiments lead to the sometimes pivotal "huh, that's funny" moments. Sometimes you need a big envelope.

In turn, imaging is just a specialized case of sampling, and that is present in just about every industry job that requires book learning. Of all people, shouldn't computer industry (dev and admin alike) people be able to think (in terms of use cases and) of uses cases other than: mom, secretary =2GB, server =16GB+? The list above (and I don't mean to pick on you; rather industry myopia) boils down to age and size of data consuming device, a nod to "high end workstations," and servers. That reads like PC Magazine, c. 1990. Well, workstations have outstripped the needs of most servers long ago - servers get virtualized into a reduced number of machines/cpus, while workstations, once they run out of space for more cpus/gpus/asics start getting expanded into clusters, then renderfarms. I understand how this can be nipicked, but my point is, intensive endusers -those in information creation and manipulation- are not just a massive GFLOPS long tail, but that quantity can be a qualitative change for these users that leads to new modes of thinking. It's one thing to run up against a memory limit; it's another to add extra dimentionality to your techniques because "your brain is now bigger." Thing is, when the tool user isn't the tool maker, these unseen limits may not be perceived as such - they dont realize what they need.

"IPHONE LIKELY TO CRASH PLANES. Apple declines to comment. Google says Android is safe because it is open. "There is no plane-crashing code in Android, anyone can see for themselves." Nokia promises additional aircraft safety for its WP7 phones once they are bricked over the air this fall."

Easy. They are going to hire Uwe Boll.

I think that ship has sailed.

I'm pretty sure Android tablets will never see apps of the same quality and level of UI polish as GarageBand, iMovie or Pages.

<...>ask some prospective customers who haven't already bought iPads what features they want<...>

It is not the customers' job to know what they want. — Steve Jobs